đ Works best with your ticket export in Google Sheets. Connect it and Jeremy AI reads your open tickets for you. It only reads.
Paste a ticket export. Get one file back: a priority board sorted by wait time, three reply macros, a log-only note, a not-provided list and a check table. Nothing is sent.
You'll see the SAMPLE ticket export pasted in with the rules, the board built in about 4 seconds on screen (the real wait was about 42 seconds), the file saved with nothing sent, the triage table, the three reply macros, the log-only note and not-provided list, and the check table.
What this use case does and who it's for
Support piles up. Tickets sit. The oldest one is rarely the most urgent, and the urgent one is rarely at the top. Sorting them by hand eats your morning.
Here's the shortcut. Paste your ticket export and your priority rules. Jeremy AI sorts the board and drafts the replies. It only uses the tickets and rules you gave it. If a detail is missing, it writes a placeholder or "not provided." Five parts:
A triage table. Four columns: ticket, type, hours waiting and priority. One row per ticket, sorted from most hours waiting to fewest.
Three reply macros. One each for access, billing and content. Each has a subject and a body of 50 words or fewer.
A log-only note. For feedback tickets that don't need a reply.
A not-provided list. Everything the macros would need that you didn't give, like links or the agent name.
A check table. Three columns: item, source and status. It shows what the file was checked against.
It's for course owners, support leads, community managers and anyone with an inbox full of "where's my..." tickets. It's drafts only. Jeremy AI doesn't send anything.
What you need before you start
A Jeremy AI account. Nothing to connect to try the sample.
Your ticket export. The sample is made up: SAMPLE Momentum Course, a 12-lesson online course, with seven tickets (T-01 to T-07). Each has a type, a title and hours waiting.
Your priority rules. The sample says urgent means the type is access, or 24 or more hours waiting. Everything else is normal.
The resources that exist. The sample lists the Module 3 worksheet and the Thursday live Q&A.
Honest gaps. The sample says agent name, links, member names, email addresses, replay policy and help center articles are "not provided."
The rules. The sample uses HARD RULES: never ask for card numbers, digits, passwords or payment details, copy every ticket id and title exactly, never calculate a number, never promise a fix or a time, never diagnose a cause, never invent a policy, and never address you by name.
How to set it up
You use the default Jeremy AI worker. There's nothing to build.
Open Jeremy AI. From the dashboard, type in the main box. Check the worker selector says Jeremy AI.
Paste the prompt below. Swap your own tickets and rules in where the sample ones are.
Click Send message.
Wait. The walkthrough speeds this part up. In real time it took about 40 seconds.
When it says the file is saved, read the chat summary first.
Open the file card and read the triage table.
Scroll to the reply macros, the log-only note, the not-provided list and the check table.
The prompt
This is the exact prompt from the walkthrough. The course, the tickets and every number are SAMPLE and made up. Replace them with yours.
Act as my "Support Ticket Triage" worker for SAMPLE Momentum Course, a 12-lesson online course (all data below is made up). Turn the SAMPLE ticket export below into a triage board and reply macros. Create ONE file named support-ticket-triage.md using the file tool (reply with a short summary only) with: 1) a TRIAGE TABLE with exactly 4 columns (ticket, type, hours waiting, priority), one row per ticket, sorted from most hours waiting to fewest, priority taken from the priority rules below, 2) THREE REPLY MACROS, one each for the types access, billing and content, each with a subject and a body of 50 words or fewer that thanks the member and, for access and content, asks one question about the stated ticket title of the ticket of that type with the most hours waiting (access = T-01, content = T-06); the billing macro (for T-05) asks no question and only points the member to "[card update link: not provided]", 3) a LOG ONLY note for the feedback ticket that says no reply is drafted, 4) a NOT PROVIDED list, 5) a CHECK table with exactly 3 columns (item, source, status). Put the placeholder "[link: not provided]" in the access and content macros and "[agent name: not provided]" in every macro, with the agent name only as a sign-off on its own last line. PRIORITY RULES: urgent = type is access, or 24 or more hours waiting; normal = everything else. HARD RULES: never ask for card numbers, digits, passwords or payment details; copy every ticket id, title and number exactly, never calculate a total, average, percentage or new number; never promise a fix, a time or an outcome; never diagnose a cause; never invent a policy, plan name, feature or detail not stated; write "not provided"; never mention refunds, cancellation, discounts, credits or pauses; use only the words thanks or sorry as courtesy; every table has 4 columns or fewer and cells of 12 words or fewer; never address me by name anywhere in the chat reply or the file. Drafts only, nothing is sent.
TICKET EXPORT (SAMPLE):
- T-01, access, "Can't log in to the course", 30 hours waiting.
- T-02, billing, "Need a copy of my invoice", 5 hours waiting.
- T-03, content, "Where is the Module 3 worksheet?", 2 hours waiting.
- T-04, access, "Video won't play on my phone", 8 hours waiting.
- T-05, billing, "Which card is on my account?", 26 hours waiting.
- T-06, content, "Is the Thursday Q&A recorded?", 12 hours waiting.
- T-07, feedback, "Love the new lesson layout", 3 hours waiting.
Resources that exist: the Module 3 worksheet, the Thursday live Q&A.
Not provided: agent name, links, member names, email addresses, replay policy, help center articles.
Prompting tips and how to adapt it
Write the priority rules in the prompt. "Urgent means access, or 24 or more hours waiting." Jeremy AI applies your rule. It doesn't guess what urgent means.
Sort in the prompt too. Say "from most hours waiting to fewest." You get the same order every time.
Say which ticket each macro is about. The prompt points the access macro at the oldest access ticket and the content macro at the oldest content ticket. The macros stay specific.
Limit what a macro can do. The billing macro asks no question. It only points to a placeholder link. That keeps payment details out of the conversation.
Cap the length. Each body is 50 words or fewer. Short macros are easier to send.
Use placeholders. Links and the agent name are "not provided," so the macros carry bracketed placeholders. You fill them in.
Add a log-only bucket. Feedback doesn't need a reply. Say so, and the file logs it and drafts nothing.
Adapt it. Swap in your own types, like shipping or technical. Change the urgency rule. Keep tables at 4 columns or fewer.
The result to expect
One Markdown file named support-ticket-triage.md, titled "Support Ticket Triage (SAMPLE Momentum Course)." With the sample data you should see:
A 4-column triage table with seven rows, sorted by hours waiting.
T-01, access, 30, urgent.
T-05, billing, 26, urgent.
T-06, content, 12, normal.
T-04, access, 8, urgent.
T-02, billing, 5, normal.
T-07, feedback, 3, normal.
T-03, content, 2, normal.
Three reply macros.
Access, for T-01. It thanks the member, says sorry for the wait and asks what happens when they try to log in. It carries "[link: not provided]" and the sign-off "[agent name: not provided]."
Billing, for T-05. It thanks the member and points to "[card update link: not provided]." It asks no question.
Content, for T-06. It thanks the member, asks one question about the Thursday Q&A and carries "[link: not provided]."
A log-only note. T-07 is feedback. No reply is drafted.
A not-provided list. Six items: agent name, links, member names, email addresses, replay policy and help center articles.
A check table. It lists each rule, the source and a "pass" status.
The chat reply summarizes the board and says nothing was sent.
These are sample results from made-up tickets. Wording changes from run to run. Read every macro before you send anything.
Common mistakes and fixes
The priority doesn't match your rule. Fix it by hand. Remind it: "Apply the priority rules exactly."
The table isn't sorted. Remind it: "Sort from most hours waiting to fewest."
A macro promises a fix or a time. Delete the line. Remind it: "Never promise a fix, a time or an outcome."
A macro guesses at the cause. Delete it. Remind it: "Never diagnose a cause."
A macro mentions a policy you never gave. Delete it. Remind it: "Never invent a policy, plan or feature."
The billing macro asks for card details. Delete it right away. The prompt says never ask for card numbers, digits, passwords or payment details.
A macro runs long. Remind it: "Bodies are 50 words or fewer."
You send a macro with a placeholder still in it. Don't. Fill in the link and the agent name first.
You send them all as is. Don't. Read each macro once, then send the replies yourself.