DocsUse CasesCustomer Success

Customer Success

Use Cases by Department · Beginner Friendly

Prioritize by Sentiment & Urgency

Run in Prompt Architect
supporttriage

Problem: First-come-first-served queues mean angry Enterprise customers wait behind simple 'forgot password' tickets.

1

Sentiment Scan

AI identifies 'Frustrated' or 'Churn Risk' tone in incoming tickets.

2

Impact Scoring

Cross-reference ticket with 'Contract Value' from the Vault to move big deals to the front.

Best Practices

Start prioritize by sentiment & urgency with a small live pilot and one owner per review lane.

Track CSAT and repeat-contact rate from day one.

Bake this control into your checklist: resolution includes owner and next checkpoint

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: empathetic language with no concrete next step.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Prioritize by Sentiment & Urgency Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Keep escalation criteria visible in the same view agents use for replies.

Empower Agents with Tailored Responses

Run in Prompt Architect
supportmacros

Problem: Static macros sound robotic and often don't answer the customer's specific edge case.

1

Dynamic Insertion

AI takes a base macro and 'wraps' it in a personalized greeting and specific answer.

2

Resolution Summary

AI drafts the internal 'Next Steps' for the next agent to read if the ticket is escalated.

Best Practices

Start empower agents with tailored responses with a small live pilot and one owner per review lane.

Track repeat-contact rate and first response time from day one.

Bake this control into your checklist: tone is clear, empathetic, and actionable

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: macro reuse without case-specific context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Empower Agents with Tailored Responses Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Keep escalation criteria visible in the same view agents use for replies.

Identify At-Risk Accounts Daily

Run in Prompt Architect
supportchurn

Problem: Customers often 'ghost' a product for 60 days before canceling, giving Success teams zero warning.

1

Activity Audit

AI flags accounts where 'Admin API calls' have dropped 80% week-over-week.

2

Warning Playbook

Generate a 'Customer Health Check' email script for the Account Manager.

Best Practices

Start identify at-risk accounts daily with a small live pilot and one owner per review lane.

Track CSAT and repeat-contact rate from day one.

Bake this control into your checklist: resolution includes owner and next checkpoint

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: ticket closure without root-cause tag.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Identify At-Risk Accounts Daily Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Include one sentence that confirms what has already been tried.

Transform Tickets into Public Docs

Run in Prompt Architect
supportkb

Problem: Documentation lags behind new features, leading to 50+ tickets for the same issue.

1

Ticket Clustering

AI identifies 10+ tickets asking the same new question.

2

Article Drafting

AI synthesizes the 10 best agent-responses into a single, polished Help Center article.

Best Practices

Start transform tickets into public docs with a small live pilot and one owner per review lane.

Track repeat-contact rate and first response time from day one.

Bake this control into your checklist: resolution includes owner and next checkpoint

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: macro reuse without case-specific context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Transform Tickets into Public Docs Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Include one sentence that confirms what has already been tried.

Manage User Forums & Slack Communities

Run in Prompt Architect
supportmoderation

Problem: Toxic behavior in user communities can destroy a brand's reputation in minutes.

1

Toxicity Filter

AI flags harassment or off-topic spam across thousands of daily messages.

2

Expert Answer Flag

AI flags high-quality 'User Answers' so agents can reward helpful community members.

Best Practices

Start manage user forums & slack communities with a small live pilot and one owner per review lane.

Track CSAT and repeat-contact rate from day one.

Bake this control into your checklist: severity routing is correct for business impact

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: macro reuse without case-specific context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Manage User Forums & Slack Communities Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Link every external response to one internal diagnosis category.

Transform Support data into Product Insights

Run in Prompt Architect
supportvoc

Problem: Product teams ignore 'Support feedback' because it feels anecdotal and un-quantified.

1

Feature Gap map

AI clusters tickets into 'Requested Features' with total 'Revenue at Risk' attached.

2

