Voice Response Unit (VRU)
A Voice Response Unit (VRU) is an automated telephony system that answers inbound calls, plays recorded prompts, and collects caller input through keypad tones or speech before a live agent gets involved.
Definition
A Voice Response Unit (VRU) is an automated telephony system that answers inbound calls, plays recorded prompts, and collects caller input through keypad tones or speech before a live agent gets involved. In a Salesforce contact center, the VRU sits in front of the agents and gathers details such as an account number or the reason for the call. That information then travels into Salesforce so the right record can appear and the call can route to the right queue.
In practice, "VRU" and "IVR" (Interactive Voice Response) name the same thing. VRU is the older label, and most current Salesforce documentation and product names use IVR instead. The concept still matters because every modern voice channel, from Open CTI adapters to Service Cloud Voice with Amazon Connect, relies on this front-door automation to qualify callers and pass context to agents.
How a VRU feeds the Salesforce contact center
VRU and IVR are the same idea under two names
The term VRU dates back to early call center systems, before "Interactive Voice Response" became the standard phrase. Both describe the automated layer that greets a caller, reads out menu options, and reacts to what the caller presses or says. You will still hear veteran telephony architects say VRU, while newer Salesforce material says IVR almost everywhere. They are interchangeable in day to day conversation. The distinction worth holding onto is scope. A VRU is the automation engine itself, the part that plays prompts and captures responses. The wider voice solution adds routing rules, agent desktops, and reporting on top of that engine. When someone says a call "sat in the VRU for two minutes," they mean the caller was working through the automated menus before reaching a person. For a Salesforce admin, the practical takeaway is simple. Treat VRU and IVR as the same component when you read vendor docs, certification material, or a partner statement of work. The behavior you configure, collecting caller data and handing it to Salesforce, does not change based on which word the document happens to use.
Passing collected data into Salesforce
A VRU is only useful to Salesforce if the data it gathers actually reaches the org. With an Open CTI adapter, the telephony vendor collects menu answers and caller ID, then calls JavaScript methods to surface a record. The adapter can read configuration through getCallCenterSettings() and trigger a record using screenPop() or searchAndScreenPop(). Those methods turn raw call data into a Salesforce screen the agent sees the moment they answer. With Service Cloud Voice and Amazon Connect, the same job happens through a contact flow. The flow stores values as contact attributes, and Salesforce reads them onto the VoiceCall record tied to that call. From there, automation can pop a Case, an Account, or a Contact, and Omni-Channel can route the call to the right agent. The data itself is usually small but high value. An account number entered in the VRU lets Salesforce find one exact record instead of guessing from a phone number. A menu choice like "billing" steers the call to the billing queue. Without that handoff, the VRU would just be a recorded greeting with no link to your CRM data.
Screen pop driven by VRU input
Screen pop is the visible payoff of a working VRU. When an agent picks up, Salesforce can bring the relevant record to the front automatically, so the agent is not searching while the customer waits. The Open CTI screenPop() method supports several targets, including SOBJECT for a specific record, SEARCH for a query string, OBJECTHOME, LIST, and NEW_RECORD_MODAL for a brand new record. There is also a FLOW target that passes data into a screen flow through flowArgs. There are two common triggers for the pop. One is the caller ID, also called ANI (Automatic Number Identification), where Salesforce searches on the inbound number. The other is the data the VRU captured, such as an account number typed into the menu. The second option is usually more reliable, because the same person can call from many numbers, but an account number points to one record. When no match is found, a NEW_RECORD_MODAL pop can open a fresh record with fields pre-filled from VRU data using defaultFieldValues. That keeps first-call handling fast even for unknown callers, and it reduces the manual typing that slows agents down.
Where the VRU fits in Open CTI
Open CTI is the browser based JavaScript API that lets a third party phone system embed a softphone inside Salesforce. The VRU lives on the telephony vendor side, not inside Salesforce, but Open CTI is the bridge that lets VRU results control the Salesforce window. The adapter runs in the call center softphone and calls Open CTI methods as call events happen. It helps to keep the layers straight. The VRU handles the audio prompts and captures input. The telephony platform routes the call and decides which agent receives it. Open CTI carries the relevant data into Salesforce and drives the screen pop and softphone display. The agent then works the call inside the Service Console with the right record already open. One important planning note. Open CTI is in maintenance mode and is scheduled for retirement in February 2028. Salesforce now recommends Salesforce Voice, which offers many of the same features with native Omni-Channel and Command Center integration. New contact center builds should favor the Voice path rather than a fresh Open CTI adapter, even though existing adapters keep working for now.
The modern equivalent: Service Cloud Voice
Service Cloud Voice, also branded Salesforce Voice, is where the VRU concept lives today inside the Salesforce ecosystem. It brings phone calls directly into the agent workspace alongside cases, chats, and other channels. With the Amazon Connect option, Salesforce provisions an Amazon Connect instance, and you build the automated menu as an Amazon Connect contact flow rather than a separate standalone VRU box. The contact flow plays prompts, captures input, and sets contact attributes, exactly the role the old VRU played. Those attributes flow onto the VoiceCall record, and Omni-Channel routes the call to an available agent. Because the call is a native Salesforce object, you get real time transcription, supervisor monitoring, and reporting that a bolted on legacy VRU could never provide on its own. For teams modernizing an older contact center, the migration is less about replacing a VRU outright and more about rebuilding its menu logic as a contact flow. The caller experience can stay familiar, the same greeting and the same options, while the data handling becomes tighter and the agent tooling improves. That is the practical reason most new Salesforce voice projects start from Service Cloud Voice.
Designing VRU menus that help, not frustrate
A VRU only pays off if callers can get through it. Long menus, deep nesting, and prompts that ask for data the agent will request again all push customers toward the "press zero for an agent" escape hatch. The goal is to collect the few pieces of context that genuinely speed up the call, such as an account number and a reason code, then hand off quickly. Think about what the data buys you on the Salesforce side. Every value the VRU captures should map to something useful: a record to pop, a queue to route to, or a field to pre-fill. If a prompt does not drive one of those outcomes, it is probably just adding hold time. Capturing an account number is worth it because it enables an exact screen pop. Asking a caller to repeat their full address rarely is. Accessibility and fallback also matter. Speech recognition should have a keypad backup, and every path should reach a human if automation cannot help. A well built VRU shortens average handle time and improves first contact resolution, because the agent starts the conversation already knowing who is calling and why, instead of asking questions the caller just answered.
Trust & references
Cross-checked against the following references.
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 runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. What is a VRU?
Q2. What data does it gather?
Q3. What's the modern equivalent?
Discussion
Loading discussion…