IVA
NLP in the IVR is not the same as Studio
Studio regions, task keys, handoffs, and prompts that are production changes.
IVA and GenAI ยท advanced ยท 12 min full read
The modules chapter includes a Natural Language Processing module and Voice Input, and it also includes IVA Transfer. They are different blocks. NLP inside a script is not automatically a Studio task, and a Studio task is not automatically the NLP module.
- Use the module name you configured
- Keep Studio for tasks with keys
Pick the block that matches the design. If the work is a Studio bot with a task key, use IVA Transfer and the Studio article. If the work is a grammar in the IVR, use the IVR module and its own properties.
Do not swap the names.
Label the box
On two designs, write the module name.
- A yes-or-no speech check
- A Studio billing bot
The labels differ.
- Same block? No.
- Studio handoff? IVA Transfer.
- Short speech menu? An IVR module can do it.
- Wrong name? Wrong system.
- IVR modules. vendor. last checked 2026-10.
- Studio digital IVA with VCC. community. last checked 2026-10.
- Interactive voice response. wikipedia. last checked 2026-10.
Glossary. E911: Direct 911 with a dispatchable location. The data sheet names RedSky. E911 data sheet
Sister technologies. CRM SDK. Bring-your-own CRM when no named adapter exists. APIs and SDKs
Config. On two designs, write the module name.
Troubleshooting. No task key exists. The module is Voice Input. Say Voice Input unless a Studio task is really there.
Cross-platform bridge. A mapping to another PBX or contact center is a teaching bridge. It is not an import button.
Future hook. The guide's cloud endpoint stays unset. Confirm before relying on a dated catalog or a case-study number.