case-deflection-strategy

# Case Deflection Strategy

Use this skill when a practitioner needs to design, assess, or improve a Salesforce case deflection program. It activates when the goal is to reduce live contact volume by routing customers to self-service channels — primarily through Einstein Bots, knowledge articles, and Experience Cloud self-service — and when decisions about which topics to deflect, which channels to deploy, and how to measure success need architectural guidance.

---

## Before Starting

Gather this context before working on anything in this domain:

- What is the org's current case volume by contact reason? Pull from Case reports or Einstein Conversation Mining. Without topic-level volume data, deflection prioritization is guesswork.
- Does the org have Salesforce Knowledge enabled and populated? Deflection without a serviceable knowledge base produces bot conversations that end in agent escalation — defeating the purpose.
- What is the org's self-service channel inventory? Experience Cloud portal, Messaging for In-App and Web, Einstein Bots, and Email-to-Case all have different deflection profiles.
- Are data categories set up correctly on Knowledge articles? Miscategorized or uncategorized articles surface in wrong contexts and produce low article-solved rates.

---

## Core Concepts

### Einstein Conversation Mining for Topic Identification

Einstein Conversation Mining (ECM) analyzes historical chat and messaging transcripts to surface the most frequently discussed contact reasons. It clusters similar intents together and ranks them by volume, making it the primary tool for identifying deflection candidates. The output is a report showing topic clusters, volume share, and a recommended automation potential score. Topics with high volume and low complexity (password resets, order status, return requests) are the best first-wave deflection targets. ECM requires an existing transcript history — typically 90 days minimum — and a Messaging or Chat channel. Orgs without transcript data must use case subject/description classification or manual categorization as a proxy.

### Deflection Rate and Goal Completion Rate

Deflection rate measures the percentage of contacts that were resolved in a self-service channel without transferring to a live agent. It is the headline KPI for a deflection program. Industry benchmarks published by Salesforce cite 27% average deflection rates across Einstein Bot deployments. Goal completion rate (GCR) is the more meaningful operational metric: it measures the percentage of self-service sessions where the customer achieved their stated goal (e.g., found an article, completed a transaction, got an answer from the bot) regardless of whether they subsequently escalated. A bot with 60% GCR and 30% deflection rate is performing well — the escalations are genuinely complex. A bot with 5% GCR and 30% deflection rate is suppressing contacts without resolving needs, which degrades CSAT. Always track both. Salesforce ROI research documents an average 198% ROI from deflection programs across Service Cloud deployments, primarily driven by avoided agent handle time.

### Knowledge Article Quality as a Prerequisite

Deflection channels that surface knowledge articles — bots, self-service portals, search — are only as good as the articles behind them. Common knowledge quality failures that kill deflection programs: articles are written at an agent reading level not a customer reading level; articles are too long and not scannable; articles answer edge cases instead of the top 80% of contact reasons; data category assignments are inconsistent so articles appear in wrong channel contexts. Before launching a deflection channel, audit article coverage against the ECM topic list and grade each article for customer readability. The knowledge readiness assessment is a required input to the deflection program design, not a nice-to-have.

### Data Category Hygiene

Salesforce Knowledge uses data categories to control which articles are visible on which channels and to which user profiles. Mis-assigned data categories are one of the most common causes of "we have articles but customers can't find them" complaints. Key behaviors: articles assigned to a parent data category are visible to Experience Cloud users with access to any child category of that parent — but this inheritance does not work in reverse. A data category assigned to a guest user profile but not to the relevant Experience Cloud channel's sharing settings will produce no-results searches. Bots surfacing knowledge via Einstein Article Recommendations pull from the same data category visibility rules as the Experience Cloud site the bot is embedded in. Always validate data category assignments end-to-end across guest/authenticated user profiles before launching.

---

## Common Patterns

### Pattern: Einstein Bot as First-Door Triage

**When to use:** Org has Messaging for In-App and Web or Live Agent Chat, has a knowledge base with 50+ articles, and can identify 5–10 high-frequency contact reasons from ECM or manual analysis.

**How it works:** Deploy an Einstein Bot as the entry point for all inbound messaging. The bot handles a menu-driven or NLU-driven triage that routes customers to: (1) article self-service for informational topics, (2) transactional bot dialogs for automatable requests (order status via API, password reset via Flow), or (3) Omni-Channel queue transfer for genuinely complex issues. Configure containment — the bot resolves the intent without human transfer — as the primary success metric. Use session end surveys to measure goal completion rate.

**Why not the alternative:** Routing all contacts directly to agents and using agents to recommend articles (reactive deflection) is consistently less effective than front-door triage. It increases agent handle time even for conversations that could have been self-served, and it does not reduce contact volume.

### Pattern: Knowledge-Led Self-Service Portal with Federated Search

**When to use:** Org has Experience Cloud and wants to reduce email and phone contact volume for informational queries (how-to questions, policy lookups, product documentation).

**How it works:** Build an authenticated or guest Experience Cloud site with Salesforce Knowledge as the content layer. Enable federated search so customers can find articles, community answers, and Trailhead content from a single search bar. Gate case submission behind a search-first flow: before the Web-to-Case form renders, the customer sees top-matched articles for their typed subject. This is the Salesforce-recommended "article deflection before case creation" pattern. Track article-solved rate (sessions ending in article view with no case submitted) as the deflection metric.

**Why not the alternative:** Embedding a case form on the landing page without a search-first gate guarantees that high-frequency informational queries generate cases, regardless of how good the knowledge base is.

---

## Decision Guidance

