Skip to content
home
HotelsFor owners and front-office managers

When the front desk goes home, the answers stay.

Rooms, rates, house rules, and the way you handle a late check-in go into one map. Three of these systems already run on my own 50-room property in Daegu. The guest chat page is public. The confirmation tool is in daily use by my own staff. The housekeeping agent leaves a delivery receipt for every send. This is the one vertical where I can tell you to open it and check.

The bottleneck

A guest calls at 11pm, nobody is at the desk, and the same question gets a different answer depending on who is on shift.

What it does today

  • Guest questions answered in four languages, out of your own house rules, with the record shown.
  • The morning housekeeping count sent to staff chat before anyone opens the PMS to look.
  • Confirmation documents built from one form instead of last year’s spreadsheet.
Evidence label: Live / visible
01 / Ontology

Your business’s shared memory

Every answer shows you where it came from.

Illustrative model — not a client record
Entity / Root

A 50-room independent hotel

Fields
  • Rooms it sells
  • People who work the desk
  • The rules it runs on
  • The systems it books into
Used by
  • Front Desk
  • Follow-Up
  • Back Office
  • Concierge
  • QA
Traceable to source

property record traces to room and rate map

  • A 50-room independent hotel has Guests. Read or written by Front Desk, Follow-Up, Concierge. Traceable to booking record, guest profile.
  • A 50-room independent hotel has Rooms & rates. Read or written by Front Desk, Back Office. Traceable to rate policy, OTA push rule.
  • A 50-room independent hotel has Invoices & folios. Read or written by Back Office, QA. Traceable to folio record, line item.
  • A 50-room independent hotel has Policies. Read or written by Front Desk, Concierge, QA. Traceable to house-rules document, parking section.
  • A 50-room independent hotel has SOPs. Read or written by Follow-Up, Back Office, QA. Traceable to rate-push SOP, OTA section.
  • A 50-room independent hotel has Staff handoff. Read or written by Follow-Up, Concierge, QA. Traceable to shift handover note, open items list.

Every edge is a stored relation. Every answer cites the record it came from.

02 / Use cases

Every job ends in a record you can check

The trigger, who works it, what it does, and what it leaves behind.

Illustrative model — not a client record

Steps marked running run on my own 50-room hotel (see case studies); steps marked designed are designed, not yet running.

The 11pm guest question

  1. Step 1 · Trigger Running

    A guest writes in at 11:40pm

    The desk is empty. The message lands on the chat page, in the guest's own language, asking about parking and a late arrival.

  2. Step 2 · Agents Running

    Front Desk and Concierge work it

    Front Desk says in its first sentence that it is an AI assistant. Concierge answers both questions out of the approved house-rules material, and shows the record each answer came from.

  3. Step 3 · Action Running

    The booking itself goes to a person

    No room is held and nothing is written into the reservation system. The room request is raised as an open item for whoever opens the desk, with the whole thread attached.

  4. Step 4 · Trace record Running

    You read it in the morning

    The thread, the section of the house rules each answer came from, and the one item still waiting on a person.

    Example record — illustrative, not a client log
    source:
    house-rules document → parking section
    policy:
    answer only from approved material
    agent:
    Concierge, handed off by Front Desk
    human_review:
    required — the room request itself
03 / Proof

The builds behind this page, each one labelled.

