Why does a guest complaint queue behind routine questions?

The question this file answersHow many of the messages my front desk answers every day are the same handful of questions — and why does the complaint still queue behind them?

Fits: hotels and small groups handling 50–500+ guest enquiries a day across email, OTA messaging and WhatsApp, with a PMS that holds live availability; in the composite, a five-property group answering in four languages.

Not for: properties where enquiries are a handful a day and the owner answers them personally — the volume is not there to remove — or where most messages are group and event requests, which stay with a person.

Typical day

What the desk looks like today

Typical, from the hospitality playbook — not a client's day. A mid-size hotel or small group takes 50–500+ enquiries a day across email, Booking.com messages, WhatsApp and the phone. Whoever is on the desk reads each one, checks dates in the PMS, finds the parking or check-in policy, writes yesterday's paragraph again and logs it between check-ins. It hurts twice: in high season, when enquiries double but the desk does not, and after every staff change, because the answers live in heads, not documents. The guest with a real problem waits behind the availability questions.

What changes

What Monday looks like after

Sunday evening, after the last check-in. The desk opens the enquiry queue and finds the availability and parking questions already answered from the PMS, each reply logged against the guest. What remains is a change request waiting for a confirm, two complaints, and the returning VIP who wrote in French — the messages a person should have been reading all along. In the morning the manager can see, per channel, how many enquiries went out without staff and which ones the desk touched. Nobody leaves the desk; the retyping of the parking policy does. Revinate's figure below covers routine enquiries only; upselling, packages and events are not in it.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

~50–65%

of guest enquiries handled without staff — Revinate (2023)

Before: staff retype availability and policy answers while a complaint sinks in the queue. After: Revinate (2023) reports 50–65% of guest enquiries handled without staff — VIPs and complaints go to a person first.

Where this number comes from

Revinate 'Hotel Guest Communication' (2023) reports AI-powered messaging handling 50–65% of guest enquiries without staff intervention; an industry range, not our measurement. Playbook range 45–65%. Not a conversion or revenue claim.

What we install

What we put in front of the systems you already run

Your PMS stays — Opera, Mews, Cloudbeds, Protel or the one you run. In front of the desk we add a messaging step that reads the PMS:

each message from email, the OTA extranet and WhatsApp is sorted — availability, price, a booking change, a complaint, a VIP name
availability and house-rule questions are answered from live PMS data and your written policies, in the guest's language
in-policy changes are drafted for a one-click confirm, not sent
complaints and VIP names go to a named person with the thread attached — nothing is auto-sent there
pre-arrival information goes out on your schedule.

With a PMS API we connect directly; an email-only property starts with the inbox. First scope: your three most repeated question types.

What stays human — and what this will not do

VIP guests. Complaint resolution. Upselling a complex package. Coordinating a special event. Anything that is not a rate and a date.

Not a conversion or revenue claim.

What can go wrong — and what we do about it

House rules that live in people's heads produce wrong answers in writing — if policies are not written down, the audit starts by writing them, and nothing goes out before that. Without a PMS API, availability comes through the vendor's connector; on email-only properties we sort and draft but do not confirm dates. A complaint phrased politely reads as a question, so anything with a booking reference and a negative word goes to a person, not a guess. The 45–65% range covers routine enquiries; group requests, packages and events stay manual.

How long it takes, and what we need from you

Audit, about two weeks (€1.5–3K): we read a month of enquiries with the desk, count them by channel and question type, and check what your PMS exposes — an API, a messaging integration, or only the screen. Pilot, 2–4 weeks (€10–20K; low-to-medium complexity in the hospitality playbook): one property, the top question types, every draft reviewed before any auto-reply goes live. Production: more properties and languages, complaints still routed to a person. From you: mailbox and extranet access, written house rules, the VIP list.

The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →

This is about you if…

Do guest questions arrive as free text across email, OTA messages and WhatsApp?
Does someone on the desk look up the PMS and retype the answer for each one?
Does your PMS hold live availability and policies a system could read?

What does this mean in euros?

That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.

Get your free savings estimate 60 seconds · no sales call Or write first → Map an ops process like this one — free, 60 seconds →

Not a named Aperanda client. Process file · Ops.

Deep-dive process file. Volumes, weeks and sources come from the industry playbook; nothing here is a named client.

All process files