9.5 Agentforce Service, Sales, and Internal Productivity Scenarios

Scenario patterns by business area

Agentforce can show up in service, sales, and internal productivity scenarios. The certification angle is not to memorize every branded agent type. The admin should recognize the work pattern and choose controls that fit. Service use cases usually involve customers or service reps. Sales use cases usually involve account, contact, lead, opportunity, activity, and pipeline context. Internal productivity use cases usually help employees find information, draft content, or complete administrative tasks.

Service is the most obvious starting point for many organizations. A service agent can answer common customer questions, guide self-service troubleshooting, summarize a case for a rep, suggest a knowledge article, collect intake information, or route to the correct queue. The admin must ensure published knowledge is current, data categories are correct, channel access is appropriate, and the fallback to a human is clear. If a customer asks for a refund, warranty exception, or legal commitment, the agent may need to create or route a case instead of deciding.

Sales scenarios should be grounded in CRM facts and sales policy. An agent might summarize an opportunity, identify missing fields before a stage change, draft a follow-up email, help prepare for a renewal call, or surface open tasks. The admin should check field-level security, forecasting sensitivity, activity visibility, and record sharing. Pipeline data can be sensitive. A sales rep should not receive summaries of opportunities owned by a different team unless the sharing model allows it.

Sales productivity does not mean the agent should close deals automatically. Some actions are reasonable when properly scoped, such as creating a task, drafting an email, updating a next step field, or suggesting that required fields are missing. Other actions need more approval, such as changing stage to Closed Won, discounting a quote, updating forecast category, or sending a contract. The admin should ask whether existing validation rules, approvals, and record types already govern those actions.

Internal productivity scenarios are broad. Employees may ask an agent how to request a laptop, how to file a support ticket, how to find a Salesforce report, or how to update a record. Admins may use supported setup assistance to navigate configuration, troubleshoot user access, understand permissions, or draft setup changes that still require approval. The key is that the agent must respect user permissions and should not make changes without the required approval flow and auditability.

Scenario design workflow:

1. Name the persona: customer, partner, service rep, sales rep, manager, employee, or admin.
2. Name the channel: Experience Cloud, enhanced chat, Salesforce app, console, Agentforce Studio, or another supported surface.
3. Name the data: knowledge, records, files, data library, prompt template inputs, or external service.
4. Name the action: answer only, summarize, draft, create, update, route, transfer, or escalate.
5. Name the stop condition: low confidence, restricted request, missing data, high risk, legal issue, or angry customer.
6. Name the owner: content owner, business approver, admin, developer, support queue, and monitoring owner.

A common service example is case deflection. The business wants fewer routine cases, but the admin should not define success only as fewer cases created. If the agent prevents case creation by giving bad answers, service quality falls. Better measures include resolution rate, transfer rate, customer feedback, answer accuracy, repeat contact rate, and whether high-priority issues are escalated quickly. The best agent protects the customer experience, not just the queue size.

A common sales example is account briefing. The agent can summarize open opportunities, recent activities, support cases, and key contacts before a call. The admin should decide which objects are included, whether cases can be shown to sales users, which fields are sensitive, and whether the summary can be saved back to Salesforce. If service case visibility is restricted, the agent should not reveal case details in a sales summary.

Study trap: do not confuse a productive draft with an approved action. Drafting an email, summarizing a record, or recommending next steps can be useful, but sending a message, changing a contract term, granting access, or closing a case may require additional controls. The admin answer should map the scenario to the correct data, action, permission, and fallback.