Lesson 26 of 41 · All lessons
Salesforce Agentforce Specialist
0 of 41 complete
1Exam Overview
  1. 1.1Agentforce Specialist Complete Exam Overview
2Prompt Engineering20%
  1. 2.1When to Use Prompt Builder
  2. 2.2Prompt Template Access Controls
  3. 2.3Field Generation and Flex Prompt Template Types
  4. 2.4Grounding Techniques for Prompt Templates
  5. 2.5Creating, Activating, and Executing Prompt Templates
  6. 2.6Best Practices for Writing Effective Prompts
  7. 2.7Trust Layer Security and Privacy Features
  8. 2.8Managing and Preventing Specific Models from Being Accessed
3Data 360 Fundamentals20%
  1. 3.1Agentforce Data Library
  2. 3.2Data 360 Concepts for Agentforce
  3. 3.3Chunking
  4. 3.4Indexing
  5. 3.5Retrievers
  6. 3.6Choosing a Grounding Approach for a Scenario
4AI Agents35%
  1. 4.1How an Agentforce Agent Works
  2. 4.2Agent Building Blocks and Agent Script
  3. 4.3Hybrid Reasoning and Deterministic Behavior
  4. 4.4Agentforce Builder: Canvas and Script Views
  5. 4.5Filters, Variables, and Template Expressions
  6. 4.6Standard and Custom Topics
  7. 4.7Standard and Custom Agent Actions
  8. 4.8Configure Topics, Instructions, and Actions for a Use Case
  9. 4.9Connecting Agents to Digital Experience, Email, Voice, and Slack
  10. 4.10Agent Security Context and Action Execution
  11. 4.11Choosing Between Employee and Service Agents
  12. 4.12When to Use Agent API
5Testing, Deployment, and Maintenance10%
  1. 5.1Testing Agents with Testing Center
  2. 5.2Understanding Testing Center Evaluations
  3. 5.3Deploying Agents from Sandbox to Production
  4. 5.4Deploying Prompt Templates Between Environments
  5. 5.5Reviewing Agent Behavior After Changes
6Governance and Observability10%
  1. 6.1Managing and Monitoring Agents
  2. 6.2Agent Analytics and Performance Signals
  3. 6.3Identifying Opportunities to Optimize Agent Behavior
  4. 6.4Using Observations to Guide Improvements
7Multi-Agent Orchestration5%
  1. 7.1Choosing a Multi-Agent Architecture
  2. 7.2Orchestrators and Connected Subagents
  3. 7.3Handoff and Supervisor Modes
  4. 7.4Model Context Protocol (MCP)
  5. 7.5Agent-to-Agent (A2A) Communication

Section 4 · AI Agents · 35% of exam

4.11 Choosing Between Employee and Service Agents

3 min read Updated Nov 16, 2026

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.

Check your knowledge

Answer exam-style AI Agents questions with answers and explanations.

Practice AI Agents
Finished this lesson? Mark it complete to track your progress.

Ready for the real exam?

Take the timed Salesforce Agentforce Specialist simulator: same number of questions, same time limit.

Get Complete Access