Back to all systems
Case study · 03/Hospitality technology

A WhatsApp ordering journey connected to menu management, kitchen queues, staff actions, customer notifications, and feedback.

Working conversational workflow + adminAnonymous by design
Case study · 03Hospitality technology

Operating system

Conversational commerce

01 · QR-to-WhatsApp customer entry02 · Natural-language menu and quantity parsing03 · Structured confirmation, totals, and queue-based ETA

Operating context

A busy hospitality team needs the ordering channel, fulfilment queue, and customer updates to behave like one system. Manual transcription creates missed items, uncertain wait times, and weak order traceability.

The challenge

Complexity had to become one legible operating loop.

Let a customer order naturally in chat while preserving deterministic prices, quantities, order states, staff accountability, and a practical fallback when language understanding is uncertain.

The system response

The interface and architecture tell the same story.

The experience combines natural-language parsing with a structured menu and explicit confirmation flow. Orders move into a staff and kitchen workspace with quick status actions, scheduling, payment state, customer notifications, and an audit trail.

Product scope

Capabilities shaped around the work.

01QR-to-WhatsApp customer entry
02Natural-language menu and quantity parsing
03Structured confirmation, totals, and queue-based ETA
04Kitchen board with order-state controls
05Menu, customer, team, promotion, and feedback administration
06Returning-customer reorder and post-order feedback

System architecture

From entry point to operating control.

A narrative view of the system boundary. Each layer creates a cleaner handoff into the next and keeps consequential work visible.

01

The chat layer interprets customer intent against a controlled menu.

02

A confirmation boundary converts conversation into an order record.

03

Kitchen and staff surfaces manage the fulfilment state machine.

04

Status changes trigger customer-facing updates.

05

Operations data feeds menu, customer, and feedback views.

What the work demonstrates

Evidence, without invented metrics.

These outcomes describe the product and operating model visible in the repository. They are not presented as confidential client KPIs.

01

Natural conversation without sacrificing transaction structure

02

One order state shared by customers, staff, and kitchen operators

03

A reusable pattern for chat-led commerce beyond hospitality

Repository evidence

  • Documented webhook and order API surface
  • Working staff command and kitchen workflows
  • Prompt hardening and state-management test suites

Technical material

TypeScriptNode.jsWhatsApp/TwilioPostgreSQLOptional LLM parsing