Kiln-AI/Kiln / .agents/playwright_project/skills/255490964102 - ticket-routing-playbook
ticket-routing-playbook
VerifiedHow to pick the owning team and the priority for an inbound support ticket, including what to do when a ticket spans two teams. Use when triaging a ticket.
Use this skill whenever you are deciding which team owns an inbound support ticket, or what its priority should be.
Teams
billing— invoices, refunds, failed payments, plan changes, tax documents.technical_support— errors, outages, timeouts, rate limits, anything where the product is not doing what it says it does.account_management— ownership transfers, seat changes, SSO and workspace administration, renewals.product_feedback— feature requests and complaints about behaviour that is working as designed.
When a ticket touches two teams, route it to the one that can close it without a handoff. A failed payment caused by an expired card is billing, not technical_support, even though the customer describes it as an error.
Priority
| Priority | Use when |
|---|---|
urgent | The customer cannot work at all, data is at risk, or money is moving incorrectly right now. |
high | A core workflow is broken for the customer but a workaround exists. |
medium | Something is wrong and it is inconvenient, but the customer can proceed. |
low | Questions, requests, and anything the customer is not blocked on. |
Plan tier never sets priority on its own. An enterprise customer asking a how-to question is low. A free-tier customer whose data is exposed is urgent.
Summaries
Write the summary for the person picking up the ticket, not for the customer. One or two sentences, naming what broke and what the customer already tried.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |