"Run of House, Roll-In Shower, Virtuoso Rate": The Reservation Shorthand General AI Gets Wrong at a 28-Room Inn

It is 4:12 on a Tuesday in October. Leaf season, the twenty-eight-room inn is sold out Friday and Saturday, and the reservations agent picks up line two. A travel advisor talks the way advisors talk: "Two nights arriving the fourteenth, run of house is fine, book it on the Virtuoso rate, and she'll need the roll-in shower, not the tub — and note the amenity on the folio."

Seven minutes later, line one: a guest who has never worked in a hotel. "I want the double-double for my son's wedding block, and my brother-in-law comes Thursday but wants to be walked over to your sister property because he has points."

Both callers just used vocabulary a general AI assistant, dropped onto the phone line untouched, will mangle. In lodging a mangled word is not a typo. It is a room type that does not exist on the fourteenth, an accessible room given to somebody who did not need it, and a family in your lobby at 9 p.m. on the busiest Saturday of the fall.

The shorthand nobody in this trade thinks twice about

Run a plain, general-purpose assistant on an independent hotel's phone line for a week and the failures are always the same words. "ROH" comes back as "row." "OOO" becomes "oh oh oh." "The BAR rate" gets answered as though the caller asked about the lounge. "Walk the guest" becomes escorting somebody down the hall rather than paying to move them to a competitor. "Attrition" is heard as staff turnover instead of the wedding-contract clause that bills the couple for rooms the block did not pick up. "Rack rate" turns into luggage racks.

A hotel-tuned model is a general AI that has been taught the lodging trade's own vocabulary — room-type codes, rate codes, folio and block language, and the difference between a prepaid third-party booking and a direct one — so it stops guessing at words your front desk says fifty times a day. That is the whole idea, and it is the thing that changed in 2026.

Through 2024 and 2025 the pitch was "our model is smart enough to figure it out." It usually was not, because the mistakes hotels care about are not reasoning mistakes — they are hearing mistakes and units mistakes. KQ2 versus KSTE. DQQB versus DDB. A king with a rollaway versus a queen suite with a pullout that three of your listings describe differently. GOV meaning the federal per diem for that county, which changes every October 1 with the government fiscal year, and which a general model will happily quote at last year's number.

What tuning on the trade's own language actually fixed

In 2026 vertical models — trained on one industry's own material rather than the whole internet — became a real category rather than a marketing line. For lodging the material is not exotic: reservation calls, rate plans, room-type dictionaries, cancellation policies, folio lines, channel manager mappings. Three things get fixed at once.

First, the ear: it stops mishearing the codes, having heard them spoken by tired front desk agents and fast-talking advisors, in accents, over hold music. Second, the units: length of stay is nights not days, a 3 p.m. check-in and a 90-day group cutoff are different kinds of deadline, a pet fee is per stay at some properties and per night at others. Third, the edge cases — in this trade, mostly about who may change what. A prepaid booking made through an online travel agency on a virtual card is not a reservation your agent may re-rate, extend or refund. A tuned model treats that as a hard wall; a general one treats it as a service opportunity and creates a chargeback for you.

flowchart TD
  A["Caller: 'two queens, ROH, Virtuoso rate, roll-in shower'"] --> B{"Room type and rate code recognised?"}
  B -->|No| C["Agent asks one clarifying question, does not guess"]
  B -->|Yes| D["Agent checks live availability in the PMS"]
  C --> D
  D --> E{"Is this a prepaid third-party booking?"}
  E -->|Yes| F["Hand to front desk, no rate or date change"]
  E -->|No| G["Book direct, quote pet fee and occupancy tax"]
  G --> H["Accessible room held and noted per ADA reservation rule"]

The three words that cost you a room night

Wrong bed type is survivable — the room attendant swaps a rollaway in and the guest grumbles. The expensive errors are narrower.

Accessible. The Department of Justice reservation rule under Title III requires you to describe accessible rooms in enough detail for a guest to decide independently, and to hold that room out of general inventory once booked. A general model treats "handicap room," "ADA room," "roll-in" and "accessible tub" as one bucket — so it sells a roll-in shower to a guest who did not need it and leaves a wheelchair user with a tub. That is not a service recovery problem. That is a complaint letter with a regulation number in it.

