index · use cases
10 pages
What teams run on flat lines.
Each page works one workload: the latency budget it has to live inside, the cost shape a meter gives it, and what the API has to do at 3 AM.
01
8,000 min
one busy desk line, every month
TTS for AI customer-support agents
The latency budget and cost arithmetic for a voice support desk: why first audio decides whether callers interrupt, and what 8,000 minutes a month costs.
02
10,800 min
six talking hours a day, one line
TTS for outbound sales agents
Outbound dialers talk six hours a day per line. That is 10,800 minutes a month — $324 to $1,080 on a character meter, $150 on a flat line.
03
43,200 min
the always-on ceiling month
TTS for AI receptionists
A 24/7 receptionist line speaks up to 43,200 minutes a month: $1,296 to $4,320 on a character meter, $150 flat. The arithmetic for always-on voice.
04
2,000 min
where the meter honestly wins
TTS for appointment reminders and notifications
Reminder traffic is bursty and short-form. Where a meter genuinely wins, this page says so — and where burst lines beat both, it shows the arithmetic.
05
23
languages one clone carries
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.
06
20 ports
one queue, shadowed for a month
Replacing IVR menus with voice agents
Tearing out press-1 menus for a conversational agent changes the latency and concurrency math. What the synthesis layer must do, with measured figures.
07
500
connects a day, one line, same $150
TTS for debt-collection voice agents
Collections dialers speak required disclosures on every connected call. The cost arithmetic of scripted outbound, per-key audit trails, and provenance watermarks.
08
2,000
characters — a full read-back fits one utterance
TTS for insurance claims calls
Claims lines are quiet until catastrophe day. Sizing voice capacity for the storm with burst lines, long structured turns, and one cloned voice in 23 languages.
09
zero
marginal cost of the second workload
TTS for healthcare scheduling calls
One line answers the front desk and speaks the recall list. TTS for clinic scheduling: a consistent cloned voice, 23 languages, and traffic accounted per key.
10
12,000 min
a peak-season month, unchanged bill
TTS for order-status calls
An order-status call is one fact delivered fast. The latency and seasonal cost shape of where-is-my-order traffic, with burst lines for the peak weeks.