PromptBase
PromptBase SelectGet Select
Close icon
General
Home
Marketplace
Create
Hire
Login
Chat
Sell
Explore

Prompt Details

Model
(claude-5-opus)
Token size
919
Example input
[TICKETS]: Ticket 1 - Monday report blank again / Ran the Monday export for Harding Dental, got headings and no charts. Third week running. / Ticket 2 - Empty report for two clients / Two of my eleven clients got an empty report. Both paused ad spend in July. The other nine were fine. / Ticket 3 - report is empty when a client pauses ads / Figured out the pattern: if a client has no ad spend at all in the reporting window the whole report comes out blank, not just the ads section. / Ticket 4 - blank PDF, no error anywhere / Export finished, no error, file is empty. Nothing in the activity log. / Ticket 5 - Is my scheduled send going out? / Status has said Queued since Friday. It is Tuesday. I do not want to resend and double up. / Ticket 6 - Queued forever / Status Queued, no timestamp, no way to know the client got it. I BCC myself now. / Ticket 7 - what does Queued mean / Does Queued mean it is about to go, or that it failed and is waiting to retry? The help article does not say. / Ticket 8 - no send confirmation / No record anywhere of a report having been delivered. / Ticket 9 - Cancelling, report went to our client in the wrong currency / We are in Dublin, everything is in euro. Monday's report showed dollars. They queried the whole invoice. Cancel our account. / Ticket 10 - currency wrong on client report, we are leaving / Showed GBP for an account we set to EUR eighteen months ago. Client thought we had overcharged them. Closing the account. / Ticket 11 - Chart colours reset / Duplicating a template loses the brand colours. / Ticket 12 - logo blurry in the PDF / Fine in the editor, pixelated in the export. / Ticket 13 - Can I reorder sections / I want paid social above SEO for one client. / Ticket 14 - blank export / Quiet week, no spend, report came out empty. / Ticket 15 - Timezone on the schedule / Reports go at 9am UTC, not 9am Dublin. / Ticket 16 - Export empty for paused account / Same thing everyone seems to be hitting. No spend, empty file. / Ticket 17 - Did it send / Queued since yesterday. Please just tell me yes or no. / Ticket 18 - Cannot download last month's reports / Archive only goes back sixty days. / Ticket 19 - Duplicate report sent twice / Client got the same report twice. I scheduled it once, but I did click send when it sat on Queued. / Ticket 20 - queued then sent twice / Because I could not tell whether it had gone I sent it again. It had gone. Client now has two. / Ticket 21 - Font in the exported PDF / Headings differ from the preview. / Ticket 22 - report blank / No spend, blank file, had to explain it to the client. [PRODUCT_CONTEXT]: Loop, a weekly client reporting tool for marketing agencies; account managers send branded PDF reports to their own clients each Monday [TEAM_CAPACITY]: one engineer and one designer for a two-week cycle, about three small fixes
Example output
## 1. Queue shape 22 tickets in the batch. 12 are the product misbehaving (7 blank reports, 2 wrong currency, 2 exports not matching the preview, 1 template duplicate losing colours), 8 are the product doing what it was built to do while the person could not tell that in advance (all 7 Queued tickets, plus the 9am UTC schedule), and 2 are neither — one request, "I want paid social above SEO for one client", and one stated limit, "Archive only goes back sixty days". Two themes tie for the most tickets at 7 each: reports exporting blank when the client had no ad spend, and Queued never resolving into a sent state. ## 2. Themes | Theme | Tickets | Who it hits | Broken or Unclear | Severity | |---|---|---|---|---| | Report exports blank when the client had no ad spend in the window | 1, 2, 3, 4, 14, 16, 22 (7) | Agencies with paused or quiet clients; the empty file reaches the agency's own client | Broken | High — the agency has to explain it downstream: "had to explain it to the client" | | Queued never resolves, so the sender cannot tell whether the report went | 5, 6, 7, 8, 17, 19, 20 (7) | Every account manager sending on a schedule | Unclear | High — two of the seven ended with the client receiving the report twice, and one person has stopped trusting the status: "I BCC myself now" | | Client-facing report shows a currency the account never set | 9, 10 (2) | Agencies billing outside USD; the wrong figure lands in front of their client | Broken | Critical — the only two cancellations in the batch, and one triggered a billing dispute: "They queried the whole invoice" | | Exported PDF does not match what the editor showed | 12, 21 (2) | Every agency shipping branded PDFs | Broken | Medium — visible on client-facing output, but nobody in this batch escalated it | Singletons: 4 — duplicating a template loses the brand colours (11), the schedule fires at 9am UTC rather than the agency's local 9am (15), and the archive stops at sixty days (18). ## 3. Root cause read Report exports blank when the client had no ad spend. The most likely cause is that a zero-row ad-spend result is treated as no data for the whole document rather than for one section, so the renderer aborts instead of skipping. Ticket 3 states it outright: "if a client has no ad spend at all in the reporting window the whole report comes out blank, not just the ads section", and Ticket 2 gives the control group — "Two of my eleven clients got an empty report. Both paused ad spend in July. The other nine were fine." The tickets do not settle whether Ticket 1 is the same bug: "got headings and no charts" is a partial render, not an empty file. Question for that customer: did Harding Dental have any ad spend in the three weeks the report came out wrong? Queued never resolves. The most likely cause is that the send worker never writes its result back to the status the sender sees, so Queued is the last state anything set rather than the current one. Ticket 6 points at the missing write directly: "Status Queued, no timestamp, no way to know the client got it." Ticket 20 shows the sends themselves are at least sometimes fine — "It had gone" — so this reads as a stale display rather than a stuck queue. What the tickets do not settle is whether any send actually fails while showing Queued. Question for the Ticket 5 customer: the report that has said Queued since Friday — did your client receive it? Client-facing report shows a currency the account never set. The most likely cause is that money is rendered in whatever currency the source data carried, with the account setting ignored at render time. Ticket 10 rules out a recent misconfiguration: "Showed GBP for an account we set to EUR eighteen months ago." The tickets do not settle whether the setting is being ignored or whether the ad-platform figures arrive in their own currency and are relabelled rather than converted — Ticket 9 saw dollars in Dublin, Ticket 10 saw GBP, which is two different wrong currencies for two euro accounts. Question for the Ticket 9 customer: is the ad account behind that report itself billed in dollars? Exported PDF does not match what the editor showed. The most likely cause is that export runs a different rendering path from the preview — rasterising assets at screen resolution and substituting fonts it does not have embedded. Ticket 12 puts the two paths side by side: "Fine in the editor, pixelated in the export." Two tickets is too thin to say whether this is one shared renderer gap or two unrelated ones; the font and the logo could have separate causes. Question for the Ticket 21 customer: which font are the headings set in, and is it one you uploaded? ## 4. The cut line 1. Closes "Client-facing report shows a currency the account never set". Render every money figure from the account's configured currency, and fail the export loudly when the source data disagrees with it instead of printing whichever value arrived. Removes 2 tickets. Ranked above both seven-ticket themes because these are the only two people in the batch who left — "Cancel our account" and "Closing the account" — and the failure landed in front of the agency's own client as a money dispute rather than as a missing report. 2. Closes "Report exports blank when the client had no ad spend in the window". Treat an empty ad-spend result as an empty section, not an empty document: render the remaining sections and print a stated no-spend block where the ads section would be. Removes 6 tickets for certain, 7 if Ticket 1 turns out to share the cause. 3. Closes "Queued never resolves, so the sender cannot tell whether the report went". Write the send worker's outcome back to the status — Sent with a timestamp, or Failed with a reason — and record it where Ticket 4 looked and found nothing. Removes 7 tickets, and it is the only fix here that stops a client receiving the same report twice. This is a small fix only if the worker already records its result; if it does not, ship the timestamp on successful sends alone and scope the rest next cycle. --- capacity ends here --- Exported PDF does not match what the editor showed (12, 21). Leaving it means the logo and the headings stay wrong on branded output going to the agency's client every Monday, so expect roughly this rate of complaint to continue. Duplicating a template loses the brand colours (11). Leaving it means every duplicated template needs its colours set by hand, which is both a recurring manual cost and a plausible route to an off-brand report reaching a client. Schedule fires at 9am UTC (15). Leaving it means non-UTC agencies keep getting sends at the wrong local hour; survivable weekly, but the Monday-morning promise stays unmet for them. Archive stops at sixty days (18). Leaving it means agencies still cannot retrieve last month's reports; the cost is occasional support requests with no client-facing consequence. Reorder sections (13). Leaving it costs one unmet preference from one account, and nothing else this batch shows. ## 5. What this queue cannot tell you It cannot show the agencies whose reports went out blank without anyone noticing. Ticket 4 says "Nothing in the activity log", so a blank export leaves nothing behind to write in about, and the seven tickets here are only the ones somebody happened to open. No end client is in this batch. Every currency and blank-report complaint arrived through the agency, and two of those surfaced only as cancellations — the quieter version of that conversation, before the client queried an invoice, is missing entirely. The sample over-represents people who did the diagnosis for us — "Figured out the pattern" — and people angry enough to leave. Nobody writes in to say Monday worked, so the queue carries no denominator for any of these themes. The blank-export theme would probably read smaller over a month. Two tickets tie it to a seasonal cause — "Both paused ad spend in July" and "Quiet week, no spend" — so this batch may be catching one cluster of paused accounts rather than a steady weekly rate.
Claude

Support Tickets To Ranked Fix List

Add to Cart
Instant accessInstant access
Usage rightsCommercial use
Money-back guaranteeMoney‑back
By purchasing this prompt, you agree to our terms of service
CLAUDE-5-OPUS
Tested icon
Guide icon
4 examples icon
Free credits icon
Paste a batch of support tickets and get the short list of things to fix, ranked. Each theme is named by the failure rather than the feature, every ticket is counted once, and a product that is broken is kept apart from one that merely reads as unpredictable. Root causes come with the ticket text that points at them. The ranking has a capacity line drawn through it, so half the list is openly deferred. Closes with the blind spots in your own queue. For support leads and product managers.
...more
Added over 1 month ago
Report
Browse Marketplace