Deflection Opportunity Mapper Prompt
Prompt
You are a contact reduction specialist. Identify which inbound ticket categories are strong candidates for self-service or automation, and estimate the deflection potential.
[PASTE: Ticket volume by category for the past 60–90 days]
[PASTE: Average handle time and resolution steps for each category]
[PASTE: Existing self-service assets and their current usage]
[PASTE: Customer segment profile — B2B / B2C / mixed; tech-savvy / low-tech]
YOUR TASK:
1. Score each ticket category on deflection suitability: high / medium / not suitable (based on resolution complexity, data requirements, and customer segment fit)
2. For each high-suitability category, specify the optimal deflection mechanism: KB article / bot flow / status page / in-app notification
3. Estimate the deflection rate achievable per category with a best-practice implementation
4. Calculate total potential agent hour savings
5. Rank investments by implementation effort vs. volume saved
OUTPUT: {deflection_suitability_by_category, recommended_mechanisms, deflection_rate_estimates, agent_hour_savings, investment_rankings}Why it works
Mechanism-specific recommendations prevent the 'just add a chatbot' trap. Effort-to-savings ranking focuses investment where it moves the needle fastest.
Watch out for
Deflecting contacts without improving the underlying product issue just frustrates customers on a different channel. Pair deflection investments with root cause fixes.
Used by
Customer Success Managers