Configure Voice, Recognition, Recording and Transcription

Choose voice and speech-recognition settings and manage call recording, transcripts, access and retention.

What this guide helps you do

Choose voice and speech-recognition settings and manage call recording, transcripts, access and retention.

Who should use it

Workspace owners, managers, automation users and authorized technical users responsible for AI configuration or customer workflows.

Before you begin

  • Use the correct workspace and minimum required role.
  • Use a business-controlled provider account where applicable.
  • Understand provider billing, usage and data settings.
  • Use fictional Pakistan test data.
  • Define human handover before enabling automatic replies or calls.

Main concepts and fields

Concept / FieldMeaning or Use
Voice ProviderText-to-speech service.
VoiceSelected speaker.
Recognition ProviderSpeech-to-text service.
LanguageExpected caller language.
RecordingStored call audio.
TranscriptionGenerated text.
RetentionHow long call data is kept.

Step-by-step instructions

  1. Choose the voice provider and voice.
  2. Choose language/recognition behavior.
  3. Test English, Urdu, Roman Urdu and mixed speech where required.
  4. Enable recording only when authorized.
  5. Add caller disclosure.
  6. Enable transcription where required.
  7. Restrict access.
  8. Set retention and deletion process.
  9. Test audio quality and transcript accuracy.

Test and verification

  1. Test quiet and noisy calls.
  2. Test interruption and silence.
  3. Review recording access.
  4. Review transcript accuracy and retention.

Common issues and solutions

IssueWhat to Check
Poor recognitionLanguage, audio quality and provider.
Recording missingProvider capability, setting, storage and permission.
Transcript inaccurateAudio and recognition configuration.

Security, privacy, consent, cost and provider notes

  • AI-provider charges and Wemblo AI-action usage are separate controls.
  • Do not expose provider keys or customer data in screenshots, tickets or client-side code.
  • Use human review or handover for sensitive, private, regulated, urgent, high-value or final decisions.
  • Do not promise perfect accuracy or guaranteed business outcomes.

Last reviewed: