Starbase / 02 RecipeAgents

RecipeAgents / Recipes / Support

Support recipe

Flag upset customers before they churn

The angry email sits in the queue behind ten easy ones. This puts the upset ones at the top.

InputNew support message
ToolsHelpdesk or Gmail, Zapier, an AI step, Slack
TimeSetup about 25 minutes.

Download it

The n8n file has three nodes (trigger, AI step, output) plus a read-me note. We check that its JSON structure is valid, but we haven't run every file in a live n8n instance, so test it with sample data before you switch it on.

Steps

  1. Trigger: new message.
  2. AI step returns sentiment plus a reason.
  3. If 'upset' or 'cancel_risk', add a priority tag and DM the owner.

The prompt

Rate this customer message: calm | frustrated | upset | cancel_risk. Return JSON {level, reason (quote the phrase)}. Sarcasm counts. Message: {{msg}}

Sample run

Example input (written for illustration)
'Third time asking. If this isn't fixed by Friday we're moving to another provider.'
Example output (shows the format, not a real log)
{"level":"cancel_risk","reason":"we're moving to another provider"}
SPONSOR SLOT · AVAILABLEFeature your product here

Where it breaks

  • Polite but furious. Some customers are very polite when they're angry, which is why the prompt asks for the supporting quote: so you can check it.
  • Anything customer-facing or money-related. Keep a human approval step until you've watched a few dozen runs and trust it.

Tool names and pricing change often, so check each tool's current docs before you build. Times on this page are estimates, not measurements.

More support recipes

All collections · Full inbox-triage walkthrough

Newsletter

One small automation every Friday

Each Friday email has one recipe, the prompt for it, and the way it broke when we wrote it up. It's free, and every email has an unsubscribe link.