Key Findings

  • Across a 30-day sample of inbound guest messages on Akia, most messages work out of the box: wifi codes, parking, check-in times, breakfast hours, late-checkout requests, and policy questions. The AI agent handles these the day you turn it on.

  • Messages get sharper with training — multi-step requests, edge cases, property-specific judgment calls. This is where an agent earns its name. A chatbot can't do this work. An agent that learns your property, your policies, and your tone can.

  • A few stay with your team on purpose — active complaints, refund disputes, sensitive escalations. Not because the AI can't try, but because someone's reputation, safety, or money is on the line and the right answer is a human voice.

How much of your staff's day is spent answering things AI could handle in seconds.

A guest texts at 9:47pm asking for the wifi password. Three minutes later, another guest asks where to park the rental car. At 11:14am, two minutes after a front-desk agent finally sat down, a third person asked for the gate code because their flight was late.

None of these messages needed a person. Each one has a single correct answer, written somewhere in a binder, a PMS field, or the property's website.

When we looked across a 30-day sample of inbound guest messages flowing through Akia, four out of five were asking for information that already exists. Not the kind of conversation where a human voice changes the outcome. Just what a guest needed at that moment.

What separates an AI agent from an FAQ bot is what happens with the messages where the answer isn't sitting in the knowledge base.

How we categorized messages.

We bucketed messages by two questions, then mapped them onto a 2x2.

The first question is whether a single correct response exists somewhere in a knowledge base, policy doc, or PMS field, or judgment-based, meaning the right response depends on context, history, or the specific guest in front of you.

The second question is the stakes: low (no real downside if the response is wrong) or high (reputation, safety, money, or a guest who is already upset).

Those two axes give you four quadrants. Three of them, anything factual at any stakes, plus low-stakes judgment calls that can be resolved with a clear policy, are AI work. One of them, high-stakes judgment, is human work.

What we saw was the same thing everywhere we looked. Across thousands of properties, most of what guests are asking are the same questions, over and over.

But "AI handles it" isn't one thing. It splits into two tiers: the work that's ready on day one, and the work that gets sharper as the agent learns your property.

## Tier 1: What's ready on Day 1.

Four categories do most of the work.

Information from your PMS or website - automatically available.

Logistics and arrival: Check-in times, addresses, gate codes, wifi passwords, parking. Every property's knowledge base has the answer.

Service requests: Extra towels, more pillows. These are tasks to route to housekeeping. An AI agent can read the request, create the housekeeping task, and confirm with the guest in the time it takes a human to glance at their phone.

Compliments and thanks: "Loved our stay." "Perfect weekend." None of these need a person, but if no one responds, the guest feels ignored. Freeing staff from typing "we're so glad!" Forty times a week isn't a small recovery.

Time-flex requests: Early check-in, late checkout, and extra night. The answer is often "yes, for a fee." A well-configured AI agent quotes the policy, applies the upcharge, and closes the upsell while the guest still has their phone in their hand.

Other categories include amenities, local recommendations, booking policy, and pet and kid logistics.

Tier 2: Where agents earn their name.

The middle tier is where the difference between an FAQ bot and an AI agent actually shows up.

Message like: "We had a really late night. Any chance we can stay until 2pm before heading to the airport?"

A chatbot pattern-matches on "checkout" and either replies with the standard 11am checkout time (missing the request entirely) or gives a flat "yes/no" without checking anything.

An AI agent reads the reservation, checks whether the room is booked again that afternoon, applies the property's late-checkout policy (free until 1pm, $30 after), confirms with the guest, and updates the housekeeping schedule so the room isn't flagged for an 11am turn.

The agent has to learn your property's specific policies and team's escalation patterns.

A few examples of what lives in this tier:

  • "We're running 30 minutes late, will the kitchen still be open?" (Reads the F&B hours, checks against ETA, offers an alternative if the kitchen will close, holds a reservation if it won't.)

  • "My partner has a peanut allergy. Is breakfast safe?" (Looks up dietary information, confirms with kitchen contact if uncertain, escalates if the answer isn't definitive.)

These messages can quietly eat up most of your front desk's time, because they require pulling information from three different systems and making a small judgment call. But this is what an agent does that a chatbot doesn't.

Tier 3: What stays with your team on purpose.

The last tier is where you should lean on your team. Active complaints, refund disputes, in-progress room issues, and any message that names a staff member or describes how a guest was made to feel, these aren't knowledge-based questions. A bot fumbling is how you end up with angry reviews and refunds you didn't need to give.

Akia's view: this should escalate to a human. And when it does, the staff knows exactly what's been said, who said it, and what they need next.

AI agent needs this to be useful.

A real agent does four things a chatbot can't:

Pulls live context. It reads the PMS, the reservation, the property's website, and the room status in real time.

Handles multi-step work. Agents can read a reservation, check housekeeping availability, apply a policy, execute a PMS update, and reply to the guest.

Knows the difference between similar messages. "What is my door code" is a different question than "I'm at the door and the code isn't working." Same words, different intentions, different actions. An agent reads the situation; a chatbot reads the keywords.

Escalates with full context. When a human is needed, it hands them off with a summary, the steps already taken, and what the human needs to do next. It's understanding "when the AI hands off, does my team have what they need to be useful?"

## What operators should do.

Two moves before you go shopping for a tool.

Start with the most repetitive questions. Automate the type of question that comes up most, regardless of where it lands. Start with logistics and amenities (wifi, parking, check-in times). Then layer in policy questions like early check-in and late checkout. That order gets you most of the time savings in the first few weeks.

Protect the 5% deliberately, and judge it on handoff quality. Configure the system so complaint language, refund language, and health-and-safety always escalate to a human, no matter how confident the AI's response is. When you're evaluating vendors, ask "when you escalate, what does my team see?