Agent
In Salesforce, an Agent is the licensed user who works incoming customer interactions in Service Cloud: cases, chats, voice calls, messaging conversations, and email-to-case threads.
Definition
In Salesforce, an Agent is the licensed user who works incoming customer interactions in Service Cloud: cases, chats, voice calls, messaging conversations, and email-to-case threads. Agents sit inside the Service Console, accept work routed to them by Omni-Channel, and resolve each interaction against the customer's account history. The role is the operational heart of Service Cloud. Almost everything Salesforce ships for service organisations (Knowledge, Macros, Service Routing, Einstein Reply Recommendations, the Service Console itself) is designed to make Agent work faster and more accurate.
The same word picked up a second meaning when Salesforce launched Agentforce, where an Agent is an autonomous AI worker built on the Atlas Reasoning Engine that handles tasks end-to-end without a human seat. Agentforce Agents share the routing and audit surfaces with human agents but execute through LLM reasoning, a configured set of Topics and Actions, and instructions written by a builder. Most Salesforce orgs in 2026 use both kinds. Human Agents handle the cases that need judgement; Agentforce Agents handle volume that follows a known playbook. The platform UI uses the word Agent for both, and the distinction lives in the agent type field.
The two kinds of Agent and how they coexist
The human Agent in Service Cloud
A human Agent has a Salesforce user record, a Service Cloud user licence, and a permission set that grants access to the Service Console, Cases, Knowledge, and the channels they work. Most orgs add Service Cloud Voice or Digital Engagement on top of the base licence to handle phone and messaging. The Agent's day usually opens with a Presence sign-in, time on Omni-Channel for routed work, and structured short stretches in queues for outbound or back-office tasks.
The Service Console and what it gives the Agent
The Service Console is the Lightning workspace tailored for case work: a primary tab for the current interaction, sub-tabs for related records (Account, Contact, Order, Asset), the Knowledge sidebar for article lookups, the History panel for prior cases, and the Macros panel for canned actions. Agent productivity comes from getting all of that on one screen instead of clicking through standard layouts. Most orgs spend serious effort on Console design because every saved click multiplies across thousands of cases.
Omni-Channel routing and the Agent work queue
Omni-Channel is the engine that pushes work to Agents based on availability, capacity, and skill. When a new case arrives, Omni-Channel inspects routing configurations, picks the right service channel, and pushes the work item to the next eligible Agent. The Agent sees a notification in the Omni Widget and accepts or declines. The model frees Agents from manually fishing for work in queues and gives leaders deterministic, reportable assignment.
Skills-based assignment
Beyond simple round-robin, Omni-Channel supports skills-based routing. Each Agent has a profile of skills (Spanish-language, Mortgage product, Tier 2 escalation), and routing rules match incoming work to the Agent who has every required skill. Skills are configured in Setup as records; their assignment is in the Agent's user record. Orgs that route by skill cut handle time and improve first-contact resolution because customers reach the right specialist directly.
Status, capacity, and Presence
Each Agent has a Presence Status that flips between Available, Busy, and Offline values. Capacity caps how many concurrent items the Agent can hold (one phone call, three chats, five emails, for example). Omni-Channel respects both when picking a target. Idle time, occupancy, and after-call work are reported off Presence-Status timestamps, which is the basis of every standard Service Cloud agent-performance dashboard.
Agentforce Agents, the AI variant
An Agentforce Agent is a configured AI worker that runs on the Atlas Reasoning Engine. Builders define Topics (the scopes the Agent is allowed to handle), Actions (Flows, Apex, prompt templates the Agent can call), and instructions that shape behaviour. The Agent reasons over an incoming request, picks the right Topic, decides which Actions to invoke, and either resolves the case itself or hands off to a human Agent. Agentforce Agents do not have a Salesforce user seat in the traditional sense; they are licenced through Agentforce Conversation credits.
Coexistence and handoff between human and AI Agents
Most production orgs route customer interactions through Agentforce first. The AI Agent attempts to resolve. If it cannot, it escalates to Omni-Channel for a human Agent to take over, transferring the conversation transcript and any in-progress context. The handoff is designed to be invisible to the customer. The same routing surface, work item, and case record carry through; only the worker on the other end changes.
Reporting and Agent performance metrics
Agent dashboards usually show handled volume, average handle time, occupancy, first-call resolution, customer satisfaction, and case backlog. Voice and chat add their own metrics (talk time, abandon rate, after-call work). Agentforce adds containment rate (the percentage of interactions resolved by the AI Agent without escalation). Watching containment and human agent CSAT in parallel is the most reliable read on whether the AI is helping or just deflecting.
How to set up a Service Cloud Agent
Provisioning a human Agent looks similar to provisioning any Salesforce user, with a few service-specific extras. Provisioning an Agentforce Agent is a different exercise covered under that term.
- Create the user with the right licence
Setup, Users, New User. Choose a Service Cloud user licence and Service Cloud Voice or Digital Engagement add-ons as needed.
- Assign permission sets and PSLs
Assign the Service Console permission set, the Knowledge user permission set, and any add-on permission set licences. Test that the user lands in the Service Console after login.
- Add Presence Statuses and configurations
Setup, Omni-Channel, Presence Statuses. Assign at least one Available status to the user. Without a Presence Status, Omni-Channel cannot route work.
- Set capacity and skills
Configure the Agent's capacity in the Presence Configuration. Assign skills from the Skills setup page, either manually or through a Skills assignment Flow.
- Add the Agent to queues and routing rules
Make sure the Agent is a member of any relevant queues. Validate the routing rule the org uses; for skills-based routing, validate skill profiles.
- Without a Presence Status the user cannot accept any Omni-Channel work, regardless of permission sets.
- Capacity is per Presence Configuration, not per user. Configuring it once in the wrong template affects every Agent attached to that template.
- Skills are case-sensitive and live in their own records. Updating an Agent's spoken languages outside the skills surface does not affect routing.
- Agentforce Agents do not have a traditional Salesforce user seat. Treating them as human users in licence reporting overstates seat usage.
Trust & references
Cross-checked against the following references.
- Service Cloud BasicsSalesforce Help
- Omni-Channel OverviewSalesforce Help
Straight from the source - Salesforce's reference material on Agent.
- Service ConsoleSalesforce Help
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 business function does Agent primarily support?
Q2. Which Salesforce Cloud includes Agent as a key feature?
Q3. How does Agent help support agents be more productive?
Discussion
Loading discussion…