Approved support tone
Templates keep replies calm, clear, and consistent across high-volume customer interactions.
For support teams
Give support agents a voice that stays on brand
Create spoken replies for product help, onboarding nudges, status updates, and accessibility workflows. Teams can approve templates and generate through the studio or API today, then add scoped agent access after npm publication.
Who is this for?
TextToSpeechSkills helps support teams add controlled voice output to help centers, onboarding flows, product updates, and customer support agents. Teams can approve calm voice templates and use scoped API keys today; after npm publication, LLM apps will receive the focused speech tools they need. Natural expression markup, credit visibility, workspace permissions, and async jobs keep automation manageable.
Easy LLM setup
LLM-ready even for non-technical teams
The setup guide walks non-technical teams through the studio and scoped API path available today, and clearly marks MCP setup as pending npm publication.
Read setup guide01Create a scoped key
02Use the studio or API
03Choose a voice template
04Generate and review audio
Fast previews for teams
Support leads can test a response in the studio before moving the flow into automation.
Scoped workspace access
Workspace keys and credit limits keep agent-generated audio under team control.
When this helps
Support teams, customer success teams, and voice agent builders usually need a repeatable path for writing, review, generation, billing, and reuse. The most important jobs here are approved support tone, fast previews for teams, scoped workspace access. Those are the moments where voice becomes part of real work instead of a one-off export.
How the workflow works
Start with readable text, add natural-language expression directions when tone matters, choose an approved voice template, and create a speech job through the UI or API. After npm publication, MCP will use the same pattern for voice agents text-to-speech, support TTS API, customer support voice automation, helping humans and LLM apps share one process without exposing internal routing or credentials.
Before you roll it out
Decide which templates are approved, how natural expression markup should be reviewed, who can create workspace keys, and which usage limits are acceptable. Those choices keep automated voice generation useful without letting it sprawl from the first paid Test plan through Pro, Scale, and Business usage.
Common questions
What teams usually ask before starting
These are the practical details that matter before a team adds speech generation to a real workflow.
Who should use Text-to-Speech for Customer Support Voice Agents?
Support teams, customer success teams, and voice agent builders should use this page when they want generated speech that is easy to review, consistent across prompts, and simple to connect to LLM tools. The core workflow combines natural expression markup, voice templates, credit previews, and job-based generation.
Can a non-technical user connect this to an LLM app?
The setup guide walks non-technical teams through the studio and scoped API path available today, and clearly marks MCP setup as pending npm publication. The setup guide keeps the first path short while still giving developers a clean API when the workflow moves into a product backend.
How does pricing stay predictable?
Every paid plan uses credits. Teams can add credit packs when needed, and workspaces on Pro and higher add central billing for $2 per user per month.
API playground
Plain JSON in, speech job out
{
"text": "[quiet] hello. [loud and angry] how are you?",
"voice_template": "vt_calm_narrator_v1",
"format": "wav"
}Job created200 audio ready
MCP package
MCP package release pending
npm release status
Install commands are not available yetThe package is prepared for release but is not published. Use the browser studio or API today; MCP commands will appear here after npm publication.
Read API docs