Neat AI

Systems that speak in the house voice.

Neat AI is the second practice at Drinks By Neat: guest and staff systems for hotels and restaurants that already have a point of view. Same doctrine as the bar work — scoped before it starts, trained on your knowledge, handed over so the house owns it.

Guest Communication

The inbox, answered

Most rooms lose guests in the gap between a message and a reply. Hours, menus, amenities, dietary notes, “are you open on Monday” — the questions are predictable, and the answers already exist in someone’s head or a buried PDF.

Guest Communication puts those answers in the house voice, on the channels guests already use. It knows when to escalate: a complaint, a VIP, anything a bot should not close. The standard is the same as a well-run bar — consistent, fast, and never improvising the allergen story.

Booking & Inquiry

Holds, routes, follow-ups

Inquiries die in inboxes. A table for six on Saturday, a private dining request, a room-plus-dinner package — if the reply is slow, the guest books elsewhere and nobody logs why.

This module captures the ask, routes it to the right desk, and follows up on holds. It does not replace a reservations system. It stops the leak around it.

Staff Knowledge Copilot

Specs at the shoulder

The best bartender on the team is also the wiki. Specs, allergen notes, 86s, the way this house builds a martini — it lives in one person’s head until that person calls out.

The copilot is trained on your specs, SOPs, and standards, not a generic cocktail encyclopedia. New hires get the house answer, not a guess. It is the same instinct as a spec book, built for a phone in the well rather than a binder in the office.

Hotel Upsell

The right offer, once

Most upsell is a banner. Guests learn to ignore it. A useful offer is timed to the stay — a table when they have none, a late checkout when the flight is actually late, an F&B note that sounds like the concierge, not the CRM.

Hotel Upsell is written against your inventory and your voice. It suggests; it does not nag. If the offer is not defensible at the desk, it does not go out.

Loyalty & Feedback

Before the review

The complaint you hear is cheaper than the one you read. Post-stay and post-serve loops catch the miss while there is still a chance to fix it — and notice the regular before they drift.

This is not a points program. It is a disciplined follow-up: who came, what they asked, whether they would come back, and who on the floor should know.

Analytics

A GM can read it in five minutes

What guests asked. What staff needed to look up. Where the menu and the service actually leak. The report is short on purpose — a weekly readout, not a dashboard nobody opens.

Analytics is only useful if it changes a decision: a spec that confuses the team, a question the website should already answer, a day-part that is quietly dying. The numbers sit next to the floor, not above it.

How it is sold

Scoped like a beverage engagement.

A call, then a proposal

We start with the channels you already have, the knowledge that is trapped, and the questions that repeat. Then a fixed-scope proposal — not a discovery invoice.

Trained on your house

Voice, specs, hours, menus, constraints. A generic assistant is worse than no assistant. If it cannot be sourced to your materials, it does not answer.

You own the system

Same rule as the bar: the work is finished when your team can run it. Documentation, handoff, and a clear owner inside the building.

The method is on the approach page. Beverage work still lives on services.

FAQ

Straight answers.

Is this a product we log into?

It is a practice, not a boxed app. We design, train, and hand over systems that sit in the tools you already use — or specify new ones when the current stack cannot carry the work. The proposal names the stack before you sign.

Do we have to buy beverage consulting to get Neat AI?

No. They are separate engagements. They pair well — a spec book that already exists is the best training set for a staff copilot — but either practice can stand alone.

Will it invent answers?

That is the failure mode we design against. The system is constrained to your materials and is told to escalate when it does not know. Hallucinated hours or allergens are not an acceptable miss.

Who is this for?

Hotels and restaurants that already have a voice worth protecting — typically a GM or beverage director who is tired of repeating the same answers, and a team that cannot be cloned. If the room has no standards written down, we start there.

Next step

Fifteen minutes usually answers it.

Tell us the channels, the team, and what is leaking — you will leave the call knowing whether Neat AI is a fit.