
Support ticket triage
Read every new ticket, route by topic, draft replies to the easy ones.
A wall of specimen cards. Each one is a common agent in real-world use today. Skim them. Pick one or two that sound most like what you'd build first.
Each card shows: who it serves, what it does in one line, how it flows (Reads → Agent → Posts), and a rough effort/value tag. Notice they're all the same five parts in different clothes.

Read every new ticket, route by topic, draft replies to the easy ones.

Sort returns by reason, flag suspicious ones, surface trends to the buyer.

Watch reviews, draft calm replies to negatives, summarise themes weekly.

Yesterday's numbers vs last year, with one short sentence on why.

Spot SKUs about to stock out, surface a tight shortlist to purchasing.

Draft polite reminders for overdue invoices on a quiet schedule.

Notice when a number drifts outside its normal band. Name it in plain English.

Watch ROAS and spend, flag campaigns that drifted overnight.

Notice price, copy, and product page changes on a curated list of rivals.

Turn a transcript into a short shared note: decisions, owners, deadlines.

Pre-flight check a document against a policy and flag the gaps.

One short morning note: yesterday's numbers, today's calendar, this week's risks.
Pick the two specimens that made you nod. We'll narrow to one in the next station.
Fourth sticker. Five more to collect.