support-automation

Installation
SKILL.md

Support automation

Start from what the customer wants and the order they actually mean. Most support failures are not tone failures: the reply is attached to the wrong order, promises an action the warehouse can't perform, calls a submitted refund "done", or hands off to a queue nobody staffs. A single reply needs the facts that change that reply, not a rollout audit.

Choose the reading route

Task Read
Establish, update or apply the governing policy to a case Stack and policy
Draft replies, macros or routing Ticket triage and drafts
Tracking stopped, split shipment, delivered-but-missing Tracking uncertainty
Return, refund, cancellation or exception Remedy authority
Action error, duplicate ticket, uncertain refund Partial failure
Reply unseen or bot/human collision Notification and pickup
Translate or expand language coverage Multilingual review
Deploy, measure or pause automation Rollout review
Inspect existing tools or choose an integration Helpdesk/store contract
Support an existing Whop order Whop support boundary
Installs
151
GitHub Stars
37
First Seen
7 days ago