Ticket triage

Classifies an incoming ticket and says how urgent it really is.

Support · produces a Review · built in, ready to run

What you give it

Something like this:

Subject: THIS IS RIDICULOUS
I have been trying to place my order since morning and your app keeps saying 'price list unavailable'. I have 40 stores waiting. I have emailed twice. If this is not fixed today we are going back to WhatsApp. — Bilal, Kanwal Foods (paid plan)

What you get back

This is a real run of the skill on the input above, not a mock-up:

Type: bug
Urgency: critical
Why: Production blocker affecting paying customer's core workflow with 40 stores waiting and explicit threat to churn same-day.
Suggested first reply: We sincerely apologize for the disruption to your ordering. We're treating this as a priority and investigating the price list issue immediately. A senior engineer is on it now—can you confirm if this affects all store locations or specific ones?

The wording changes a little every run. The shape does not — that is what the procedure below is for.

Tools it uses

None of its own. A skill that only writes needs no tools, so this one inherits whatever your assistant can normally reach.

The procedure it follows

This is the skill, in full. Add it to your own skills to change any of it.

Classify the ticket below.

Reply in exactly this shape:
Type: bug | billing | how-to | feature request | complaint
Urgency: low | normal | high | critical
Why: <one line>
Suggested first reply: <two or three lines>

Urgency is about impact, not tone. An angry message about a cosmetic issue is not critical; a calm message saying nobody can log in is.

How to run it

In chat, on the Skills page and in automations you do not have to add it first — a library skill runs as it is. Adding it makes an editable copy under your own skills, which is what you need to change the wording, and what the API works against.

New to skills? Start with what a skill is.