Journeys
SayGoodbyetoRoboticAutomatedMessaging
The first automated messaging system that knows every message already sent, every message scheduled, and every condition blocking the next one - so your AI can explain the full timeline when guests ask.
Rotate for a sneak peek
Turn your phone sideways to preview Journeys, or book a live walkthrough.
AI-Aware Automated Messaging
The AI That Knows Every Message, Past and Future
Every other tool sends messages on a dumb timer. Besty's AI reads the entire journey timeline before replying - every message already delivered, every message scheduled to go out, and every condition gating the next send. When a guest asks where their check-in instructions are, the AI responds with the exact date they're scheduled.
When they ask for their door code, the AI sees it's gated on the rental agreement, tells the guest what's blocking it, then fires the code the moment they sign - all automatically. This isn't a chatbot bolted onto a drip sequence. The AI and the automated messaging share one timeline, one system.
Full Timeline Visibility
The AI reads every message already sent, every message scheduled, and every condition blocking future sends - before composing a single reply.
Condition-Aware Responses
When a guest asks for their door code, the AI checks whether the rental agreement is signed. If not, it tells them exactly what's blocking it.
Automatic Trigger on Completion
When a guest signs their rental agreement, Besty triggers the gated door code message within the hour - no manual action required.
Specific Answers, Not "We'll Follow Up"
Guests asking "when do I get check-in instructions?" get a date, not a placeholder reply. The answer is in the scheduled timeline.
One Unified System
The AI and the automated journey share a single data model. There's no chatbot bolted onto a drip sequence - past, present, and future messages are all one context.
March Booking - Sarah Chen
Arrival Mar 15 · 4 nights · Airbnb
Booking Confirmation
EmailRental Agreement
EmailCheck-in Instructions
EmailRental agreement signed ✓
Check-in Reminder
SMSDoor Code
SMSRental agreement signed - required
Checkout Reminder
Email2 sent · 2 scheduled · 1 gated · 1 pending
Besty AI
Aware of your full journey timeline
Try a guest question
Select a question above to see the AI respond with full timeline awareness.
AI checked 6 journey messages before responding
Journey Builder
One Sequence per Guest Segment, Not Dozens of Disconnected Automations
A journey groups your entire messaging lifecycle - booking confirmation, rental agreement, check-in instructions, mid-stay check-in, and review request - into a single consolidated flow. Journey Settings control which reservations enter: filter by listing set, stay type, booking source, and advance notice window. Need a variation for last-minute bookers? Duplicate the journey, adjust the targeting, done.
6 messages · 2 channels
Guests book ≥ 3 days out · Airbnb & VRBO · Guest stays only
Click any step to inspect · All 6 messages in one consolidated flow
Journey Settings
3 rules activeReservations must match all enabled rules to enter this journey.
Toggle rules · Changes apply to new reservations only
Duplicate & Adjust
Clone an entire journey, update the targeting rules, and you have a clean variation - no rebuilding content from scratch.
Beach Portfolio Journey
Airbnb · Guest stays · 6 messages
1
journey replaces 8+ individual automations
Booking confirmation, agreement, 2× pre-arrival, mid-stay, checkout, review request - all in one flow with shared content.
Per-step
timing and channel control
Each message inside a journey has its own send time, channel selection, and optional condition gate - independent of every other step.
Booking Source Filtering
Include or exclude specific OTA channels per journey. Run a different flow for direct bookings vs Airbnb guests without duplicating all your content.
Advance Notice Windows
Gate entire journeys on how far out a guest booked. Guests booking same-day skip the 3-day pre-arrival sequence and enter a condensed last-minute flow.
Listing Set Targeting
Group listings by property type - keyless vs office check-in, pool homes vs condos - and assign the matching journey to each set.
Stay Type Exclusions
Exclude owner stays, blocked periods, or specific reservation types so operational holds never trigger a guest-facing message sequence.
Every Channel · 03
One Journey Delivers Across Email, SMS, WhatsApp, and OTA
Each message in a journey selects its own channel - email for the rental agreement, an SMS nudge pointing guests to their inbox, OTA messaging for the mid-stay check-in on the platform they booked through. You write a separate version of each message per channel so SMS stays short and link-free while email carries the full detail. One journey, every guest reached where they actually check.
Mountain House - Standard Stay
6 messages · Email, SMS, OTA
Rental Agreement
1 hour after booking
Send via
Subject
Action required: sign your rental agreement
Please complete your rental agreement before your stay. Once signed, we'll automatically send your check-in instructions: {{rental_agreement_link}}
Link goes in email only - SMS drives opens, avoids broken mobile links.
Select any step to inspect its channel configuration · Each message is independently targeted
Email with full detail
Send rental agreements, check-in packets, and review requests with links, attachments, and rich formatting - the channel that handles everything.
SMS that actually lands
Short, link-free SMS messages that nudge guests to check their email - not broken links that confuse people on mobile. Each SMS is written separately from its email counterpart.
Native OTA messaging
Mid-stay check-ins and post-stay review requests fire through Airbnb, Vrbo, or Booking.com - the platform the guest used to book, not a channel they have to check separately.
WhatsApp for global guests
International guests who rarely check SMS or email get messages where they actually read - WhatsApp, configured per message, same journey.
Per-message channel control
Every step in a journey picks its own channel. One step can hit email + SMS. The next can go OTA-only. You don't pick a channel for the whole journey - you pick it message by message.
PMS Integration
Every PMS Event Wired Directly Into Your Journey
Besty mirrors your PMS one-to-one - every reservation event, every custom field, every variable available as a trigger or condition in your journeys. When a booking lands, a payment clears, or a rental agreement is signed, the right message fires automatically with every data field already populated.
Template tokens like {Unit_Code}, {Customer_First}, and {Reservation_ChargesPayments} pull live from your PMS into every message. Click any event below to see it in action.
{Customer_First}, your door code is {Unit_Code}. Check in at {Unit_Address1} - {Unit_Bedrooms} bed, {Unit_Bathrooms} bath.
PMS fields used
Available fields: Customer_First · Unit_Code · Unit_Address1 · Reservation_ChargesPayments · Admin_UnitName · Unit_Bedrooms · +40 more
Every Reservation Event
Booking created, payment received, agreement signed, balance due, check-in, check-out - every event your PMS emits maps to a trigger you can act on.
Custom Field Variables
Any field you've built in your PMS - unit code, property address, balance schedule - becomes a {Variable} token that populates live into message templates.
Complete Data Mirror
Every reservation field, guest record, and unit attribute in your PMS is mirrored and queryable in Besty - not a subset, the full data model.
Replicate & Extend
Recreate every automation you had in your old PMS, then build new ones gated on field combinations - like releasing a door code only after both payment and agreement are complete.
Smart Timing
The Right Message Fires When the Data Says So
Timing in Besty adapts to each booking. Guests who book 3+ days ahead get check-in instructions at T-3 and T-1; last-minute bookers receive them 1 hour after confirmation. Every message can also be gated on conditions - balance paid, rental agreement signed, or any PMS field - so nothing sends until the guest is actually ready.
Event-based triggers take it further: one hour after the rental agreement is signed, Besty fires the door code automatically. All of this runs inside a single journey - no splitting into dozens of micro-automations to handle edge cases.
Lead-Time Adaptive Timing
Guests booking 3+ days out get check-in instructions at T-3 and T-1. Last-minute bookers get the same message 1 hour after confirmation - automatically.
Data-Gated Conditions
Gate any message on real PMS data: balance paid, rental agreement signed, or any custom field. The message simply won't fire until the condition is true.
Event-Based Triggers
Fire messages off real actions. One hour after the rental agreement is signed, Besty automatically sends the door code - no polling, no manual follow-up.
One Flow, Not Dozens of Micro-Automations
Conditional steps live inside the same journey. You don't need a separate sequence for every guest scenario - the logic is per message, not per flow.
Pre-Arrival Journey
5 messages · 2 channels
Booking Confirmation
Email + SMS
Rental Agreement Request
Check-in Instructions
Send only if…
Door Code + Access Details
EventSMS
Day-Before Reminder
SMS
Click a step to see its send conditions · Toggle lead time to see adaptive timing
At a glance
Automated messaging that actually understands your guests
0 channels
Email, SMS, WhatsApp, and OTA messaging - all from one journey
0%
PMS triggers and custom fields mirrored one-to-one in Besty
0 conditions
Per-message gates: balance paid, agreement signed, custom field set
0 dumb timers
Every message is AI-aware - the bot knows what's sent, what's next, what's blocked
Besty Journeys
The only automated messaging that knows what it already said
Every guest gets the right message, on the right channel, at the right time - and the AI can explain the entire timeline if they ask. Set up your journeys and stop babysitting your automations.