Sixto
EN
EspañolEnglishPortuguês
See demo
Explore every Sixto workflow

Automated guest messages

Plan guest messages around a stay event, its timing and eligibility conditions. Preview the rendered content for a specific stay, then use the delivery history to distinguish planned, skipped, failed and delivered messages.

Before you start

Viewing templates does not grant editing, approval or sending permission. Live delivery needs a supported ready connection.

  1. Open Messages, choose the sequence or template and read its stay event, timing, eligibility conditions, language and delivery ownership. Conditions determine which stays qualify, so timing alone does not mean a message should be sent.

    Choose the event and timing
    Automated guest messages
    1 / 3
    Before arrivalBefore · Planned
    Arrival dayArrival · Planned
    Before departureDeparture · Planned
    Garden studioAlex Rivera · A-104
    3 nights
    Message templateDraft
    Stay event and timingBefore arrival
    Guest languageEN
    Sequence
    Stay event and timing

  2. Edit the supported text and variables, then preview a specific stay to check names, times and guest or check-in links. Reviewing substituted values helps catch information that looks correct in a template but wrong for the guest.

    Preview the actual message
    Automated guest messages
    2 / 3
    AR
    Alex Rivera10:05Here is your stay link with registration and house information.Garden studio
    S
    Sofía09:20Before arrivalGuest
    GuestHere is your stay link with registration and house information.
    Not sent
    Garden studio23 Oct → 26 OctSigned stay link
    Guest preview · EN
    Stay preview
    Rendered names, times and links

  3. Read the planned time, eligibility and skip or failure reason before retrying. Correct the cause through the supported action so a retry addresses the actual problem.

    Trace a missed delivery
    Automated guest messages
    3 / 3
    Garden studioAlex Rivera · A-104
    3 nights
    10:05
    Welcome message

    Delivery result recorded

    Sent
    Later
    Departure reminder

    Planned for the departure event

    Planned
    History
    Planned, skipped, failed or delivered

Check the result

The stay’s message history shows the rendered content and whether the message was delivered, skipped, failed or is still planned.

Limits and prerequisites

A preview sends nothing. Unsupported variables must be resolved rather than replaced with private codes or credentials.