Customer support
Turn technical guidance into customer action steps
Convert verified technical instructions into safe, ordered steps with checks, branches, and recovery
Open recipeTopics
Customer support prompt templates for issue summaries, empathetic replies, escalation signals, help articles, ticket analysis, and accurate next steps
Support responses must acknowledge the customer while staying within confirmed facts and authority. These recipes separate the issue, attempted steps, available resolution, escalation conditions, and unknowns.
Customer support
Convert verified technical instructions into safe, ordered steps with checks, branches, and recovery
Open recipeCustomer support
Compress a case into a searchable title and handoff summary without losing uncertainty or safety context
Open recipeCustomer support
Group comparable ticket evidence while preserving denominators, uncertainty, duplicates, and severity
Open recipeCustomer support
Address a complaint clearly while separating resolution, compensation review, and agent authority
Open recipeCustomer support
Classify support evidence against explicit safety, authority, privacy, service, and complexity thresholds
Open recipeCustomer support
Build a factual troubleshooting state from a conversation without merging different attempts or inventing results
Open recipeCustomer support
Acknowledge the customer's actual impact, answer what is known, and provide a safe next step
Open recipeCustomer support
Turn verified product behavior into safe, scannable steps with prerequisites, outcomes, errors, and escalation
Open recipeCustomer support
Compare a draft response with every customer question, fact, constraint, and requested outcome
Open recipeCustomer support
Preserve one verified incident state while changing detail, cadence, privacy, and actions by channel
Open recipe