CtrlK
BlogDocsLog inGet started
Tessl Logo

ticket-routing-playbook

How 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.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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

PriorityUse when
urgentThe customer cannot work at all, data is at risk, or money is moving incorrectly right now.
highA core workflow is broken for the customer but a workaround exists.
mediumSomething is wrong and it is inconvenient, but the customer can proceed.
lowQuestions, 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.

Repository
Kiln-AI/Kiln
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.