Turn Support Ticket Topics into a Help Center Category Structure and Article List

Groups your pasted ticket topics into 5-8 customer-language categories, flags duplicates and orphans, and ranks proposed article titles by ticket volume.

You getCategories, article table with columns and duplicates merged

Prompt

Prompt
Act as a help center content strategist who organizes self-service sites for support teams.

I will paste a list of ticket topics right after this prompt, ideally with a ticket count next to each. Turn them into a help center category structure and a prioritized article list.

Rules:
1. Create 5-8 categories named in the words customers use in tickets, not internal team or feature names (e.g. "Billing and payments", not "Revenue Ops").
2. Put every topic in exactly one category. If a topic fits two, pick one and note the cross-link.
3. Flag duplicates: topics that describe the same problem in different words become one article, with the merged topics listed.
4. Flag orphans: topics that fit no category or appear only once. Say whether to drop, merge or keep each one.
5. Write article titles as the task or question a customer would type into search, under 70 characters.

Output format:
1. Categories: name, one-line scope, total ticket count.
2. Article table with columns: Rank | Article title | Category | Ticket topics covered | Ticket volume. Sort by volume, highest first.
3. Duplicates merged (bullets).
4. Orphans and recommendation (bullets).

If counts are missing, rank by how often a topic appears and say so. End with one line on gaps or assumptions in the data.

Example output

Example for: a project management SaaS with 41 ticket tags covering 1,860 tickets over 90 days.

1. Categories

CategoryScopeTickets
Account and loginPasswords, two-step login, profile changes512
Billing and paymentsCards, invoices, plan changes438
Projects and tasksCreating, moving, restoring and importing work390
Team and permissionsInviting people, roles, guest access246
IntegrationsSlack, Google Calendar, Zapier198
Notifications and emailWhat alerts you get and how to change them76

2. Article List (top 12)

RankArticle titleCategoryTicket topics coveredVolume
1Reset your password or unlock your accountAccount and loginforgot password, locked out, reset link expired318
2Update your card or fix a failed paymentBilling and paymentscard declined, payment failed, update card204
3Add, remove or change a team member's roleTeam and permissionsinvite user, remove user, change role171
4Download an invoice or receiptBilling and paymentsinvoice copy, receipt for expenses134
5Restore a deleted task or projectProjects and tasksdeleted by mistake, recover project128
6Turn on two-step login and fix code problemsAccount and login2FA setup, code not arriving122
7Connect Slack and choose which updates postIntegrationsSlack setup, too many Slack messages117
8Move tasks between projectsProjects and tasksmove task, copy task104
9Cancel or downgrade your planBilling and paymentscancel, downgrade, refund request100
10Import tasks from a CSV fileProjects and tasksCSV import, Trello migration96
11Sync due dates with Google CalendarIntegrationscalendar sync, dates not showing81
12Stop or change email notificationsNotifications and emailtoo many emails, unsubscribe76

3. Duplicates Merged

  • "Locked out", "can't log in" and "reset link expired" are the same problem: one article (rank 1).
  • "Refund request" and "cancel subscription" usually arrive together: merged into rank 9, with a refund section.
  • "Trello migration" is a CSV import case: merged into rank 10 as a worked example.

4. Orphans and Recommendation

  • "Dark mode" (3 tickets): drop; answer with a saved reply.
  • "API rate limits" (7 tickets): keep, but place under Integrations as a developer note.
  • "Feature request" (22 tickets): not a help topic; link to the feedback board from the help center footer.
  • "Other" (41 tickets): too vague to sort; retag a sample of 20 before the next review.

Assumption: tag counts reflect real volume, but 41 untagged tickets may hide one more category.

Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Requiring customer-language category names stops the structure from mirroring your org chart, so people find articles faster.
  • Ranking by ticket volume tells you which articles to write first for the biggest drop in tickets.
  • Separate duplicate and orphan sections catch the messy tags that usually inflate article counts.

Use when building or reorganizing a help center. Export 60-90 days of ticket tags or subject lines with counts, then paste them into ChatGPT, Claude or Gemini right after the prompt.

Common edits

  • Change the category range to 3-5 for a small product with few ticket types.
  • Add a column for 'Existing article URL' to audit what you already have against the new list.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Customer Support