Guest e-mails are mostly the same twenty questions — availability, prices, parking, check-in times, cancellations — mixed with a few that really need a person. An AI e-mail assistant is built to handle the first kind instantly and pass on the second kind. This page explains what such a tool should do, what to check before you buy, which questions to ask vendors, and how to introduce it without risking your guests' trust.
What an AI e-mail assistant is (and is not)
It is software connected to your reservation mailbox. It reads incoming guest e-mails, understands what each one is about, and writes a reply using your hotel's information — then either sends it or leaves it as a draft for staff. It is not the same as pasting e-mails into a general chatbot: there is no copy-paste, the rules are the same for every reply, and it works when nobody is at the desk. If you are comparing the two, read how to use ChatGPT to answer hotel e-mails.
What it should do
- Read the inbox. Pick up new e-mails without anyone forwarding them, and ignore spam, newsletters and automatic notifications.
- Understand the type of inquiry. A new booking request, a change, a cancellation, a question before arrival, a complaint and an invoice request need different handling.
- Use your facts, policies and availability. Answers must come from your hotel's information — times, prices, cancellation terms — not from general knowledge. Ask how the tool gets availability and rates, and how up to date they are.
- Reply in your tone and the guest's language. A family hotel and a business hotel sound different. Guests write in many languages and expect a reply in theirs.
- Hand over complex cases. Complaints, groups, special requests, payment disputes and anything it is unsure about go to staff — clearly flagged, with a summary.
- Log everything. You should be able to see every e-mail it received, what it answered or why it handed over, and when.
Example: a routine question answered, a complex one handed over
An illustrative example. The first e-mail is answered from the hotel's own facts; if the guest had asked for a wedding block of twenty rooms, the assistant would instead have passed it to staff.
Guest e-mail · Late arrival on Friday
We arrive on Friday around 11 pm after a late flight. Is the reception open that late, and can we still get dinner anywhere nearby?
Best regards,
Sara
Reply drafted by BookingWatch
Thank you for letting us know — a late arrival is no problem.
Reception is staffed until midnight, so we'll be here to welcome you. If your flight is delayed beyond that, just reply to this e-mail and we'll arrange a key code for you.
Our restaurant closes at 10 pm, but the pizzeria on the harbour square, two minutes' walk away, is open until 1 am on Fridays.
Have a good trip, and see you on Friday!
Warm regards,
Anna
Hotel Seaview
Checklist: what to look for when choosing
| Area | What to look for | Why it matters |
|---|---|---|
| Accuracy controls | Answers only from your facts; says "I don't know" or hands over rather than guessing | A confident wrong answer about price or cancellation terms costs more than a slow reply |
| Approval mode vs auto-send | Can run in draft mode; auto-send can be switched on per topic | Lets you build trust gradually |
| Handover to staff | Clear rules for what goes to a person, with notification and summary | Complaints and exceptions need human judgement |
| Availability and prices | How the tool knows what is free and what it costs, and how fresh that is | Most booking inquiries are about exactly this |
| Languages | Replies in the guest's language, with your tone kept | International guests expect it |
| GDPR and data processing agreement | Signed data processing agreement, list of sub-processors, retention period, no training on your guests' data | Required when a vendor processes guest data for you |
| Data location | Where e-mails and data are stored and processed (EU or not) | Affects transfers under GDPR and your guests' trust |
| Setup time and effort | Realistic timeline; what you must provide; whether you keep your booking engine and PMS | A small hotel cannot run an IT project |
| Pricing model transparency | Published prices, what counts as a billable unit, setup fee, binding period, cap | So the bill does not surprise you in high season |
| Log and reporting | Every e-mail and reply visible; response times; handover reasons | You stay in control and can improve the rules |
Source: GDPR Article 28 (Processor), gdpr-info.eu, retrieved 2026-10-07
Questions to ask every vendor
- Show me what happens when a guest asks something that is not in our information. Does it guess, ask, or hand over?
- How does the tool know our availability and rates? How often are they updated?
- Can we start with drafts only, and later switch on auto-send for selected topics?
- Which topics are always handed to staff by default? Can we change the list?
- Can we see a log of every e-mail, reply and handover?
- Will you sign a data processing agreement? Where are data stored and processed, and which sub-processors do you use? Is our guests' data used to train AI models?
- How do you handle transparency about AI — for example, telling guests that a reply was written with AI, if we want or need to? (The EU AI Act includes transparency obligations in Article 50; ask how the vendor addresses them.)
- What do we need to provide, and how long until the first real replies?
- What will it cost at our e-mail volume in low season and in high season? Is there a setup fee, binding period or price cap?
- Who built it, and have they run it at a real hotel?
Source: EU AI Act, Article 50 (transparency obligations), artificialintelligenceact.eu, retrieved 2026-10-07
How to roll it out safely
Week 1–2: drafts only
Connect the inbox and let the assistant write drafts that staff read, edit and send. Write down every correction. Most corrections point to a missing or unclear fact — fix the fact sheet, not just the e-mail.
Week 3 onwards: auto-send for simple topics
Switch on automatic sending for questions with clear, stable answers: directions, parking, check-in and check-out times, breakfast, availability inquiries for standard rooms. Keep drafts or handover for the rest.
Always handed to staff
A suggested starting list, which you can adjust:
- Complaints and unhappy guests
- Group bookings, events and conferences
- Requests for exceptions to policy: refunds outside terms, discounts, special agreements
- Payment problems, invoices to companies, disputes
- Anything involving health, safety or legal matters
Every week: sample and adjust
Read a handful of sent replies and all handovers. If a topic keeps going to staff with the same answer, add the answer to the facts. If a reply went wrong, narrow auto-send for that topic until it is fixed.
Where BookingWatch fits
BookingWatch is one option, built by hotel owners for their own hotels. It connects to the reservation inbox, answers guest e-mails in seconds day and night using the hotel's own facts and rules, can write drafts you approve before sending, and hands cases to staff when a person is needed. Your booking engine, channel manager and PMS stay as they are. Pricing is a monthly fee with a number of answered e-mails included, a charge per additional answered e-mail and a monthly price cap, with no binding period or setup fee — current prices are on the pricing page. To estimate what slow replies cost you today, try the lost revenue calculator.
Common mistakes
- Switching on auto-send for everything on day one.
- Feeding the assistant outdated or incomplete hotel information — and blaming the AI for the answers.
- No clear handover rules, so complaints get a cheerful standard reply.
- Choosing on demo impressions alone without testing your own real (anonymized) e-mails.
- Skipping the data processing agreement and data-location questions.
- Not reading the log after go-live. The first weeks are when you learn the most.
- Comparing monthly prices without checking what happens at high-season volume.