> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Voice design

> Prepare a voice brief and review saved voices while a first-party voice-generation workflow remains planned.

A voice brief describes the sound appropriate to your agent: language, delivery, pace, and the kinds of words it needs to pronounce clearly. You can prepare that brief now and use it to evaluate accessible saved voices.

<Note>
  This page does not provide a released text-to-voice design or cloning workflow. A saved voice reference is not evidence that Threetone can generate or clone a new voice. Voice-agent publication is also currently unavailable.
</Note>

## Write a useful voice brief

| Decision | Example requirement |
| - | - |
| Language | Clear delivery in the languages your task requires. |
| Tone | Calm explanations, with a neutral response when an action fails. |
| Pace | Slow enough to distinguish dates, addresses, and short codes. |
| Pronunciation | A reviewed list of organization names and domain terms. |
| Consistency | Similar clarity across greetings, questions, and longer explanations. |

Describe the desired qualities without asking to imitate an identifiable person. Use sample text you are permitted to use and avoid real customer information.

## Review existing options

<Steps>
  <Step title="Prepare a short script">
    Include a greeting, one explanation, a clarification question, and a response to an unavailable service. Keep the script unchanged across voice comparisons.
  </Step>

  <Step title="Inspect accessible saved voices">
    Use [List my voices](/api-reference/voices/list-my-voices) and the [model catalog](/overview/models). Record actual voice IDs and compatible model requirements instead of treating a brief as a generated resource.
  </Step>

  <Step title="Prepare the draft reference">
    If a suitable saved voice is available, follow [voice configuration](/agents-platform/configure/voice-and-language/overview) to prepare its model and voice IDs in a server draft. Keep listening and live-conversation verification separate.
  </Step>
</Steps>

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Where do I submit a voice-design prompt?" id="faq-voice-design-prompt">
    There is no verified first-party voice-design submission workflow documented here. Keep the brief as preparation and select from accessible saved voices where suitable.
  </Accordion>

  <Accordion title="Can a voice brief replace a voice ID?" id="faq-voice-design-id">
    No. Agent TTS configuration requires an actual saved voice identifier and a compatible model identifier.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.