Reach out at the appropriate moment, or only while a connected source still shows that something needs attention. StayAssist can speak with the guest, understand the response within the workflow's scope and carry the result forward.
A missing detail, incomplete external step or unanswered confirmation can leave the team checking stays and repeating the same contact. Static reminders may continue after the item is complete, while a question, refusal and no answer can each require a different next step. Guest Reminders gives that follow-up a consistent path without removing local judgment.
Use relevant stay or operational context so the prompt is about the item that still needs attention.
Place the reminder at a chosen time, relative to the reservation or within the communication window that fits the situation.
Keep the contact outcome and guest response visible so the next step does not depend on someone reconstructing the exchange.
Repeatable follow-up does not remove judgment. It makes the routine path clear and gives exceptions somewhere deliberate to go.
Some prompts belong at a known moment. Others should happen only while a current status still shows that the step needs attention.
The time says when to remind.
Contact the guest at a chosen time or a moment relative to the reservation. Communication windows, the relevant timezone and guest or property Do Not Disturb rules help keep contact appropriate.
Current status can tell the workflow whether the reminder still makes sense.
Where the workflow can access the relevant current status, check whether the item still needs attention before contact or later follow-up. If the source shows that the step is complete, the reminder path can stop or take a different configured route.
Current status depends on provider data and permissions. StayAssist does not always know when a step is complete, and this is not continuous monitoring.
Guest Reminders can prompt a guest about an operational item the property is waiting for. The connected payment, form, registration or access process remains responsible for completing it.
Ask for or remind the guest about arrival details that the operation still needs.
Where the current status shows that attention is still needed, remind the guest to complete the step through the property's established payment process.
Prompt the guest when an externally owned form, registration or document step still shows as incomplete.
Ask the guest to confirm an arrival, in-stay or departure detail the operation still needs, then keep the response or no-answer outcome with the reminder.
StayAssist does not collect card details, process payment, validate ID, submit forms, perform legal registration or provision keys and access.
See Check-in & Checkout conversationsAn outbound voice reminder lets the guest respond in the moment. StayAssist can use the relevant context, understand the response within scope, ask a useful follow-up, capture information and recognize when the team needs to become involved. Outbound messages can begin or continue the path where the channel is available.
Keep the acknowledgment, information, refusal or question that matters to the reminder.
Clarify what the guest means or collect information the reminder path needs, without implying unlimited understanding.
Answer within the prepared knowledge and scope, or bring in the team when judgment, approval or an externally owned action is needed.
Voice is conversational. SMS and WhatsApp are outbound only in the current model; OTA/PMS messaging depends on the provider.
A sent reminder is not the useful endpoint. The operation needs to distinguish what the guest said, whether nobody answered and what a connected source still shows about the item.
Keep the acknowledgment, refusal, question or information the guest provided. A statement that the step is complete remains a conversational result unless the underlying source confirms it.
Keep no answer as a distinct contact outcome. The reminder can follow a later attempt or team path where configured, without assuming one universal retry sequence.
Where current status is available, keep the unresolved item distinct from the contact outcome. A guest may respond while the external step still needs attention.
Workflow Follow-Through can carry a guest response, no answer, an item that still needs attention or a request for team help into the next configured operational step.
The next step may be another guest contact, a team step, another workflow or a supported connected action. The destination and its result depend on the setup and provider.
The guest is reminded that standard check-in begins at 15:00. If early check-in is an option for that stay, StayAssist can introduce it as a separate next step.
Keep the operational result - acknowledged, no answer or still outstanding - separate from commercial interest, acceptance or decline. Availability, approval, booking and payment are not implied.
Explore Revenue WorkflowsUse the same reminder approach across a portfolio while timing, local instructions and team paths remain appropriate to each property.
Review what happened after the reminder: the contact attempt, guest response, no answer, known status, team continuation and how the reminder path ended.
StayAssist can prompt guests about stay-related steps such as missing arrival information, a requested operational confirmation, or a deposit, payment, form or registration step that still needs attention. What the workflow can know depends on the connected source and setup.
Yes, when the relevant provider exposes a current status the workflow can use. The reminder path can check that status and stop or change course when the source shows that the step is complete.
Yes, during an outbound voice call. StayAssist can hold a two-way conversation, use relevant context, ask a follow-up and continue according to the guest's response. SMS, WhatsApp and OTA/PMS messages are outbound channels where available, not inbound guest chat.
No answer is kept as its own contact outcome. The reminder may continue to a later attempt, another outbound channel, a team path or a stop where configured. There is no universal retry cadence or guaranteed contact.
Yes, as outbound messages where the provider, region, template and setup support them. OTA/PMS messaging depends on the connected provider and its available API operations.
Yes, when a provider-supplied status shows that the step still needs attention. StayAssist can remind the guest to use the property's established process; it does not itself collect card details, process payment or create a payment flow.
Workflow Follow-Through can carry the result into the next configured operational step, such as another guest contact, a team path, another workflow or a supported connected action. The destination and what it can do depend on the setup and provider.
Tell us what guests need to complete, when the reminder should happen and what should shape the next operational step.