Sentiment Trend

Track if the last product release increased or decreased 'User Happiness' in tickets.

Best Practices

Start transform support data into product insights with a small live pilot and one owner per review lane.

Track repeat-contact rate and first response time from day one.

Bake this control into your checklist: tone is clear, empathetic, and actionable

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: macro reuse without case-specific context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Transform Support data into Product Insights Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Include one sentence that confirms what has already been tried.

Generate Quarterly Business Reviews (QBR)

Run in Prompt Architect
supportqbr

Problem: CS Managers spend 3 hours per client preparing QBR slides.

1

ROI highlights

AI extracts top 5 'Business Wins' the client achieved using the platform.

2

Usage Narrative

Draft a narrative showing how the client's team matured from 'Basic' to 'Advanced' users.

Best Practices

Start generate quarterly business reviews (qbr) with a small live pilot and one owner per review lane.

Track CSAT and time to resolution from day one.

Bake this control into your checklist: tone is clear, empathetic, and actionable

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: macro reuse without case-specific context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Generate Quarterly Business Reviews (QBR) Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Keep escalation criteria visible in the same view agents use for replies.

Automated Support Quality Audits

Run in Prompt Architect
supportqa

Problem: QA leads only have time to audit 2% of tickets, missing critical coaching opportunities.

1

Rubric Check

AI audits 100% of tickets for: Empathy, Accuracy, and Resolution Speed.

2

Coaching Cards

Generate a weekly 'Learning Path' for each agent based on their actual ticket performance.

Best Practices

Start automated support quality audits with a small live pilot and one owner per review lane.

Track repeat-contact rate and first response time from day one.

Bake this control into your checklist: tone is clear, empathetic, and actionable

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: macro reuse without case-specific context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Automated Support Quality Audits Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Keep escalation criteria visible in the same view agents use for replies.

Streamline Logistics for Exchanges

Run in Prompt Architect
supportlogistics

Problem: Return Merchandise Authorizations (RMA) involve 10+ manual steps, leading to lost inventory and unhappy customers.

1

Vetting Bot

AI interviews the customer: 'Is it broken? Did you try Step X?' before issuing a label.

2

Label Gen

AI calculates weight and triggers a Shipping Label generation based on the warehouse's current capacity.

Best Practices

Start streamline logistics for exchanges with a small live pilot and one owner per review lane.

Track time to resolution and CSAT from day one.

Bake this control into your checklist: severity routing is correct for business impact

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: macro reuse without case-specific context.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Streamline Logistics for Exchanges Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Keep escalation criteria visible in the same view agents use for replies.

Support 20+ Languages with 1 Team

Run in Prompt Architect
supportglobal

Problem: Hiring native speakers for every time-zone and language is prohibitively expensive for startups.

1

Real-time Translate

Incoming tickets are translated into the agent's native language with 99% accuracy.

2

Cultural Nuance Check

AI rewrites the agent's response to ensure it follows local cultural norms (e.g. Formal vs. Informal).

Best Practices

Start support 20+ languages with 1 team with a small live pilot and one owner per review lane.

Track repeat-contact rate and CSAT from day one.

Bake this control into your checklist: resolution includes owner and next checkpoint

Capture where humans still rewrite outputs and convert that into prompt constraints.

Common Mistakes

Avoid this pattern: ticket closure without root-cause tag.

Do not scale while approval ownership is still ambiguous.

Do not mix policy edits and prompt rewrites in the same release cycle.

Do not call the workflow stable until two consecutive review cycles pass quality gates.

Quick Handoff Note Workflow: Support 20+ Languages with 1 Team Owner: Support Operations Lead Decision needed by: <date> Confidence level: Low / Medium / High Next action owner: <name> Risk if delayed: <1 sentence>
Pro Tip: Operator Habit

Keep escalation criteria visible in the same view agents use for replies.

Academy v4.0 · Interactive Documentation · Beginner Mode