Know the detail.Care for the relationship.
Your hotel has its own way of welcoming guests. Bring together the context your team needs to carry that care across shifts, channels and stays.
The conversation does not start from scratch.
A preference in a note, a request in another channel and a previous visit in the PMS. The challenge is to give the team useful context, with identifiable sources and permission for each use.
One request, with the context intact.
An example guest asks about a late arrival. Switch perspectives to see what each team needs before acting.
- Guest
- Example guestIdentity awaiting review
- Stay
- Arriving this afternoonSource: illustrative reservation
- Request
- Late arrivalTo confirm with reception
Prepare the arrival
Reception brings together the available reservation and the request. The profile match is reviewed before assuming all the data belongs to the same person.
Confirm missing information with the guest and record the need for the next shift.
- Case
- Late arrivalThe same guest request
- Context
- Hotel instructionsCheck they are current before replying
- Owner
- ReceptionHuman decision pending
Pick up the request
Guest service checks the context and prepares a response. If the request requires a hotel decision, it is passed to a person with the necessary information.
Reception confirms the arrival procedure. This example does not accept bookings or send a response to the guest.
- Profile
- Example stayService context available
- Permission
- No marketing consentNot inferred from WiFi access
- Journey
- Excluded from campaignReview contact preferences
Prepare the next contact
The relationship can continue after the stay if preferences allow it. The team reviews eligibility and the message before activating a journey.
Exclude the contact without marketing permission from the campaign while keeping requested service available.
Manual exploration. These scenarios do not send messages or change any hotel data.
Small details. Connected work.
Start with the tasks that currently depend on remembering a conversation or searching several screens.
Recognise with context
Connect WiFi access and available stay data with the guest profile. Review matches before using them in a conversation.
WiFi → CDP · depending on connected sourcesKeep care continuous across shifts
Keep the request and its context in a service workspace so the person taking over knows what remains to be resolved.
Concierge → team · human handoffPrepare the return with permission
Distinguish having served someone from being able to send them marketing. Prepare segments and messages using the relevant preferences and conditions.
CDP → Marketing · separate consent
Before taking the first step.
Do we need to replace the PMS?
We start by reviewing your PMS and existing sources. The data that can connect depends on the provider and configuration; we do not assume universal integration.
Does a WiFi contact allow campaigns?
Having contact data is not the same as having marketing consent. The team must separate providing the service from preferences for receiving communications.
Where can a small team start?
Choose a concrete friction point, such as finding the context of a request. In the demo we review the sources, who will handle the case and which module supports that first workflow.
Let’s talk about your welcome.
Tell us how context reaches reception and where it gets lost. We will focus the conversation on the guest profile and your personal service.
Request a demo for my boutiqueExplore other solutions