Section 4 · AI Agents · 35% of exam
4.11 Choosing Between Employee and Service Agents
Exam objective
Given a scenario, determine whether an Employee agent or Service agent is the appropriate agent type based on users, purpose, security context, and channels.
Choose based on audience and purpose
An Employee agent serves internal staff. Typical uses include finding company information, completing employee tasks, or providing role-based support across internal channels. A Service agent serves customers and handles customer-service interactions, such as answering product questions or helping resolve cases. Start with who will use the agent and what the interaction is meant to accomplish. Do not choose solely based on the channel: supported channels overlap in some cases and differ in others. The agent type also shapes identity, security, features, and available connections, so evaluate the runtime model and operational requirements before building. Employee agent design
Employee agents run in the context of the logged-in user. This allows the agent to respect that employee’s Salesforce permissions, field-level security, licenses, and sharing access. Administrators can control which profiles or users can access a particular Employee agent. An Employee agent can be deployed to internal surfaces and, where supported, Slack or other connections. A good design provides useful internal assistance without granting access beyond what each employee should have. Test with users who have different roles and permissions, not only with an administrator account.
Service agent design
Service agents are designed for customer-facing support and operate using a configured Agent User context. Their actions and accessible data must be deliberately scoped for customer interactions. Service agents can be connected to supported messaging, email, and voice channels, depending on product setup and license. Service scenarios often need identity verification, case or order lookup, escalation, and carefully configured customer-safe responses. The Agent User should have minimum required permissions. Validate that one customer cannot retrieve another customer’s information and that escalation preserves useful conversation context without disclosing inappropriate details.
Apply the distinction in scenarios
If employees ask an agent to summarize internal account information in Salesforce or use it through Slack, an Employee agent may fit because the users are authenticated staff and should act under their own permissions. If website visitors need help with orders and cases through messaging, a Service agent is more likely because it is designed for customer service and uses a dedicated Agent User context. Some use cases can appear similar, such as answering a policy question, but their audience and access model differ. Compare audience, tasks, identity, permissions, deployment channels, escalation, and operational ownership. Confirm current channel and feature support in Salesforce documentation before implementation.
TIP: Decide by audience and runtime security: internal employees generally point to Employee agents; customer support interactions generally point to Service agents.
The terms describe different use cases and security architectures. Having the same prompt or action does not make the two agent types equivalent.
Extra concept: Separate internal and customer-facing agents can make access, tone, channel configuration, and monitoring easier to manage.
Official references:
- Create an Agent from an Agentforce Employee Agent Template https://help.salesforce.com/s/articleView?id=ai.agent_employee_agent_setup.htm&language=en_US&type=5
- Create an Agent from an Agentforce Service Agent Template https://help.salesforce.com/s/articleView?id=sf.service_agent_setup.htm&language=en_US&type=5
- Salesforce Certified Agentforce Specialist Exam Guide https://help.salesforce.com/s/articleView?id=005298924&language=en_US&type=1
Key takeaways
- Employee agents serve staff and run in the logged-in employee’s context.
- Service agents serve customers and use a configured Agent User context.
- Choose based on audience, access, task, channels, and escalation requirements.
