These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Hospitality CRM
- Features
- Group stay inquiries
Group stay inquiries
Track a group request's stay dates, room nights, venue and independent decision.
OverviewGroup stay review inbox×
Hospitality CRM · Group stay inquiries
New
Group stay review inbox
Approval conditions
| Id | Status | Arrival | Departure | Room nights | Venue | |
|---|---|---|---|---|---|---|
| IDD-598 | Submitted | 19 Oct | 26 Oct | 200 | VNE-924 | |
| IDD-912 | Submitted | 11 Oct | 14 Oct | 170 | VNE-160 | |
| IDD-491 | Submitted | 18 Oct | 27 Oct | 200 | VNE-646 | |
| IDD-598 | Submitted | 12 Oct | 17 Oct | 110 | VNE-772 | |
| IDD-214 | Submitted | 08 Oct | 10 Oct | 90 | VNE-974 |
6 of 6 records
IDD-598Group stay inquiries · GSI-63192
SubmittedArrival19 Oct
Departure26 Oct
Room nights200
VenueVNE-924
ParentOPP-75840
What you can do
Put the request beside the opportunity
A group stay inquiry belongs to a selected hospitality opportunity and operating organization. The request holds arrival and departure dates, room nights and venue. Its status shows whether the owner is drafting, has submitted, has received a decision or has completed the reviewed inquiry. This is the request record for the sales team; availability and a final reservation are separate operating connections.
A buyer may change dates while a deal is still moving through proposal. The inquiry revision and decision date identify the request that the Sales Manager saw. The review decision is stored under the parent opportunity, so the team must match its operation key and source revision to the inquiry being reviewed. The owner should resubmit a changed request for review instead of treating an earlier decision as approval of the new scope.
How the work is organized
- Prepare the request. The Relationship Owner links the inquiry to its opportunity and enters the stay evidence before submission.
- Independent review. The Sales Manager approves, rejects or returns the submitted inquiry after checking the current revision.
- Complete the reviewed case. An approved inquiry can move to completed through a guarded action with an operation receipt.
What to agree during setup
Decide what your team means by room nights and how the venue name will be entered. Agree whether a buyer’s date change creates a new revision of the inquiry and what the owner should write down before resubmission. Set the reviewer for each organization so the person preparing the request cannot treat their own work as independently approved.
The stay dates form the schedule view. Use that view to review requests by arrival and departure, and use the board to separate drafts from submitted, approved, rejected and completed requests. Keep both views tied to the same inquiry record; the board is not a separate source of truth.
Check the handoff on an actual case
A corporate buyer asks for a room block arriving on a Monday and departing on Thursday at a named venue. The Relationship Owner attaches a draft inquiry to the open opportunity and enters the dates, room nights and venue. On submission, the Sales Manager sees it in the review inbox, checks the scope, and records an independent decision for the current revision.
Change the arrival date after a return and rehearse submission again. The next reviewer should see the revised dates, not the original ones. Approve the corrected inquiry and complete it. Confirm that the receipt points to the same parent opportunity and that the inquiry’s status matches the decision. A rejected inquiry should remain readable with its decision rather than disappearing from the board.
What your team sees
- Group stay review inbox — Submitted requests awaiting the Sales Manager’s decision.
- Group stay schedule — Arrival and departure dates for submitted, approved and completed requests.
- Group stay board — Requests grouped by their current inquiry status.
Follow the work through
What it keeps track of
Data model- Group stay inquiries
- Domain extension records requesting group-stay availability for a selected opportunity parent.
- Opportunities
- Hospitality sales opportunities with lifecycle stage, expected value, expected close date and revision guard.
- Organizations
- Operating organizations (hotel groups, resorts and travel partners) that own accounts, opportunities and group-stay inquiries.
- Review decisions
- Independent review decisions (approve, reject, return) recorded against an opportunity revision.
- Operation receipts
- Idempotent operation receipts recording the outcome of each guarded action with its stable operation key.
Who uses it
Permissions- Relationship Owner
- Prepares and submits group stay inquiries.
- Sales Manager
- Reviews them independently.
- Auditor
- Reads the authorized decision and receipt trail.
Set up Hospitality CRM your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.