Use cases · Customer support

Pre-arrival guest messages

Send each guest a short pre-arrival message built from their booking and your approved property information, such as check-in details, directions and add-on options, so the front desk handles fewer routine questions on arrival day.

Where it starts

The trigger.

A booking reaches the agreed number of days before arrival.

How it runs today

  • Guests ask the same arrival questions by phone, email and chat.
  • Pre-arrival emails are generic or are not sent at all.
  • Special requests in booking notes are missed until check-in.

The workflow

Four bounded steps.

Each step has an owner and a stop rule.

  1. 01 / Read

    Read upcoming bookings and the approved property information for each stay type.

  2. 02 / Draft

    Draft a short message with check-in details, directions and relevant options in the property’s template.

  3. 03 / Flag

    Flag special requests, accessibility needs and unusual bookings for staff before anything is sent.

  4. 04 / Send

    Send approved messages on schedule and route guest replies to the reservations team.

Where people stay in control

Approval points.

  • Staff handle special requests, accessibility needs and any booking changes.
  • Messages use only approved property information and the guest’s own booking details.

How we would measure it

Against a baseline.

Measured before and after, on the same work.

Routine arrival questions per stay.

Share of bookings that receive a pre-arrival message on time.

Special requests flagged before arrival day.

Related

Go deeper.

More use cases

Other places to start.

All use cases

An illustrative workflow pattern, not a result from a specific customer.

Bring the messy version

One workflow.
A better way to run it.

Show us the tools, the handoffs, and the part that keeps slowing your team down.

Explore with AI

What would you like help with?

Get the main points in plain language.

Continue with

Includes this page title and canonical URL. The prompt is copied before the provider opens; supported providers also receive it through the URL.