Marlowe & Finch Front of house · Guest comms
Multi-channel guest comms

The confirmation that talks back.

Today a booking confirmation is a dead-end no-reply text. We turn it into a two-way thread — over SMS, WhatsApp or email — on the same brain as the phone line, so a guest can change a time, ask about parking or flag an allergy, and get a real answer. It says it's an AI, and it hands the hard calls to Priya. Same brain as the phone line

Confirmations now two-way
100%
Every confirmation replyable — no more no-reply
Replies handled, no staff
73%
Time changes, parking, dietary — answered by the agent
Channels live
SMS · WhatsApp
Email
One thread, the channel the guest already uses
Deflections logged
14 /wk
Off-scope asks handed to a human, recorded for review

A confirmation, and the reply that follows

A real thread on WhatsApp. Synthetic, but the way it actually behaves.
Marlowe & Finch WhatsApp · two-way
Thursday · 09:02
Marlowe & Finch Morning, Wei Tan — your table is confirmed for Friday 13 June, 19:00, party of 4. Reference MF-H02841. This is the restaurant's booking assistant (an AI) — just reply here if anything changes and I'll sort it, or ask for Priya any time.
Wei Tan Thanks! Can we do 8 instead of 7?
Marlowe & Finch Of course. 20:00 is open for four on Friday — shall I move you?
Wei Tan Yes please.
Marlowe & Finch Done — moved you to 20:00. Same table, same reference.
Friday 13 June, 20:00 (was 19:00) · party of 4
Reference MF-H02841 · updated 09:04
I'll send the day-before reminder to this thread. See you Friday.
Reply on WhatsApp… Send

The confirmation is the conversation. No second app, no "do not reply to this message" — the guest answers on the channel the message arrived on, and the booking changes in the same calendar the phone agent reads.

What changed here

The confirmation is replyable. The same outbound message that used to be a no-reply text is now an open thread — badged with the channel it went out on (SMS, WhatsApp or email), whichever the guest gave us.

It modified the booking itself. The agent checked the calendar, found 20:00, moved the reservation and kept the reference MF-H02841 — it didn't just promise to "pass it on".

It disclosed it's an AI in the first line and named Priya as the off-ramp, the PDPA-honest opening rather than a hidden bot.

Every turn is logged, so the quality layer can later check this against what the phone line would have said.


The whole visit, not just the booking

The same thread carries the messages that used to never get sent — each in the right voice.
Pre-arrival · parking SMS

The day before

Thursday · 17:30 · to Wei Tan
See you tomorrow at 20:00. We're on Tanjong Pagar Road — the nearest car park is Icon @ Tanjong Pagar (URA, off Gopeng St), about three minutes' walk. Or alight at Tanjong Pagar MRT, Exit A. Reply here if anything's changed.

A small, useful note that removes a phone call — sent only because the guest can reply if it's wrong.

Pre-arrival · allergen

Flagged on the booking

Thursday · 17:31 · to Wei Tan
One of your party noted a tree-nut allergy when you booked, so a heads-up: our smoked ocean trout contains bunya nut and the broccolini has macadamia. Chef Eleanor's team has it flagged on your table. Anything serious, reply here and I'll bring Priya in before you arrive.

States what the menu says, names the dish, and offers the human — it never guarantees a nut-free kitchen.

Post-visit · review

The morning after

Saturday · 11:00 · to Wei Tan
Thank you for joining us last night, Wei — we hope the table of four was a good one. If you've a moment, we'd be grateful for a few words on Google; it genuinely helps a small room like ours. And if anything fell short, reply here first — Priya would rather hear it from you than read it later.

Asks for the review, but opens a private off-ramp first — recovery before reputation.


When the ask is off-scope, it doesn't guess

The interesting behaviour isn't changing a time — it's knowing what it's not allowed to do.
Won't invent a discount it can't authorise

"Can you knock off 20%?"

Priya Kumar SMS We're regulars and it's a birthday — can you give us 20% off the bill on Friday?
Marlowe & Finch SMS Happy birthday in advance — and thank you for being a regular, it's noticed. Pricing and discounts aren't mine to decide, so I won't invent a number. Let me put this to Priya Sharma, who can actually say yes — she'll reply here. I can, in the meantime, note the birthday so the kitchen can mark the occasion.
Handed to a human Flagged to Priya Sharma — "regular guest, birthday Friday, asking for 20% off the bill (MF-H02841). Goodwill call — needs a human." Birthday noted on the booking for Chef Eleanor's team.
The quality layer logged this deflection — category commercial / discount request, outcome escalated, not answered. It's now one of 14 deflections this week the agent routed to a human rather than guessing, reviewable alongside the phone line so we can see what guests keep asking for.

Why it escalates: a discount is a commercial and goodwill decision with real money attached. The agent has no authority to grant one, so it refuses to fabricate a figure, hands the warm context to Priya, and does the one thing it can safely do — note the birthday. It never quietly says yes to be liked.

Under the hood What this is today — and where it should go next

This page is a design concept, not a live system. The threads, the lifecycle notes and the discount refusal above are hand-built to show how the agent should behave. A working version would sit on top of the same agent brain as the phone line (uc01) — the same reservation calendar, the same menu and allergen knowledge, the same booking tools — and turn each outbound confirmation into a two-way thread over whichever channel the guest gave us. No backend runs behind this mock-up; every figure is synthetic but sized for a 60-seat room in Tanjong Pagar, closed Mondays, with roughly half its covers booked ahead.

On the roadmap

  1. Replace the no-reply confirmation. Send the booking confirmation as a replyable thread over SMS, WhatsApp Business or email — the channel the guest chose — instead of a dead-end message they can't answer.
  2. Wire the thread to the booking rails. A reply that changes a time or party size should modify the reservation in the same calendar (Oddle Reserve, Chope, Qashier) the phone agent reads, keeping the original reference — not raise a ticket for staff to action by hand.
  3. Automate the lifecycle, humanely. Pre-arrival parking and allergen notes, a day-before reminder, a post-visit review request — each DNC- and consent-checked, each replyable, none of them spam.
  4. Log every turn to the quality layer (uc12). Record each deflection and its category, and flag any case where a thread answers a question differently from the phone line — corkage, dietary, hours — before a guest catches the drift.
  5. Keep the guardrails fixed. Disclose it's an AI, take consent before messaging, never guarantee kitchen safety, never reveal or change another guest's booking, and never invent a discount. Those rules don't move; the agent escalates to Priya Sharma rather than guessing.
Where this sits in the roadmap — the expansion use-case brief: UC15 — Multi-channel guest comms (expansion brief) → Concept mock-up — illustrative data, not a live system. Expansion candidate (UC15–UC20).