Booking assistant
A serverless booking assistant on AWS that reads appointment requests, checks Google Calendar, proposes slots that respect your service rules, locks in the customer’s pick, and sends quiet reminders. Seven posts on the same system — one diagram at a time — with an engineering reference at the end.
-
01
A booking assistant on AWS for a few dollars a month
The whole system on one page — a reader, a scheduler, a confirmer, and the four moves they share for every inbound request.
-
02
How a booking request reaches the assistant
Three lanes at the door: web-form fast path for the easy 80%, AI-handle for free-text email, direct escalate for VIPs the AI should never touch.
-
03
How the assistant understands the request
Three small extractors run in parallel: which service, when roughly, and who’s booking. Confidence on every field; anything borderline becomes a draft.
-
04
How the assistant picks slots
Five filters in order: calendar query, working hours, duration plus buffers, blackouts and capacity, then rank. Every constraint comes from your rules file.
-
05
How a booking gets confirmed
Claim, write, confirm, remind — in that order. An atomic claim row prevents double-booking even when two customers click at the same second.
-
06
What the booking assistant costs
A coffee a month at SMB volume. Cents per request, scaling with the email lane — the form lane is essentially free.
-
07
Engineering reference: the booking assistant architecture
Same system, drawn purely for engineers. Service names, resource identifiers, region, Bedrock model IDs, Google Calendar API choices.