AgentforceIntermediatedeflectionemail-to-caseauto-responsestrategy
Align agent deflection strategy with Email-to-Case auto-response policies
Real World Scenario
Marketing enabled auto-replies promising 24-hour human response while agents send instant KB links, confusing customers who reply to both threads.
Expected Answer
• Unify email response policy across auto-response rules and agent first-message templates
• Define when agent resolves without case creation vs creates case with agent-handled status
• Coordinate sender addresses and threading headers preventing duplicate conversation forks
• Set expectations in first agent message: self-service resolution path vs human follow-up SLA
• Measure deflection only when customer confirms issue resolved—not mere auto-send
• Align case status transitions so human queues exclude agent-resolved threads correctly
• Review auto-response and agent content quarterly for conflicting promises
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Unify email response policy across auto-response rules and agent first-message templates Also consider: Define when agent resolves without case creation vs creates case with agent-handled status In practice: Coordinate sender addresses and threading headers preventing duplicate conversation forks Balance speed of delivery with maintainability.
Architect Perspective
Email deflection fails when channel policies fight each other. One owner for customer-facing email experience spanning rules, agents, and templates.