Many places.One connected stay.
From a question before arrival to the restaurant menu. Help guests find what they need and your team understand the context behind each request.
Every touchpoint needs continuity.
Offerings change, questions arrive through different channels and several teams support the stay. Organise information and handoffs before adding more messages.
From a menu to a conversation.
An illustrative workflow from browsing a menu to a restaurant request. Each perspective clarifies what information the next team needs.
- Entry point
- Restaurant menuIllustrative resort offering
- Information
- Ingredients and allergensContent maintained by the team
- Enquiry
- Preparation questionRequires F&B confirmation
Find useful information
The guest browses a menu and checks the listed allergens. A specific preparation question is directed to the restaurant team.
Ask the restaurant to confirm the dietary requirement before making a decision.
- Service
- RestaurantContext preserved in the enquiry
- Request
- Dietary confirmationAwaiting human review
- Reply
- To prepareThis example sends no messages
Receive a specific request
The team receives the enquiry with service context. Published information helps guide the conversation but does not replace restaurant confirmation.
Confirm preparation details with the kitchen team and reply through the agreed channel.
- Timing
- During the stayAvailable event to validate
- Content
- Service informationMessage prepared for review
- Activation
- Conditions pendingNo delivery in this example
Follow through thoughtfully
A stay journey can present relevant information when suitable events and permissions exist. Opening a menu alone does not activate a promotion.
Review the event, channel and guest preference before enabling the journey.
Manual exploration. These scenarios do not send messages or change any hotel data.
Support the stay, touchpoint by touchpoint.
A service workflow begins with clear information and ends with a clearly assigned responsibility.
Keep the offering clear
Publish menus and allergens so guests can explore the restaurant’s offering. Review content whenever a service changes.
Restaurant · reviewed menus and contentConnect enquiries with the team
An informational reply and a request needing confirmation are different tasks. Preserve context and pass decisions to the responsible team.
Concierge · service and handoffChoose when to communicate
Prepare pre-stay, in-stay or return journeys using available events. Review channels, preferences and conditions before enabling delivery.
Marketing · configured events and channels
Before taking the first step.
Does this include automatic booking for every service?
Spa, activity or room availability is not assumed. In the demo we distinguish information, requests and confirmation, and review what each connected service supports.
What information should the resort prepare?
A representative menu or service, its conditions and the team that responds. It also helps to identify where the information is maintained and how changes are approved.
Does this demonstration send messages?
The workflows on this page are synthetic and send nothing. An implementation needs reviewed events, channels and communication preferences.
Start with one service at your resort.
Choose a frequent question and the touchpoint where it begins. We will review how to connect information, service and confirmation.
Request a demo for my resortExplore other solutions