Non-refundable. Advance purchase, consortia and negotiated corporate rates carry different cancellation terms, and the caller never asks. A tuned agent reads the terms attached to the rate plan it is actually quoting; a general one recites the standard 48-hour policy because that is what the website says.

Block. "I'm with the Kaplan wedding" means the caller belongs inside a group block with a cutoff date, a contracted rate and a pickup count your director of sales is watching. Booked outside it, that room night shows as transient, the block looks soft, and someone releases inventory already spoken for.

The arithmetic on four bad bookings a month

An illustration — run your own numbers off your property management system's adjustment report rather than mine.

Suppose a tuned agent, working alongside your reservations agent rather than instead of her, catches two-thirds of those by asking one clarifying question instead of guessing. Call it $700 a month, or $8,400 a year, on a line item that appears nowhere in your budget because it is scattered across rate adjustments, comps and one very bad Saturday. Prove it the boring way: pull three months of folio adjustments coded to front desk error, count them, then count them again ninety days later.

Where the front office manager still has to stand up

Tuning fixes vocabulary. It does not fix judgment, and there are four places to keep a human firmly in the chair.

Overbooking on a compression night. When the town is sold out for a festival and you are weighing the last two rooms against your own no-show history, that is the general manager's call — made with her relationships at the properties down the road.

Any apology with money attached. Rate disputes and any call where the guest is already angry should reach a person quickly. Set the handoff line low at first — a hundred dollars is sensible — and raise it only after you have listened to a month of recordings yourself.

Group and wedding contracts. Cutoff dates, attrition clauses and food-and-beverage minimums are negotiated, not looked up. Let the agent take the enquiry and gather dates, room count and decision timeline; let your director of sales write the contract.

And accessibility questions beyond the room description. Whether the pool lift works, whether the front steps have a ramp, whether the third floor is reachable without stairs in a 1908 building — somebody who has walked the property answers those.

Frequently asked questions

Does this mean I have to change my property management system?

No. The tuning is on the language side — how the assistant hears and speaks the trade. It still reads availability from whatever you run: Cloudbeds, Mews, WebRezPro, ThinkReservations, an Oracle system. Check one thing before signing: can the vendor read your actual room-type dictionary and rate plans, including the odd ones you built yourself, rather than a generic list of "king" and "double"?

How do I test whether a vendor's model actually knows lodging?

Call their demo line and speak the way your regulars do. Ask for a run-of-house at the AAA rate with a late arrival guarantee. Say you are with a block and give the block name. Say the booking came through a third party and ask to move it a day. Say "we'll need the roll-in, not the tub." A model never taught this trade fails at least two of those four within thirty seconds — and fails confidently, rather than by asking.

What about guests who speak in the wrong terms entirely?

That is most guests, and it is the point. Real callers say "the room with the two big beds," "the handicap one," "the discount for old people." A trade-tuned model maps those onto your room types and rate codes without correcting the guest — exactly what a good agent does at the desk. A general model takes the phrase literally or invents a room type you do not have.

We only take about forty calls a week. Is this worth it?

At forty calls a week the case is not labour savings — you are not removing a person from a twenty-eight-room inn. The case is the calls at 9:40 p.m., during the breakfast rush, and while the one person on duty is carrying a bag upstairs. Count last month's voicemails and how many you returned the same day. That is the business case.

The first thing to do Monday

Export your room-type dictionary and active rate plans, print them, and spend twenty minutes with your front office manager marking which codes confuse new hires. That single page — the codes, the plain-English phrases guests use for them, the terms attached to each rate — is what a vendor needs to teach an agent your property. It is also the best onboarding document you will ever hand a new reservations agent.

CallSphere builds voice and chat agents that answer hotel phone lines and web chat around the clock, take booking enquiries and pass anything sensitive to a person at the desk. If the calls lost during check-in rush and after the desk closes are the leak you want to plug, that is the part worth a conversation — and the room-type and rate-code work above is what makes those answers correct rather than merely fast.