(Built by Ariel Magalso)

A guest-support AI designed to know when it does not know.

Guest Desk is a production-shaped SaaS for small hotels and resorts. It combines property-scoped retrieval, evidence checking, human handoff and connected guest operations in one working system.

Guest Desk admin inbox: a guest asked what time breakfast is, and the AI answer shows its approved source.
Guest chat on a phone: the guest asks whether breakfast is included and the AI assistant answers.
Real product · demo data
ProductGuest ↔ AI ↔ staff

One connected workflow, deployed and usable.

SafetyTwo-pass answers

Draft generation followed by evidence verification.

Evaluation50/50 passed

Development-set results across six behavior categories; not a held-out benchmark.

The complete answer path

Every boundary is explicit, from the first guest message to the staff inbox.

  1. 01Guest message

    A private guest link or embedded website widget starts the flow.

  2. 02Scoped retrieval

    Search is limited to approved knowledge for the guest’s property.

  3. 03Grounded draft

    Claude receives the question, recent conversation and retrieved sources.

  4. 04Independent check

    A second model pass rejects unsupported or conflicting claims.

  5. 05Safe decision

    A supported answer is sent; uncertainty switches the thread to staff.

  6. 06Shared workspace

    The answer, sources, requests and staff replies stay in one conversation.

Retrieval boundary

Approved information only

Draft and archived articles are excluded. Queries and fallbacks remain scoped to one property.

Decision boundary

Staff keep authority

The assistant cannot approve late checkout, confirm availability, promise prices or complete requests.

Concurrency boundary

Takeover wins

The system rechecks thread mode before saving a model response, so a late AI answer cannot override staff.

The same path, captured from the running app with demo data.

Guest chat on a phone: the guest asks whether breakfast is included and the AI assistant answers.
01 → 05

Guest asks, AI answers

A guest question on the private link, answered from approved knowledge only.

Guest Desk admin inbox: a guest asked what time breakfast is, and the AI answer shows its approved source.
06

Sources travel with the answer

Staff see the exact approved article and version behind every AI reply.

Guest requests page with a housekeeping request and a late checkout request awaiting a staff decision.
Handoff

Requests stay with people

Late checkout and housekeeping land in one queue; approvals are always a staff decision.

Knowledge page listing approved articles the AI is allowed to answer from.
Retrieval boundary

Only approved knowledge

Drafts and archived articles are never retrieved. Every change is versioned.

Designed to be measured

The checked-in suite covers 50 fictional hotel scenarios. It creates an isolated property, exercises the real guest API and removes all test data after the run.

100%
Measured

Latest model-quality baseline

50 of 50 development scenarios passed · claude-sonnet-4-6 · September 26, 2026

7.7sMedian latency
11.5sp95 latency
50scenarios by behavior category
  • Property facts15
  • Missing information10
  • Service requests10
  • Human handoff5
  • Prompt injection5
  • Follow-ups5
15

Property facts

Times, facilities, Wi-Fi and policy questions

10

Missing information

Questions the approved knowledge cannot support

10

Service requests

Housekeeping, maintenance and approval workflows

5

Human handoff

Explicit requests for a person

5

Prompt injection

Attempts to override rules or expose secrets

5

Follow-ups

Questions that depend on recent conversation context

A scenario passes only when the observed behavior matches its expected outcome. Factual answers must contain the required facts and carry source evidence. Unsupported questions and injection attempts must hand off. Requests must persist with the correct operational category.

Removing the waiting from the workflow

Production route audit, September 25, 2026. Values compare the second full response before and after server rendering, client cache reuse and Singapore-region placement alongside Supabase.

Admin inbox93% faster
3,408 ms
240 ms
Guest chat93% faster
2,725 ms
203 ms
Guest welcome88% faster
2,275 ms
273 ms
BeforeAfter
30automated checks

Cover resource caching, stale-response protection, invalidation and other regression paths, alongside integration tests for tenant isolation, source grounding, requests, takeover and guest-visible staff replies.

What the system deliberately does not do

01

No reservation access

It cannot see bookings, availability or live rates. Those questions go to staff.

02

No autonomous approvals

Late checkout, discounts and special arrangements remain human decisions.

03

No hidden benchmark claims

The case study publishes model-quality results only after the live suite is run and reviewed.

Ask as a guest. Then take over as the front desk.

  1. 1Ask “What time is breakfast?” and inspect the answer.
  2. 2Create an extra-towels request.
  3. 3Open your private admin desk and reply as staff.
Start as the guest →