The Short Answer
In customer service, the difference between a pilot that expands and one that stalls almost always comes down to the initial scenario selection. A mature scenario is one that relies on a single, reliable data source, doesn't involve irreversible actions, and has sufficient volume to justify its maintenance.
The most tempting scenarios—handling a complaint, customer retention, credit decisions—are precisely those that demand judgment, sensitivity, and information from multiple systems. These come in phase three, not phase one.
A general decision framework for fitting use cases can be found in Agentforce for Enterprises.
Scenario Maturity Rating
| Scenario | Maturity | Requirements | Primary Risk |
|---|---|---|---|
| Status Inquiries | High | Single reliable field in CRM | Almost none; reversible error |
| Common Knowledge Questions | High | Up-to-date Knowledge articles for common scenarios | Citing outdated policy |
| Agent Assist During Call | High | Knowledge and Case history | Agent adopts incorrect answer |
| Routing and Classification of Inquiries | Medium | Consistent taxonomy of inquiry types | Incorrect classification prolonging resolution |
| Updating Details and Simple Actions | Medium | Precise permissions and limited Actions | Incorrect update in customer record |
| Scheduling, Cancellation, and Rescheduling | Medium | Stable integration with operational system | Integration failure with customer |
| Credits and Compensation | Low | Written policy, authority, and human approval | Financial exposure and customer precedent |
| Complaint Handling and Retention | Low | Contextual understanding, sensitivity, and complete history | Damage to brand and trust |
Three Scenarios to Start With
Status inquiries are the best starting point. The customer asks where their order is, what the status of their request is, or when the technician will arrive. The answer relies on a single field, there's no write operation, and the volume is usually high. Success is also easily measured: did the customer receive an answer and not follow up again?
Common knowledge questions are the second scenario. Here, the challenge isn't the agent but the content. Therefore, the work begins by examining the twenty most frequent inquiries and ensuring that each has an approved and up-to-date article.
Agent assist is the most recommended scenario to start with when there are concerns. The agent suggests an answer, and the human agent approves or corrects it. Every correction is a learning input, and the external risk is zero. Organizations that begin here face external exposure with a real testing set instead of assumptions.
What's needed for the knowledge base to handle the load is detailed in Knowledge Management for Agentforce.
What to Postpone to a Later Stage
Credits and compensation require a written policy that, in most organizations, doesn't fully exist—it lives in the discretion of team leaders. Before the agent enters this domain, the policy must be written, and then it's discovered to be an organizational endeavor in itself.
Complaint handling requires an understanding of emotional context and complete history. Even when the technical answer is correct, the phrasing matters. This is an area where quick escalation is almost always preferable to attempting a solution.
Cross-system scenarios where information is scattered across three systems without a single source of truth—not because of an AI limitation, but because data discrepancies will be revealed here first and attributed as an agent failure.
Escalation Rules That Must Be Defined
Four strict triggers: an explicit request to speak to a person, identification of a negative tone or escalation words, two failed attempts to answer the same question, and any inquiry touching on a predefined sensitive topic.
The transfer must preserve context. A customer forced to repeat everything to a human agent perceives the agent as an obstacle, and that's what they'll remember. A summary of the conversation, what was checked, and what was found should automatically transfer to the human agent.
Designing escalation paths within a channel ecosystem is detailed in Omni-Channel and SLA in Service Cloud.
Scenario: A Contact Center That Swapped Pilots After Two Weeks
A consumer goods company planned to start with an agent handling return requests—the scenario with the most complaints. Within the first two weeks, it became clear that each request required checking warranty conditions in the ERP system, checking inventory, and making a decision that was actually based on a manager's discretion.
The pilot was moved to another scenario: responding to the status of an existing return. The same customers, the same domain, but relying on a single status field. Volume was high, the escalation rate low, and the contact center saw an immediate decrease in repeat inquiries.
Six months later, after the returns policy was written as an approved document, the original scenario returned to planning—this time with human approval for every return authorization. Order, not technology, was what enabled this.
Risks and Prevention Actions
| Risk | How it Appears in the Contact Center | Prevention Action |
|---|---|---|
| Starting with an Emotional Scenario | Complaints reaching management in the first week | Start with an information scenario, not a resolution scenario |
| No Path to a Human | Customer trapped in a loop of questions | escalate to an agent at any stage and hard triggers |
| Loss of Context in Escalation | Customer repeats the story to the agent | Automatic conversation summary transfer |
| Unwritten Policy | Inconsistent answers between cases | Write the policy before introducing the scenario |
| Too Many Scenarios Concurrently | No capacity to maintain and quality declines | Up to three active scenarios in the first year |
Metrics in Service
| Metric | Definition | Frequency |
|---|---|---|
| Containment | Percentage of inquiries closed without an agent and no repeat inquiry | Weekly |
| Repeat Inquiry Rate | Customers who followed up on the same issue within a week | Weekly |
| Time to Escalation | How long until transfer to a human when needed | Weekly |
| Channel Satisfaction | Comparison against a comparable human channel | Monthly |
| Agent Handling Time | Did assistance actually shorten the call | Monthly |
Containment without a repeat inquiry rate is a misleading metric. A conversation closed quickly because the customer gave up is counted as a success, and therefore, both metrics are always read together.
When guidance is needed in selecting scenarios and establishing escalation paths, Agentforce and AI services is the practical next step.
Checklist for First Scenario Selection
- ☐ Scenario relies on a single, reliable data source
- ☐ No irreversible action in the first version
- ☐ Monthly volume justifies ongoing maintenance
- ☐ Approved articles exist for its common scenarios
- ☐ Four escalation triggers are defined
- ☐ Transfer to an agent includes a conversation summary
- ☐ Agent clearly states it is not human at the outset
- ☐ Baseline containment and repeat inquiry rates are measured
- ☐ Maximum number of active scenarios concurrently is set