Support · workflows we automate

Repetitive support work,
automated.

Spion records the repetitive customer support tasks your team does by hand — triaging tickets and drafting replies, chasing CSAT, building the metrics report, escalating recurring bugs — finds the pattern with AI, and exports a ready-to-run automation to Claude, Workato, Make, Zapier or n8n. Drafts stay internal for an agent to send; Spion never auto-replies. Here are the support workflows we automate most.

Download Spion — free
By The Spion teamLast updated June 14, 2026Recorded by you, not imposed on you
Worked example
Case 33 ~5 min/ticket → 0

Triage and draft replies for inbound ticketsZendesk + Claude → Slack

Agents review and send — instead of starting from a blank box.

What Spion observed
  1. Open each new ticket.
  2. Read and categorize it.
  3. Set a priority.
  4. Search the help center / macros.
  5. Write a reply.
  6. Assign it to a queue.
6 steps · ~5 min · per ticket · high volume
What Spion runs
  1. Read the ticket, customer, plan, and history.
  2. Classify, prioritize, and draft a reply grounded in the help center with Claude.
  3. Tag and route; attach the draft as an internal note (not auto-sent).
  4. Escalate any outage, churn-risk, or angry ticket to #support-escalations.
4 steps · agent reviews + sends
The Claude promptGet ↓
Role: Support automation engineer.
Input: a new ticket's subject, body, customer, plan, and recent history.

Build this workflow:
1. Categorize: billing, bug, how-to, outage, or cancellation.
2. Set priority from impact and plan; detect sentiment.
3. Draft a reply grounded in the matching help-center article or macro, with citations.
4. Apply category, priority, and tags; assign the queue; attach the draft as an internal note (never auto-send).
5. Post any outage, churn-risk, or angry-sentiment ticket to #support-escalations for a human to grab now (added by Spion).
Best exportClaude for triage + draft; Workato/n8n to tag and route.
Case 34~8 min/resolution → 0

Run CSAT follow-up & detractor escalationZendesk → email → Slack

Ask everyone, catch the unhappy ones fast.

View workflow →
What Spion observed
  1. Notice a ticket was solved.
  2. Send a CSAT survey.
  3. Watch for the response.
  4. Flag low scores for follow-up.
  5. Log it for reporting.
5 steps · ~8 min · per resolution · often skipped
What Spion runs
  1. On solved, wait the set delay, then send the CSAT survey.
  2. Split detractors from passives and promoters on response.
  3. Post detractors to #support-escalations for same-day follow-up.
  4. Log every score to the CSAT sheet for the weekly report.
4 steps · unattended
The Make scenarioGet ↓
Trigger · Zendesk, ticket solved.

1. Delay · wait the configured time (e.g. 2 hours) so the resolution settles.
2. Email · send a one-click CSAT survey referencing the ticket and agent.
3. Router · on response, split detractors (low score) from passives and promoters.
4. Slack · post detractors to #support-escalations with score, comment, and ticket link.
5. Google Sheets · log score, agent, category, and comment to the CSAT sheet.
Best exportMake or Zapier.
Case 35~30 min/wk → 0

Build the weekly support metrics reportZendesk → Google Sheets → Slack

Volume, response time, CSAT and backlog — assembled overnight.

View workflow →
What Spion observed
  1. Export last week's tickets.
  2. Compute volume, FRT, resolution time.
  3. Pull CSAT.
  4. Paste into the metrics sheet.
  5. Write the summary.
5 steps · ~30 min · weekly
What Spion runs
  1. Pull last week's tickets and CSAT.
  2. Compute volume, median FRT, CSAT, backlog, top categories.
  3. Flag any metric 10%+ worse than last week.
  4. Write the sheet and post the headline to #support.
4 steps · unattended
The n8n workflowGet ↓
Trigger · Schedule node, every Monday 07:00.

1. HTTP Request · last week's tickets from Zendesk: volume, first-response time, resolution time, reopens, by channel and category.
2. Google Sheets · read last week's CSAT scores from the CSAT log.
3. Function · compute volume, median FRT, CSAT, backlog, top categories; flag any metric 10%+ worse than last week.
4. Google Sheets · append the week's row to "Support Metrics" and refresh the trend block.
5. Slack · post the headline metrics and any movers to #support.
Best exportn8n or Make.
Case 36~20 min/day → 0

Escalate recurring issues to engineeringZendesk + Claude → Jira → Slack

Fifty tickets about one bug become one tracked issue.

View workflow →
What Spion observed
  1. Notice the same complaint repeating.
  2. Gather the example tickets.
  3. Write up the pattern.
  4. File an engineering ticket.
  5. Link the tickets back.
5 steps · ~20 min · ad hoc · often too late
What Spion runs
  1. Read the last 7 days of tickets.
  2. Cluster by root cause with Claude; count and note affected customers.
  3. For any cluster over the threshold, open or update a linked Jira issue with evidence.
  4. Post the spike to #support-eng and tag the source tickets.
4 steps · unattended
The Workato recipeGet ↓
Trigger · Scheduler, every day 09:00.

1. Zendesk · read the last 7 days of tickets with category, tags, and text.
2. Claude · cluster tickets describing the same underlying issue; count each cluster and note affected customers.
3. Jira · for any cluster over the threshold, create or update a linked issue with the count, examples, and affected ARR.
4. Slack · post the spike to #support-eng with the Jira link and tag the source tickets so agents can reply when it ships (added by Spion).
Best exportWorkato; Claude for the clustering.
More by team
SalesPipeline · quota · lead routing MarketingReports · SEO · MQL handoff ITOnboarding · tickets · licenses OperationsSyncs · reporting · reconciliation FinanceClose · AR · budgets · invoicing HROnboarding · hiring · headcount LegalContracts · NDAs · renewals Customer SuccessHealth · renewals · onboarding All use casesEvery workflow, by team

Questions

Most people we record have five or six rituals like the ones above.

Repetitive browser work: CRM and data entry, recurring reports, onboarding and offboarding, reconciliation, lead routing, and ticket triage. If you do it the same way in your browser more than once a week, Spion can usually record it.

No. You record the task once; Spion writes the automation for you to drop into Claude, Workato, Make, Zapier, or n8n — or gives you a step-by-step PDF guide instead.

Spion records whatever you do in the browser, so any web app works — Zendesk, Intercom, Jira, Salesforce, Slack, Google Sheets and the rest. The export targets your automation platform of choice.

No. Spion drafts replies as internal notes grounded in your help center and approved macros, and an agent reviews and sends. It never auto-replies to a customer or invents policy. See our Privacy Policy for how data is handled.

Most people we record have five or six repeating rituals like the ones on this page.

Free for 5 recordings a month, with every export format and full AI analysis included. Pro is $9/mo (20 recordings) and Ultra is $19/mo (50). Paid plans add volume, not features. See pricing.

Record one ritual.
Retire it for good.

Pick the workflow you do most. Record it once, and Spion exports the automation — recorded by you, not imposed on you.

Download Spion — free
Home · Pricing