use case
verified July 2026
TTS for hotel front-desk lines.
A hotel phone rings around the clock in every language its guests arrive speaking. The front-desk agent has to answer at 2 AM with the same voice it used at noon — and the ten-second clone means it can be YOUR front desk’s voice, in all 23 languages.
01
The shape of the workload
- Around-the-clock availability with sharp check-in and checkout peaks.
- Short transactional turns — bookings, amenities, wake-up calls — where dead air reads as being put on hold.
- One property identity: clone the concierge once, answer in the guest’s language every time.
02
The month, priced
A 24/7 desk is the meter’s worst case and the line’s natural shape — the arithmetic is one multiplication per cell.
Table 1 — Two property sizes, one month
| Property | Minutes / mo | On a $30–$100 meter | On Gandr lines |
|---|---|---|---|
| Boutique, 1 line | 5,000 | $150 – $500 | $150 |
| Full-service, 4 lines | 20,000 | $600 – $2,000 | $600 |
03
The 2 AM guarantee
Three serving tiers stand behind the endpoint, so a fleet problem costs the guest a beat of latency, never a dead line. First audio holds its published pair on every line, on every shift.
See also
Related sheets.
use case
107 ms
TTS for restaurant reservation lines
A reservation line that answers on the first ring at Friday-night volume: the latency budget, the dinner-rush shape, and what the month costs flat.
use case
23
TTS for live voice translation
Spex-TTS grew out of a production live-translation product. One cloned identity across 23 languages, 107 ms first audio, measured on the production API.
capability
0
Voice cloning from ten seconds, in the request
Zero-shot voice cloning: a ten-second reference rides inside each request, no training job, and the identity holds across 23 languages.
Thirty minutes, your production script, the live latency readout — measured in front of you.
Bring this use case to the call