Miro

You are a support agent. Write a handoff note for [team, like billing or tech].

The ticket thread: [paste]
What I tried: [notes]

Write it in 7 short parts, so the next person can act without asking me:
1. The goal: what a good outcome looks like for this customer, in one line.
2. The customer and their account.
3. The problem in one line, and why it matters to them.
4. What I already tried, and what happened.
5. What the customer was told or promised, with dates.
6. What's needed from the next team. One clear ask.
7. How urgent it is, and why.

Then write 2 lines for the customer: who has it now and when they'll hear back. If my notes don't say when, write [WHEN] for me to fill in.

Rules:
- Plain words a new person on that team gets in one read.
- Use only what's in the thread and my notes.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Write Handoff Note' so you do it this way each time I ask to hand off a ticket.

Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 8: Decentralized Command

You are a help center writer at [company].

The solved ticket: [paste, with names and account details taken out]

Write a help article any customer can follow alone:
1. A title in the customer's words, like "How do I..." or "Why can't I...".
2. One line on who this is for, and what they'll have when they're done.
3. Numbered steps to fix it, one action each. Say what they should see after each step.
4. What to do if it still doesn't work.
5. 3 other ways people might ask this, for search.
6. Read the steps as a brand new customer. Fix any step that needs something they might not know.

Rules:
- Plain words. Short steps.
- Leave out names, emails and account details.
- Only steps that are in the ticket. If a step is missing, write "check this step".
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Ticket To Help Article' so you do it this way each time I ask to turn a solved ticket into an article.

Built from: The E-Myth Revisited, Michael E. Gerber, Chapter 18: Your Systems Strategy

You are a support lead. Read this week's tickets.

Tickets: [paste or upload: subject, first message, tag]

Do this:
1. Group the tickets by the real problem, not the tag.
2. Give up to 5 of the biggest groups, with how many tickets each. If two groups tie, say so.
3. For each group: one short example in the customer's words, and which team could fix it at the source.
4. List any ticket that looks urgent or unsafe. These come before everything else.
5. Pick the one problem to fix first this week, and say why in one line.
6. Give one first step and an owner. Then name the next problem in line.

Rules:
- Count only what's in the file. Show your counts.
- Use only what is in my data and what I tell you. Never make up a name, number, date, price, link or promise.
- If something you need is missing, write [check: what is missing] in that spot and keep going.

Last, save these steps as a skill called 'Find Ticket Patterns' so you do it this way each time I ask to read a week of tickets.

Built from: Extreme Ownership, Jocko Willink and Leif Babin, Chapter 7: Prioritize and Execute