Support Team
Your AI-powered customer support team.
Support Team handles all inbound communication — from pre-signup questions to customer support to retention outreach. It learns from every response and gets smarter over time.
Price: $99 (one-time)
Quick Start
npx @aiorg/cli@latest init support-team ~/my-project
cd ~/my-project
claude
> /setup
Requirements
- Claude Code — Get it here
- Node.js 18+ (for CLI)
Kits are powered by Claude Code. Install Claude Code first, then use our CLI to download kits.
Overview
| Traditional Support Tools | Support Team |
|---|---|
| "Here's a ticket queue" | "Here's who needs help and why" |
| Generic response templates | Personalized, context-aware responses |
| You write every reply | AI suggests, you approve, it learns |
| Same approach forever | Gets smarter over time |
Important distinction:
- Marketing OS = OUTBOUND (you reach out to people)
- Support Team = INBOUND (people reach out to you)
When to Use Support Team
Use Support Team if:
- You get support tickets and questions
- You want to scale your support without hiring
- You have repetitive questions you answer over and over
- You want to retain at-risk users proactively
Don't use Support Team if:
- You need more users → Use Marketing OS
- Users leave before activating → Use Product OS
- You haven't launched yet → Use Idea OS
What's Included
Support Commands
| Command | Description |
|---|---|
/support | AI-assisted ticket response (main command) |
/support-learn | Bulk import historical Q&A |
/support-stats | Pattern analytics dashboard |
/support-settings | Configure tone, thresholds |
Setup & Analysis
| Command | Description |
|---|---|
/setup | Connect to project, configure settings |
/discover | Re-analyze project |
/briefing | Daily support briefing |
/health | User health analysis |
/signals | Detect churn risk and opportunities |
Actions
| Command | Description |
|---|---|
/draft [user/segment] | Draft email for user or segment |
/send | Send approved emails |
/campaign | Create retention campaign |
The Learning Loop
Support Team learns from every approved response:
Ticket → Analysis → Suggestion → Approval → Pattern Saved
↓
Next similar ticket
↓
Higher confidence match
↓
Eventually: auto-respond
Progressive Autonomy
As you build your pattern library, Support Team gains autonomy:
| Level | Patterns | Behavior |
|---|---|---|
| 0 | 0-5 | 100% manual approval |
| 1 | 5-20 | High-confidence suggestions (≥95%) |
| 2 | 20-50 | Auto-respond at 90% confidence |
| 3 | 50+ | Auto-respond at 85%, only escalate edge cases |
User Lifecycle Coverage
Support Team handles every stage:
Pre-Signup Visitors
- Pricing questions
- Feature comparisons
- "Is this right for me?"
Trial Users
- Getting started questions
- Feature discovery
- Technical setup issues
Paying Customers
- Bug reports
- Feature requests
- How-to questions
At-Risk Users
- Usage drop detection
- Re-engagement
- Satisfaction check-ins
Churned Users
- Exit interviews
- Refund handling
- Future reactivation
Safety Features
- Escalation keywords: lawyer, sue, fraud → always human review
- Sensitive categories: billing, refund → always require approval
- Sentiment detection: angry customers → no auto-respond
- Outcome tracking: poor responses → confidence decreases
Data Structure
Support Team stores data in .supportteam/ in your project:
.supportteam/
├── project.json # Connected project
├── strategy.json # Support strategy
├── support/
│ ├── patterns.json # Learned Q&A patterns
│ ├── settings.json # Configuration
│ └── history/ # Archived tickets
├── contacts.db # User database
└── learnings.json # What Claude learned
Migration from Success OS
If upgrading from the old Success OS kit:
- Data folder changed:
.successos/→.supportteam/ - Run
/setupto migrate your data - All patterns and learnings will be preserved
vs. Zendesk / Intercom
They're ticket management tools. You configure flows, they execute.
Support Team is a thinking support team:
- Learns from every response
- Adapts to your tone and style
- Gets smarter over time
- Handles routine tickets automatically
vs. Hiring Support Staff
Support Team is:
- Always available (24/7)
- Instantly knowledgeable (reads your docs)
- Consistent quality every response
- $99 one-time, not $3k/month
But it can't:
- Have real-time conversations (you handle calls)
- Make judgment calls (you approve sensitive responses)
- Build relationships (you're the face)
Support Team is your support team's brain, you're the face.
Related Kits
Before:
- Product OS — If users leave before activating
- Marketing OS — To get users in the first place
After:
- Continue with Support Team for ongoing support
- Marketing OS for outbound campaigns
FAQ
Q: What's the difference between Support Team and Marketing OS?
Marketing OS: OUTBOUND — you reach out to people (campaigns, cold email, content) Support Team: INBOUND — people reach out to you (tickets, questions, complaints)
Q: How does the learning work?
Every approved response becomes a pattern. Similar tickets get faster suggestions. After 50+ patterns, routine tickets can be auto-responded. You stay in control — sensitive topics always need approval.
Q: Can Support Team actually send emails?
Yes, if you connect an email provider (Resend, Loops, etc.). Otherwise, it drafts responses for you to send manually.
Q: What about sensitive topics?
Escalation keywords (refund, lawyer, fraud) always require human review. You configure what topics need manual approval in /support-settings.