| Situation | Recommended Approach | Reason |
|---|---|---|
| High chat/message volume, ECM data available | Einstein Bot with NLU + ECM topic coverage | NLU handles natural language variance; ECM gives validated topic list |
| Low transcript history, but case data available | Manual topic clustering from case subjects + Bot menu dialog | Menu-driven bots do not require NLU training and are reliable for known topic lists |
| Primarily email and web form contact volume | Search-first portal with article deflection gate before case form | Reduces case creation for informational queries without requiring a bot |
| Knowledge base is sparse or poorly categorized | Knowledge readiness sprint before any deflection channel launch | Launching deflection without serviceable articles produces escalation-only sessions |
| Org has <50 articles but wants bot | Bot with transactional automation only (order status, case status lookup) | Transactional bots do not depend on knowledge quality |
| Deflection rate plateau after initial launch | ECM re-analysis to find next topic cluster; article quality audit | Initial deployment typically covers 3–5 topics; ECM identifies the next wave |

---

## Recommended Workflow

Step-by-step instructions for an AI agent or practitioner working on this task:

1. **Audit current contact volume by topic.** Run Einstein Conversation Mining on 90+ days of transcripts, or pull a case volume report grouped by Case Type or Subject keyword. Rank contact reasons by volume. Identify the top 10 topics and tag each as: informational, transactional, or complex. Deflection candidates are informational and transactional.
2. **Assess knowledge readiness.** For each deflection candidate topic, check whether a customer-readable knowledge article exists, is assigned to the correct data categories, and is visible on the target self-service channel. Flag gaps. A topic with no article cannot be deflected via knowledge-led channels.
3. **Select deflection channel per topic.** Use the Decision Guidance table above. Informational topics go to search-first portal or bot + article. Transactional topics go to bot + Flow automation. Complex topics get escalation paths, not deflection targets.
4. **Define KPI baseline.** Before launch, record baseline: total inbound volume by channel, case creation rate, average handle time. Define target deflection rate (industry average is 27%), goal completion rate target (aim for 55%+), and containment rate for bot deployments.
5. **Build knowledge gaps.** Author missing articles for deflection candidates. Write at a 6th–8th grade reading level. Use numbered steps for how-to content. Keep articles under 500 words. Assign data categories aligned to the target channel's visibility rules.
6. **Launch deflection channel and instrument.** Deploy bot dialogs or portal search-first flow. Tag sessions with the deflection topic so you can report deflection rate per topic, not just overall. Set up a session end survey for goal completion rate.
7. **Run monthly ECM refresh.** Deflection programs stagnate when the topic list is treated as fixed. Re-run ECM every 30–60 days to find emerging topics and retire topics where contact volume has dropped.

---

## Review Checklist

Run through these before marking work in this area complete:

- [ ] ECM report or equivalent topic analysis completed with at least 10 topics ranked by volume
- [ ] Each deflection candidate topic mapped to informational / transactional / complex
- [ ] Knowledge article coverage assessed against deflection candidate list; gaps documented
- [ ] Data category assignments validated for target channel and user profile (guest and/or authenticated)
- [ ] KPI framework defined: deflection rate baseline, GCR target, containment rate target (bot deployments)
- [ ] Bot or portal deflection channel configured with per-topic session tagging for reporting
- [ ] Post-launch review scheduled within 30 days with ECM re-run planned at 60 days

---

## Salesforce-Specific Gotchas

Non-obvious platform behaviors that cause real production problems:

1. **Data category inheritance does not work upward** — assigning a guest profile access to a child data category does not grant visibility to articles assigned only to the parent category. Many orgs assign all articles to the top-level category and then wonder why child-category filtered searches return nothing.
2. **Einstein Article Recommendations in bots use channel-scoped data category visibility** — the bot does not search all published articles; it searches only articles visible to the Experience Cloud site context the bot is embedded in. Testing article search in Setup while logged in as an admin will show articles that authenticated guest users cannot see.
3. **ECM requires Messaging or Chat transcripts — it does not analyze Email-to-Case or Web-to-Case** — orgs that predominantly receive contact via email will not get ECM topic clusters from that channel. Case subject/description text mining is required as a substitute and is less accurate.
4. **Deflection rate and containment rate are different and often confused** — containment rate is the percentage of bot sessions where the customer did not transfer to an agent (may have abandoned). Deflection rate is the percentage where the customer's issue was resolved. A high containment rate with low GCR indicates customers are giving up, not being deflected.
5. **Bot session timeout does not equal deflection** — if a customer starts a bot conversation and stops responding, the session closes automatically. This session is NOT a deflection. Ensure bot analytics distinguish between customer-abandoned sessions and customer-resolved sessions.

---

## Output Artifacts

| Artifact | Description |
|---|---|
| Deflection candidate topic list | Ranked list of contact reasons with volume, complexity tag, and recommended channel |
| Knowledge readiness gap report | Table mapping deflection topics to article status: exists / needs update / missing |
| KPI framework document | Baseline metrics and targets for deflection rate, GCR, containment rate |
| Deflection program roadmap | Phased rollout plan: wave 1 (top 3–5 topics), wave 2 (next 5), quarterly ECM refresh cadence |
| Data category audit output | List of data category assignment issues affecting article visibility on target channel |

---

## Related Skills

- architect/service-cloud-architecture — use for end-to-end Service Cloud channel and routing decisions that frame the deflection program within a broader service strategy
- architect/multi-channel-service-architecture — use when deflection spans multiple channels (web, mobile, messaging) and channel-specific configuration decisions are needed
- admin/einstein-activity-capture-setup — not directly related but often confused; ECM is a separate product from Einstein Activity Capture