Internal Call
An Internal Call in Salesforce Service Cloud Voice is a voice conversation between two contact-center users, such as agent-to-agent, agent-to-supervisor, or agent-to-specialist, that stays inside the contact-center system instead of routing over the public phone network.
Definition
An Internal Call in Salesforce Service Cloud Voice is a voice conversation between two contact-center users, such as agent-to-agent, agent-to-supervisor, or agent-to-specialist, that stays inside the contact-center system instead of routing over the public phone network. The platform records these conversations on the VoiceCall object with CallType set to Internal, which separates them from Inbound calls (customer-initiated) and Outbound calls (agent-initiated to a customer).
Internal Calls exist because service work often needs more than one person during a single customer interaction. A frontline rep consults a supervisor on a refund, brings in a billing specialist, or escalates to a higher tier while the customer stays on the line. Service Cloud Voice supports these rep-to-rep calls natively and writes a VoiceCall record for the internal leg so reports can see both the customer call and the consultation behind it.
How internal calls work in Service Cloud Voice
CallType separates internal from customer calls
The VoiceCall standard object is the system of record for every call in Service Cloud Voice, and it has been available since API version 40.0. Its CallType field carries a small set of picklist values, and the ones you see most often are Inbound, Outbound, Internal, Transfer, and Callback. An Internal Call is tagged CallType = Internal, which marks it as a conversation between two staff members rather than a customer interaction. That single field drives a lot of downstream behavior. Reports group handle time and consult frequency by call type. Routing logic can treat internal requests differently from customer queues. Analytics dashboards can isolate agent-to-agent activity to study collaboration patterns. Because the data lives on a standard object, you build these reports with ordinary report types and list views, no custom logging required. The clean separation also keeps customer-experience metrics honest, since an internal consult does not inflate the count of customer calls handled. When you design reporting for a voice contact center, CallType is usually the first field you filter on.
Warm transfer keeps the customer connected
The most common internal-call pattern is the warm transfer, also called a consult transfer. Agent A is on a customer call, realizes the right person is Agent B, and conferences B in. A introduces the customer and shares the context, then either stays for a three-way conversation or drops off and leaves B with the customer. Throughout, the customer is never disconnected and never re-dials. This contrasts with a cold or blind transfer, where Agent A hands the call straight to a queue or to B without a private introduction first. Service Cloud Voice captures the two legs as linked records. The original customer call carries CallType Inbound, and the private A-to-B consultation carries CallType Internal, so a report can trace the escalation chain end to end. Warm transfers reduce customer frustration because the receiving agent already knows the situation before picking up. They also create a clear audit trail of who was involved in resolving a case, which helps with quality review and coaching.
Supervisor monitoring, whisper, and barge-in
Supervisors can join an agent's active call in three escalating modes, and each one shows up as supervisor participation tied to the original customer call. Listen In, sometimes called monitor, is silent. The supervisor hears the agent and customer, but neither of them hears the supervisor. Whisper, or whisper coaching, lets the supervisor speak privately to the agent while the customer hears nothing, which is useful for live guidance on a tricky call. Barge In is full participation. The supervisor clicks Conference and joins the conversation so the agent can hear them, stepping in to resolve a situation directly. These modes give team leads a graduated set of tools, from passive observation to active rescue, without dropping or restarting the customer call. Supervisors typically launch monitoring from the Supervisor view, where active calls and real-time transcription are visible. Treat these powers carefully and grant them only to staff who actually supervise, since they expose live customer conversations and private agent coaching channels.
Specialist consultation without transferring
Not every internal call ends in a transfer. An agent on a customer call can dial a specialist, such as a Tier 2 engineer or a billing expert, for a quick question without handing the customer over. The specialist joins, gives advice, and drops off, and the original agent continues the customer conversation. This quick-consult pattern still produces an Internal Call record that captures the participants and the duration of the consultation. The data is valuable in two directions. For coaching, a pattern of consults on the same topic tells you frontline agents need better training or knowledge-base content in that area. For capacity planning, consult volume shows how heavily specialists are being pulled into live calls, which informs staffing for those skill groups. During the internal call itself, the available controls are deliberately simple. Agents can mute, and the agent who started the call can record it. Keeping the control set small avoids accidental actions, like dropping the customer, while two staff members are talking privately on the side.
Routing and presence for internal calls
Internal calls do not pass through the IVR that greets customers. The agent who starts the call picks the target directly, usually from a phone book or directory of agents, from a queue such as a Tier 2 pool, or by a known extension. Omni-Channel can route internal requests with the same skills-based assignment, presence, and availability logic it uses for customer work, so a consult request can land on whichever qualified agent is free. Presence matters here. The receiving agent has to be available in Salesforce for the internal call to connect, which prevents a consult from ringing someone who is already on another customer. This availability check keeps internal collaboration from disrupting active service. Because routing reuses the Omni-Channel engine, admins do not maintain a separate system for internal calls. They configure queues, skills, and presence once, and both customer and internal traffic respect the same rules. That shared model is part of why internal calls feel like a natural extension of the agent's normal workflow rather than a bolt-on feature.
Reporting that surfaces training gaps
Internal-call data is one of the clearest signals a contact-center manager has for spotting knowledge gaps. Build a report on VoiceCall, filter for CallType = Internal, and group by the subject or case category of the linked customer call. A spike of consults on one topic is a direct hint that frontline training or the knowledge base is thin there. If a large share of Tier 1 calls require a Tier 2 consult on the same product area, the fix is usually upstream, in enablement, not in adding more specialists. Pair the internal-call view with customer-call metrics for the full picture. Customer-side data tells you how long handles take and whether customers are satisfied. Internal-side data tells you how much hidden collaboration sits behind those numbers. Looking at both together is what turns raw call logs into an improvement plan. Over time, a falling internal-consult rate on a topic is good evidence that a training investment paid off, which makes this report useful for measuring enablement, not just for diagnosing problems.
Recording and compliance considerations
Internal calls can be recorded the same way customer calls are, and the agent who initiates the call holds the record control. The same Service Cloud Voice retention and storage policies that govern customer recordings apply to internal ones. Recording employee-to-employee conversations is a sensitive area, though. Labor laws and workplace policies in some regions restrict or require disclosure for recording staff, and the rules differ from those that cover customer calls. Before turning on internal-call recording broadly, confirm the approach with your legal and HR teams so you stay compliant in every jurisdiction where your agents work. From an access standpoint, treat internal recordings with the same care as customer ones. Limit who can listen back, since these calls may contain candid coaching or escalation discussion that was never meant for a wide audience. A sensible default is to record internal calls only where there is a documented business reason, such as quality review of escalations, rather than recording everything by habit. That keeps both your compliance posture and your agents' trust intact.
How to enable internal (rep-to-rep) calls
Internal (rep-to-rep) calls need a small amount of org-level setup before agents can dial each other inside Service Cloud Voice. The core step is enabling change tracking on the Voice Call object so the platform can sync the internal leg. The exact screens vary by telephony provider, so confirm the provider-specific steps in your contact center's setup guide.
- Enable Voice Call Change Data Capture
In Setup, open Change Data Capture and add the Voice Call entity to the selected entities. This lets Service Cloud Voice track and sync internal-call records so agent-to-agent calls work end to end.
- Confirm Service Cloud Voice and the telephony provider
Make sure Service Cloud Voice is provisioned and your telephony provider (for example Amazon Connect or a partner telephony vendor) is connected, since internal-call support depends on the provider's capabilities.
- Set up the agent directory or phone book
Give agents a way to find each other, such as a phone book or directory, so they can place internal calls and pick the right colleague to consult or transfer to.
- Verify presence and Omni-Channel routing
Confirm agents use presence statuses and that Omni-Channel routing is configured, because a receiving agent must be available in Salesforce for an internal call to connect.
The Change Data Capture entity that must be selected at the org level so rep-to-rep internal calls sync correctly.
The connected voice vendor (Amazon Connect or a partner telephony provider) whose feature set determines which internal-call actions are available.
The access that controls who can use Listen In, Whisper, and Barge In, which should be limited to actual supervisors.
The setting that lets the initiating agent record an internal call, governed by the same retention policy as customer calls.
- The receiving agent must be available in Salesforce, or the internal call will not connect.
- During an internal call the available controls are limited, typically mute for both agents and record for the agent who started the call.
- Recording employee-to-employee calls can be restricted by labor law, so clear it with legal and HR before enabling it broadly.
- Provider capabilities differ, so confirm internal-call and supervisor features in your specific telephony provider's setup guide.
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Internal Call.
Hands-on resources to go deeper on Internal Call.
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 an Internal Call?
Q2. Why distinguish internal calls from customer calls?
Q3. What's a typical internal call use case?
Discussion
Loading discussion…