Be there for every part of the stay
Build guest message sequences around stay events, with the right language, useful details and a delivery history your team can understand.
Automated guest messages, with Sixto
Make the journey feel connected
Organize messages around stay events and timing. Conditions determine which stays belong in each sequence.
- Event-based timing
- Eligibility conditions
Write once, make it specific
Templates bring supported stay variables into your message. Preview the actual rendering before approving the text.
- Guest and check-in links
- Language and stay preview
Find the reason behind a missed message
See the planned time, eligibility, skip reason and delivery result. Resolve delivery ownership so the right system sends the message.
- Approval and enabled state
- History for the intended stay
What Sixto does, and what stays with you
Alex receives a welcome before arrival and useful instructions later in the stay. The team sees which message was sent and which is still waiting for its event.
Also included
Before you start
An enabled automation did not send.
Enabled does not mean every stay qualifies. Check the event, current stay facts, approval, connection and existing delivery before retrying. A dry-run entry is not delivery.
What should I verify?
Verify the rendered message and delivery history for the intended stay.
What does not happen automatically?
A preview sends nothing. Unsupported variables must be resolved rather than replaced with private codes or credentials.
More about Automated guest messages
Scope Sixto brings reservations, guest check-in, SIRE, TRA and DIAN invoicing workflows together for Colombian hospitality teams. Manage channel connections with Sixto, coordinate guest verification, compatible smart locks, cleaning, staff hours and finance. Reporting, invoicing and connected services require the relevant setup and permissions.
How it works, step by step
Automated guest messages
Review what will be sent, when it is eligible and which system owns delivery.
- Open Messages and select the relevant sequence or template. Check the stay event, timing, conditions, language and delivery ownership.
- Edit supported text and variables. Use the preview with a specific stay to check names, times and guest/check-in links.
- For a missed message, inspect its planned time, eligibility, skip reason and delivery result. Correct the cause before using the supported retry action.
The stay’s message history shows the rendered content and whether the message was delivered, skipped, failed or is still planned.
A preview sends nothing. Unsupported variables must be resolved rather than replaced with private codes or credentials.
One tool instead of five
Hosts switch to Sixto from a PMS, a compliance tool like Hospy, separate accounting software and a lock app. Everything shares the same guests, bookings and books.