Voice Response Unit (VRU)
A Voice Response Unit (VRU) is an automated telephony system that answers inbound calls, plays recorded prompts, and captures caller input from keypad tones or speech before a live agent picks up.
Definition
A Voice Response Unit (VRU) is an automated telephony system that answers inbound calls, plays recorded prompts, and captures caller input from keypad tones or speech before a live agent picks up. In a Salesforce contact center it sits in front of the agents, collects something like an account number or a call reason, and hands that context to the org.
Salesforce documentation never uses the acronym VRU. Every help article, developer guide and Trailhead unit says Interactive Voice Response (IVR). You will still hear VRU from telephony architects and see it in older contracts, so treat it as a plain synonym: the technology is current, only the word is superseded, and nothing you configure changes with the label.
In plain English
“When you call a company and a recording says press one for billing, that recording is doing real work. It gathers a few facts, like your account number, before a person joins the call. By the time a human says hello, they already know why you called.”
Worked example
A regional insurer routes claims calls through an Amazon Connect contact flow. The prompt asks for a policy number and the caller keys in 4471902. A Set contact attributes block stores that value as sfdc-Policy_Number__c, so the InvokeTelephonyIntegrationApiFunction Lambda writes it to the matching VoiceCall custom field when the call record is created. An Omni-Channel flow reads the menu choice, Claims, and routes the call to the Auto Claims queue. When the rep accepts, the Voice Call record opens with the policy number already on it. The rep reads it back instead of asking for digits the caller keyed in eleven seconds earlier.
From VRU to IVR to AI voice agents
What the VRU covers, and what it does not
The VRU is only the automation that plays prompts and captures answers. Routing, the agent desktop and reporting sit on top. When a supervisor says a call sat in the VRU for two minutes, they mean menus, not queue hold time. In a Salesforce Voice setup that boundary is literal. The menu tree lives in the Amazon Connect contact flow, outside your org, so it never appears in Setup or in a metadata retrieve. That splits the evidence when a caller says the wrong queue answered. Half the trail sits in Amazon Connect, half on the VoiceCall record, joined only by the attributes the flow set.
How keypad input becomes a field on VoiceCall
Prompts are worthless unless the answers land somewhere queryable. With Salesforce Voice on Amazon Connect you first create a custom field on the VoiceCall object. Then a Set contact attributes block in the contact flow writes the value under that field's API name with an sfdc- prefix, so MyField__c becomes sfdc-MyField__c. Ordering catches people out. That block must run before the InvokeTelephonyIntegrationApiFunction Lambda, or the attribute is missing when the call record is created. Text fields are safest; geolocation and read-only fields are not supported. The older path is Open CTI. The adapter reads what the VRU captured and calls screenPop or searchAndScreenPop. screenPop takes seven targets, including SOBJECT, NEW_RECORD_MODAL and FLOW, so one value can open a record or launch a screen flow.
The stack around the VRU has been renamed twice
If your notes still say Service Cloud Voice, they are stale. The implementation guide is now Salesforce Voice with Telephony Providers and says so openly. Help articles file voice setup under Agentforce Contact Center. Open CTI has a harder deadline. It sits in maintenance mode, gets no new features, and retires on February 28, 2028. It is already deprecated and unavailable for newly created Agentforce Service orgs, with Salesforce Voice as the recommended path. Do not build a fresh Open CTI adapter around a VRU today. Express the menu logic as a contact flow and let Omni-Channel route it instead.
Agentforce Voice is aimed at the menu tree itself
The renaming is the boring part. Salesforce now describes Agentforce Voice as replacing traditional IVR menus with AI voice agents that hold a conversation instead of reading out options. The caller states a problem, the agent works out the intent and either resolves it or hands off. That changes what the front door is for. A VRU exists because a keypad is a cheap way to disambiguate intent. If the system can just ask, the menu tree gets deleted. Whether it lands depends on the escape hatch. Menu trees frustrate people, but callers learn the shortcuts. A voice agent that misreads intent and cannot be interrupted is worse than press one for billing.
How organizations use Voice Response Unit (VRU)
Collects the account number in the IVR so the Service Console opens the right Account before the rep speaks.
Skips the prompt tree when the caller's ANI already matches a known Contact, so only unrecognised numbers hear the full menu.
Trust & references
Cross-checked against the following references.
- Pass Data from the Interactive Voice Response (IVR) System (opens in new tab)Salesforce
- Get Started with Open CTI (opens in new tab)Salesforce
- screenPop() for Lightning Experience (opens in new tab)Salesforce
- Salesforce Voice with Telephony Providers Implementation Guide (opens in new tab)Salesforce
- Agentforce Voice (opens in new tab)Salesforce
- Add IVR to Your Omni-Channel Flow in Agentforce Contact Center (opens in new tab)Salesforce
Straight from the source - Salesforce's reference material on Voice Response Unit (VRU).
Hands-on resources to go deeper on Voice Response Unit (VRU).
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He writes and edits salesforcedictionary.com, published by KineticBit Inc., to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
+5 pts / dayQ1. A vendor's statement of work refers to a VRU and the Salesforce implementation guide refers to an IVR. What should you conclude?
Q2. You created Policy_Number__c on VoiceCall and want the IVR to populate it from an Amazon Connect contact flow. How do you name the contact attribute?
Q3. Your org routes calls through a legacy VRU wired to Salesforce with an Open CTI adapter. What does current documentation tell you to plan for?
Discussion
Loading discussion…