For investors Book a consultation
All use cases
USE CASE 04 Restaurants · Hospitality

SeatMap

A restaurant reservation platform that doesn't lose money to no-shows.

Reservations, waitlists, no-show protection, kitchen prep signals and post-visit reviews — one platform, one bill per cover.

–68%
No-show rate after NoShowGuard
< 7 days
From contract to first covers
3 chan
Web + WhatsApp + phone → same book

WHY IT WORKS

SeatMap replaces a pile of fragmented tools — booking widget, SMS confirmations, WhatsApp waitlist, spreadsheet floor plan, Google reviews — with one platform that owns the diner end-to-end. Guests book from the site or WhatsApp, pre-authorise a card for peak slots, get a polite reminder the day before and a re-seating nudge if they run late.

Behind the host stand, the floor plan is a live object: reservations snap to real tables, the waitlist re-routes parties as tables flip, and the kitchen receives a prep-line signal the moment a confirmed booking hits a covers threshold. After the visit, a review nudge lands in the right inbox at the right time.

The whole stack assembles from AIMicroservices blocks: Calendar and WhatsappQR carry the communication, new domain services (TableGrid, NoShowGuard, WaitlistFlow) carry the restaurant logic. No vendor lock-in, no per-cover commission to a third party.

ARCHITECTURE · LAYERED BLUEPRINT

How the microservices wire up.

Read top to bottom. Channels are where people arrive, orchestration is how the AI thinks, domain is the startup-specific logic, data & identity keeps the source of truth, and platform is the invisible glue.

AIM microservice Data / control flow
CHANNELS Where users meet the product ORCHESTRATION Agents, prompts and flows DOMAIN MICROSERVICES The startup-specific logic DATA & IDENTITY Who is who, what they've done PLATFORM Billing, keys, governance CHANNEL BookingWidget Embeddable booking form CHANNEL WhatsappQR Diner WhatsApp thread CHANNEL VoiceHost AI phone host AI AGENT AgentBuilder Host / re-booking agent LOGIC AIFlow Trigger rules FORMS SmartForms Private-event requests SCHEDULING Calendar Service-block schedule DOMAIN TableGrid Live floor plan & table state DOMAIN NoShowGuard Hold-with-card flows DOMAIN WaitlistFlow Live waitlist + re-seating DOMAIN MenuPulse Dynamic menu w/ availability DOMAIN PrepLine Kitchen prep signal DOMAIN ReviewLoop Post-visit review nudge CRM AIM CRM Diner record + history AUTH AuthGate Staff SSO BILLING Billing Holds + deposits PLATFORM SuperAdmin Per-tenant config

Scroll horizontally to see the full architecture.

INVENTORY

Every block in SeatMap.

Each block is a microservice with a clear role — grouped by layer so you can see what belongs to channels, orchestration, domain, data and platform at a glance.

CHANNELS Where users meet the product
ORCHESTRATION Agents, prompts and flows
DOMAIN MICROSERVICES The startup-specific logic
DATA & IDENTITY Who is who, what they've done
PLATFORM Billing, keys, governance

HOW TO SHIP IT

Quick-start checklist.

  1. 01 Import the floor plan into TableGrid; tag peak / shoulder / off-peak windows.
  2. 02 Connect WhatsappQR to the house number, publish BookingWidget.
  3. 03 Configure NoShowGuard (deposit thresholds, grace window, refund policy).
  4. 04 Turn on ReviewLoop — day-after Google / Yelp / TripAdvisor nudges.

WHAT'S NEXT

Compose SeatMap in a visual workspace.

Log into AIM Engine 2.0, drop the blueprint on a canvas, fork the domain microservices you need, and deploy to your own domain. Everything shown here is already a real component.

Book a consultation Browse more use cases