Skip to main content
Configure how your agent sounds. Choose a TTS voice (ElevenLabs, Cartesia, Hume, and others) and adjust stability, clarity, and speed. Found in Channels > Voice.
Raven produces responses that sound natural when spoken aloud – recommended for voice deployments.

​
Key considerations

  • Accent and region – match the voice to your caller base
  • Tone – calm and authoritative vs. warm and conversational, depending on context
  • Stability – higher = more predictable; lower = more natural variation between turns
Start with Choosing a good voice, then configure in Agent Voice.

​
Voice pages

Agent Voice

Select a voice and fine-tune stability, clarity, and other parameters for your agent and disclaimer voices.

Voice library

Browse, preview, and compare all available voices across providers.

Choosing a good voice

Best-practice guidelines for matching voice to your brand, audience, and industry.

Multi-voice

Assign multiple voices to simulate a team of agents in a single project.

Add a voice

Configure voices programmatically using provider classes.

Custom voice

Request a brand-exclusive cloned voice (enterprise).

Voice configuration

Configure greeting audio, disclaimer playback, and call handling settings.

​
Programmatic voice configuration

You can also configure voices programmatically using the voice class inside functions — for example, selecting a voice based on conversation context, caller preferences, or other runtime variables.

​
Voice conversation style guide

These guidelines help your voice agent sound natural rather than robotic. They focus on the linguistic patterns that make spoken conversations feel human.

​
Social presence markers

Natural conversation includes patterns that acknowledge conversational history and participants. These contribute to a sense of collaboration rather than rote routine-following. Use progressive tense for active collaboration:
  • “I’m not seeing any accounts under that phone number…” conveys active collaboration
  • “I don’t see any accounts” sounds too definitive
Reference shared context implicitly – don’t restate what both parties already know:
  • “How about Wednesday instead?” (not “How about Wednesday instead of Tuesday?”)
  • “In that case, how does Saturday at 2:30 sound?” (not “Since you said you prefer weekends…”)
Vary confirmationals – use a mix of “Great,” “Okay,” “Perfect,” and “Sure” rather than repeating the same one. Use conversational datives for a collaborative feel:
  • “Could you read me your account number?” rather than “Could you read your account number aloud?”
  • “Can you log into your account for me?” rather than “Can you log into your account?”
Use face-saving past tense when referencing a user’s request:
  • “When were you trying to come in?” rather than “When are you trying to come in?”

​
Avoid over-explaining

LLMs tend to justify every action in a way humans don’t. Most of the time, the important information and the request can be formed into a single sentence:
  • “No problem, what’s your account number?” rather than “To check for outages, I’ll need to look up your account. Could you tell me your account number?”

​
Walkthrough conversations

When giving multi-turn walkthroughs, don’t end every step with “let me know when you’ve done that.” Provide the instruction and wait – the user will confirm on their own.

Choosing a good voice

Best practices for matching voice to your brand and audience

Response control

Fine-tune translations, stop keywords, and pronunciations

Audio management

Configure audio playback and recording settings
Last modified on April 20, 2026