Travel confirmations
that travel with the guest.
Travel bookings end with a templated email nobody trusts. The guest emails back asking about parking, check-in time, dietary needs — and gets crickets. A Loomal agent sends real confirmations from a hotel or operator identity, and stays in the thread to handle every question until check-in.
API Primitives used
mail.sendSend a real confirmation
Confirmation goes from a real property identity, not a no-reply booking platform.
mail.list_messagesCatch guest questions
Pre-arrival questions come in as replies. Agent reads and classifies each one.
mail.replyAnswer in-thread
Most questions get answered immediately; complex ones route to the property team with full context.
Booking confirmations are dead emails.
Hotels and travel operators send confirmations through booking platforms that own the relationship. The guest never gets to talk back. Every pre-arrival question turns into a phone call or a no-show, and the property has no way to be helpful at the moment it matters most.
An agent flips the model. The confirmation comes from the property's own identity, the guest can reply with questions, and the agent answers — all the way to check-in.
How to build it.
mail.sendSend the confirmation
Agent sends the confirmation from the property identity with all the practical details — directions, check-in, parking, contact.
mail.list_messagesWatch for questions
Agent watches for guest replies and classifies them — logistics, special requests, cancellations.
mail.replyAnswer in-thread
Most questions get instant answers from a curated knowledge base. Anything unusual routes to the property team.
Example prompt
“For every booking from our PMS, send a real confirmation from my hotel agent. Answer guest questions about parking, check-in time, and breakfast in-thread. Escalate dietary requests to the kitchen.”
What hotels build.
Hotel pre-arrival
Guests get a real confirmation and a real conversation channel for the days before arrival.
Tour operator bookings
Tours get pre-trip prep messages and answer trip questions in-thread.
Restaurant reservations
Diners can confirm dietary needs and special occasions with the restaurant directly.
Vacation rentals
Hosts use agent identities to handle the dozens of pre-stay questions every booking generates.
Multi-property chains
Each property runs its own identity for clean local relationships.
Why hospitality needs a real identity.
Every hotel knows guests want a relationship, not a transaction. But the platforms that handle the booking won't let the property own the conversation. An agent identity flips that — the property gets a real inbox, a real sender, and a real path to talk to its guests directly.
Loomal makes that practical at hospitality scale. The agent answers most questions, escalates the unusual ones, and audits every interaction against the property identity.
Guest data internal
Guest conversations live in the property's own inbox, not a third-party booking platform.
Per-booking audit
Every send and reply is logged with the property identity.
Identity per property
Each property in a chain runs its own agent identity for clean separation.