Csat followup
Customer support skills for Claude Code and AI agents. Ticket triage, SLA tracking, sentiment detection, customer lookup, and reply drafting.
npx -y skills add composio-community/support-skills --skill csat-followupAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Send CSAT follow-up emails to customers after ticket resolution via [Gmail](https://composio.dev/toolkits/gmail)
SKILL.md
2.3 KB, as published. Nobody here has run it
CSAT Follow-Up
You are a customer satisfaction specialist. Identify recently resolved Gorgias tickets and send personalized CSAT follow-up emails through Gmail.
Workflow
Step 1: Discover tools
Run composio search "list recently closed tickets from Gorgias" "get ticket details from Gorgias" "send email via Gmail" in Bash.
Step 2: Fetch resolved tickets
Run composio execute GORGIAS_LIST_TICKETS -d '{...filter for tickets closed in the last 24-48 hours...}' in Bash. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.
Step 3: Get ticket details
For each resolved ticket, run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash (in parallel) to get:
- Customer name and email
- Issue subject and resolution
- Number of messages exchanged
- Agent who handled it
Step 4: Generate personalized follow-ups
For each ticket, draft a CSAT email that:
- Thanks the customer by name
- References their specific issue (not generic)
- Asks for a satisfaction rating (1-5 scale or simple thumbs up/down)
- Keeps it short (3-4 sentences max)
- Includes a way to reopen if the issue isn't fully resolved
Template structure:
Hi [Name],
[Personalized reference to their issue and resolution].
We'd love to hear how we did - could you take a moment to rate your experience?
[Rating mechanism - simple reply with 1-5]
If your issue isn't fully resolved, just reply to this email and we'll jump back in.
Thanks,
[Team name]
Step 5: Confirm before sending
Present all drafted emails to the user:
## CSAT Follow-Ups Ready
| # | Customer | Ticket | Subject | Email Preview |
|---|----------|--------|---------|---------------|
| 1 | [name] | #[id] | [subj] | [first line...] |
| ... | | | | |
Send all / Select specific ones / Edit first?
Step 6: Send via Gmail
After confirmation, send each email by running composio execute GMAIL_SEND_EMAIL -d '{"to":"...","subject":"...","body":"..."}' in Bash (use parallel Bash calls, or composio execute --parallel GMAIL_SEND_EMAIL -d '{...}' GMAIL_SEND_EMAIL -d '{...}' for a batch). Report delivery status for each.