IVR

Speech Input IVR: Capture Spoken Answers on a Call

How a speech input IVR captures what callers say: the Ask node, timeouts, re-asking, expected words, Hindi and English, where answers go, and when to use keypad input instead.

Edesy Team5 min read

Frequently asked questions

What is a speech input IVR?

An IVR that asks a question and listens to the caller's spoken answer instead of, or as well as, waiting for a keypress. The answer is transcribed to text by speech-to-text and saved with the call.

Which languages can the Ask node transcribe?

The Ask node's language list currently offers English (India), English (US) and Hindi. The same language is used to speak the question and to transcribe the answer.

Can the IVR branch on what the caller said?

The Ask node itself has two exits: answered and no answer. To act on the content, send {{answer.<key>}} to your own API with a sync HTTP Request node and branch on its Success or Failure result, or process the answers afterwards from the call log or status callback.

How do I improve recognition of names and places?

List them in the Expected words field, comma-separated, for example 'Delhi, Lucknow, Sales, Accounts'. The hint tells the recogniser what callers are likely to say.

Where do the spoken answers end up?

In the IVR call log next to the recording, in the status callback for outbound API calls, and in later nodes as {{answer.<question key>}} tokens, for example in an HTTP Request body or an email notification.

Is speech input better than keypad input?

Not always. Use keypad input for fixed choices (confirm or cancel, a 1 to 5 rating) and speech for open answers that don't fit on a keypad, such as a city, a reason, or a name. Mixed flows often work best.

Edesy Team

The Edesy engineering team, building voice AI, messaging, and automation products for Indian businesses.

Published

Share

IVRSpeech to TextSpeech RecognitionDevelopersIndia
Back to blog