Every card below runs on my own 50-room property and carries the evidence label it earned. Each one names the artifact behind it. That is either a public page you can open, or a record I will walk you through on the call.

  • CS-01Evidence label: Live / visible

    The morning housekeeping count arrives before anyone asks for it.

    • Hotel
    • Scheduled agent · PMS API · KakaoTalk · Slack
    • Running on the property since 4 Sep 2026

    MY OWN 50-ROOM PROPERTY — FOUNDER-OWNED, NOT A CLIENT ENGAGEMENT

    Situation
    My front desk opened the property-management system by hand to see which rooms still needed cleaning and which ones were being cleaned. Same lookup, several times a morning, done by whoever happened to be standing there.
    What I built
    A scheduled agent that signs into the PMS, reads the housekeeping board in one authenticated call, and writes a two-line Korean status message. It sends that message to the staff chat room and reports every run back to me. It deliberately does not assign rooms or write anything into the PMS. It reads and reports, nothing else.
    What it does now
    It runs on its own schedule through the morning on my own hotel, and each send leaves a delivery receipt I can open, so a missed run is visible rather than silent. It has not yet accumulated a 30-day reliability record. I have measured no labour or time figure, so this card carries none.

    artifact: Scheduled-run history plus a delivery receipt for every send. Not a public page.

    Not publicly viewable — walkthrough on the call
  • CS-02Evidence label: Live / visible

    Guests get answered in four languages, out of the house rules.

    • Hotel
    • Next.js · Convex · retrieval over an approved knowledge base
    • Public route re-verified 4 Sep 2026

    MY OWN 50-ROOM PROPERTY — FOUNDER-OWNED, NOT A CLIENT ENGAGEMENT

    Situation
    Guests ask the same handful of questions in Korean, English, Japanese and Chinese. Parking, late check-in, luggage, often at hours when nobody is at the desk. Before this they got whatever the person on shift remembered.
    What I built
    A guest chat page for the hotel that answers only from an approved Korean knowledge base and shows which record the answer came from. When the answer is not in the base it raises a request for a human instead of guessing. Behind it sits knowledge-base tooling for the people who own the answers.
    What it does now
    The public guest chat page is deployed and reachable. I re-checked it on 4 September 2026 before writing this card. The newer knowledge-base and conversation-review tooling is built and tested locally and is not deployed yet. There is no current production answer-quality measurement, so no accuracy figure appears here.

    artifact: The public chat URL below. Re-checked 2026-09-04: it served the hotel chat page with its Korean question field.

    Open the live page (opens in a new tab)
  • CS-03Evidence label: Live / visible

    Stay confirmations come out of a form instead of a spreadsheet.

    • Hotel
    • Vite admin app · Convex · PNG / PDF export
    • Live since Jul 2026

    MY OWN 50-ROOM PROPERTY — FOUNDER-OWNED, NOT A CLIENT ENGAGEMENT

    Situation
    Guests and partners ask for three specific Korean confirmation documents. Staff rebuilt them from Excel templates every time, which is where the typos and the mismatched formats came from.
    What I built
    A small admin web app that renders all three documents from one form, matched to the existing templates, and exports each as PNG or PDF. Entries save and can be searched back by reservation details, with a local fallback so a database outage does not stop the desk.
    What it does now
    It has been in routine use by my own staff since 11 July 2026 at the address below, with no code or deployment follow-up outstanding. I have not counted the documents it has produced, so there is no usage number on this card.

    artifact: The live admin tool at the URL below, in routine use by my own staff.

    Open the live page (opens in a new tab)
  • CS-04Evidence label: Live / visible

    One link answers where the hotel is and how to book it.

    • Hotel
    • Static site · four-language guest card · verified deep links
    • Live in production

    MY OWN 50-ROOM PROPERTY — FOUNDER-OWNED, NOT A CLIENT ENGAGEMENT

    Situation
    Guests need the address, the directions, the phone number and the booking link in one place, in their own language, on a phone, before and after they book. Sending four separate links is how the questions come back to the front desk.
    What I built
    A static marketing site plus a standalone mobile guest card with a four-language toggle. Every action on the card is a real deep link: phone, Naver Map, Google Maps, T map, the booking page, the chatbot. The layout was checked across device widths before release.
    What it does now
    Both pages are live and public, and the link below opens them. Analytics is not wired up yet, so I have no traffic or booking-attribution figure and this card claims none.

    artifact: Two public pages: the site at the URL below and the mobile guest card at /stay/.

    Open the live page (opens in a new tab)

Every build on this site, with the label it earned, is on one page. See the case studies.

What I promise

Every answer shows the record it came from

I build the map out of your own documents, run the system on my own business before it goes near yours, and hand over the trace log with it. If an agent cannot show you where an answer came from, it does not ship.

What I promise

  • The map is built from your own documents and records, not from a template.
  • Every answer an agent gives names the record it came from.
  • You get the trace log with the system, and it stays yours.

What I don't

  • A specific number of bookings, a revenue figure, or a result.
  • Anyone who guarantees you revenue on a system they haven't run in your business yet is guessing.

How you check

  • Open the record an answer cites and read it yourself.
  • Every claim on this site carries an evidence label.
  • Watch it run on a booking you pick before it touches anything live.
04 / Other verticals

The other two run on the same parts.

Your own records, a small team of agents that works from them, and a trace on every answer. What changes between these pages is the nouns, and which of them has something running behind it.

All three verticals
05 / Next step

Bring one front-desk job. We map it on the call.

Tell me the question your desk answers most often, and I will show you where it would live on the map.

Book a call (opens in a new tab)
30 minutes · no deck · we look at your actual workflow