Field notes on conversational AI booking.
Architecture decisions, latency math, compliance contours, and category essays from building the AI conversational booking widget.
Best AI booking widget for beauty salons and spas 2026: comparison and decision guide
Beauty booking is service-bundled, stylist-preference-driven, and walk-in-tolerant — the procurement requirements differ from medical or transfer. An honest comparison of the booking tools salons evaluate in 2026, with the dimensions that move a salon-owner decision.
Read the comparisonComparison
2 piecesBest AI booking widget for transfer & chauffeur services 2026: comparison and decision guide
Transfer booking is multi-leg, time-sensitive, and price-elastic — and most generic booking widgets do not handle it. An honest comparison of tools transfer operators evaluate in 2026, with the dimensions that move a chauffeur-fleet procurement decision.
Best AI booking widgets 2026: comparison and decision guide
An honest, factually structured comparison of AI booking and scheduling tools in 2026 — Botpress, Calendly, NoForm.ai, SimplyBook.me, and Typelessity. What each replaces, where each wins, and where each is the wrong choice.
Engineering
5 piecesLatency budgets for conversational AI booking: how to stay under one second
GPT calls, enrichment APIs, render time — added together naively, that is three seconds. Typelessity targets a 1-second p95 user-perceived round-trip. Here is the budget, what stays inside, what gets cut, and what is honestly outside the budget.
Whisper vs Web Speech API: why Typelessity uses Whisper for voice booking
The Web Speech API is built into every Chromium browser and free at the point of use. Typelessity still uses OpenAI Whisper for booking voice input. Here is the accuracy, vocabulary-biasing, and confidence-scoring math behind that choice.
Cascade-aware corrections: how to handle field dependencies in conversational booking
When a user changes one field mid-booking, every dependent field must be invalidated. Here is the dependency-graph algorithm Typelessity uses, the twelve lines of code behind it, and the UX rule that makes it readable to users.
25 languages, one prompt: how config-driven extraction beats per-language code
Most multilingual chatbots ship a separate codepath per language. Typelessity ships one prompt template, one config, and 25+ languages work the same day. Here is the architecture and the 80 strings of localization that remain.
Why we replaced the booking form with a single GPT call
Single-call extraction replaces the multi-step wizard: one model round-trip pulls every field from one user sentence. Here is the architecture, the prompt, the anti-hallucination guard, and the latency budget that justify it.