operations · Shipped — running in production
Support ticket triage + autoresponder
First-line support triage. Tags, prioritizes, drafts responses. You approve + send.
What it does
Reads incoming support tickets across Intercom, Helpscout, Zendesk, or email. Tags by category (bug, feature request, billing, how-to). Prioritizes by impact + customer tier. Drafts a response from your knowledge base. Routes high-stakes tickets (cancellations, churn risk) to a human immediately.
- Inputs
- Support tool API key. Knowledge base (Notion, GitBook, your /docs site). Routing rules.
- Outputs
- Tagged + prioritized ticket queue. Drafted responses. Founder/CSM Slack ping for high-stakes tickets.
- Cost per run
- ~$0.20 per ticket triaged + draft.
- Models used
- Claude Sonnet for response drafting. Claude Haiku for tagging + prioritization.
Best for
B2B SaaS, agencies with >20 support tickets/week. Founders doing first-line support themselves who want to reclaim hours.
Not for
B2C with high-volume low-impact tickets — use a chatbot instead. Or brands with no knowledge base (build the KB first).
Common questions
- Does it auto-send responses?
- By default, no — drafts go in your inbox for review. You can enable auto-send for low-risk categories (how-to questions with high-confidence KB matches) after 30 days of supervised use.
Want this skill running in your portfolio?
10 alpha slots open Q3 2026. Founder pricing locked 12 months.
Request alpha →