Skip to content

use case

verified July 2026

TTS for restaurant reservation lines.

A reservation call is ninety seconds of pure turn-taking — date, time, party size, name — where every silence reads as a dropped call. The workload peaks hard at dinner and sleeps at 3 PM, which is exactly the shape a meter prices worst and a line prices flat.

01

The turn budget

Callers book tables while walking, driving, and half-listening; past a beat of dead air they repeat themselves and bookings double. First audio at 107 ms measured keeps the agent inside conversational rhythm through six or eight rapid turns, in whichever of the 23 languages the caller opens with.

02

The dinner rush, priced

Reservation traffic concentrates into the two hours a meter counts hardest. On lines, Friday at 7 PM costs the same as Tuesday at 3 — you size to the rush once, and burst lines catch Valentine’s Day at $10 a line-day.

Table 1 — One venue and one group, both models

OperationMinutes / moOn a $30–$100 meterOn Gandr lines
One venue, 1 line3,000$90 – $300$150
Five venues, 3 lines12,000$360 – $1,200$450

03

When every line is mid-call

Past capacity the API refuses fast with a retryable 503 — your orchestrator holds the caller one ring and retries, instead of every active booking degrading at once. The reliability sheet publishes the full posture.

See also

Related sheets.

Thirty minutes, your production script, the live latency readout — measured in front of you.

Bring this use case to the call