Name the service lane and the exact stay context.
Request entry
Enter the request before the guest has a full session.
This route is the operational fallback for concierge-style asks. It does not mint preview identities. It gives the guest a clear path into the live product once the ask deserves execution.
Declare the timing window, resort location, and who the request is for.
Hand off into the live guest or concierge surface once the ask needs execution.
Request fields
The fallback stays narrow on purpose.
Dining, concierge, transport, equipment, activity, or pre-arrival.
Now, same day, tomorrow, or a named arrival window.
Resort, hotel, chalet, restaurant, or pickup point.
Who the request is for, including any child, sizing, or mobility constraints.
Request intake
Capture the operational ask on the web before the guest has a full session.
This intake is deliberately structured so the guest can move forward without preview runtime, while Sommet still writes the essentials into a persisted backend handoff record for follow-up.
Next move
Choose the hand-off that matches the confidence level of the request.
Guests who are ready can sign in. Guests who still need human help can move into concierge. Guests who only want rough commercial framing can switch back to quote.
If the Sommet app does not open on this device, the request intake above still captures the web fallback path.