> For the complete documentation index, see [llms.txt](https://docs.aisera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aisera.com/aisera-platform/tenant-setup/aisera-platform-configuration/tenant-configuration-settings/voice.md).

# Voice

The **Settings > Configuration > Voice** window allows you to set parameters for your Aisera tenant. These are settings that apply to any bot you create in your Aisera tenant.

<div align="left"><figure><img src="/files/yw0OmH6I9BZq22Xert2f" alt="" width="563"><figcaption></figcaption></figure></div>

You can change the following settings when configuring your tenant/platform instance.

<table><thead><tr><th width="165.146728515625">Label</th><th width="83.4761962890625">Data Type</th><th>Description</th></tr></thead><tbody><tr><td>Audio recordings retention days</td><td>Integer</td><td>Specifies how long audio recordings from voice conversations are retained before automatic deletion. This helps manage storage and ensures compliance with data retention policies.</td></tr><tr><td>Cisco Webex organization ID</td><td>String</td><td>The unique organization identifier for your Cisco Webex account. This is required to integrate voice capabilities with Cisco Webex for call handling and virtual agent interactions.</td></tr><tr><td>Cisco Webex data schema ID</td><td>String</td><td>The data schema ID for Bring Your Own Virtual Agent in Cisco Webex. This schema defines how virtual agent data is structured and managed within the Webex platform. This is not typically used unless customer does audio data forking or wants to exchange media or other content between external data source and WebEx. More information <a href="https://developer.webex.com/create/docs/bring-your-own-datasource">here</a>. Please check with your WebEx admin if you think this needs to be changed.  </td></tr><tr><td>Tenant Region</td><td>String</td><td><p>Specifies the geographic region where your tenant data is processed and stored.<br></p><p><strong>NOTE</strong> – This is a very important setting if you have a requirement to meet GDPR or EMEA related data sovereignty. If the EMEA region is selected, all call data and communication will be managed from endpoints within EU and no data will be transferred out. This is not true with NA (North America) selection. When EMEA is selected, please make Deepgram URL and ElevenLabs URL fields below are switched to corresponding EU endpoints to make it work correctly.   </p><p><br>Choose: </p><ul><li>NA (North America) </li><li>EMEA (Europe, Middle East, Africa) </li></ul><p>This helps ensure data residency compliance and optimal latency.</p></td></tr><tr><td>Deepgram URL</td><td>String</td><td>The API endpoint URL for the Deepgram speech-to-text service. Configure this to enable automatic transcription of voice conversations using Deepgram’s AI-powered speech recognition.</td></tr><tr><td>ElevenLabs URL</td><td>String</td><td>The API endpoint URL for the ElevenLabs text-to-speech service. Configure this to enable natural voice synthesis for bot responses in voice conversations.</td></tr></tbody></table>