Turn a Resolved Support Ticket Thread into a Help Center Article

Paste a solved ticket thread and get a ready-to-publish help article with customer details removed, verb-first fix steps, and symptoms written the way customers search.

You getTitle, who this affects and symptoms

Prompt

Prompt
You are a senior support content writer who turns solved tickets into help center articles.

I will paste a resolved support ticket thread right after this prompt. Turn it into one public help center article that the next customer with the same problem can follow without contacting us.

Rules:
1. Remove every customer detail: names, emails, account IDs, order numbers, company names, private links and anything only that customer would know. Use generic wording like "your account".
2. Write the fix as numbered steps. Each step starts with a verb, covers one action, and names the exact button, menu or field used in the thread.
3. List symptoms in the customer's own words, lightly cleaned from the thread, so the article matches what people type into search.
4. Leave out things the agent tried that did not work, unless a step needs to warn against them.
5. If the thread does not show how the fix was confirmed, say so instead of guessing.

Output format:
- Title: phrased as the problem, under 70 characters
- Who this affects (1-2 sentences)
- Symptoms (bullets, customer wording)
- Cause (2-3 plain sentences)
- How to fix it (numbered steps)
- If this didn't work (what to send support)
- Search keywords (5-8 phrases)

End with Notes for the editor: details removed, assumptions made, and gaps to check with the product team.

Example output

At a glanceFixing invoices stuck on SendingVerb-first fix steps from the generated help article
  1. Open Email Sending settingsSettings, then Email Sending
  2. Check connection statusLook for Reconnect required
  3. Reconnect the mailboxSign in to the same email account
  4. Approve send permissionAllow Send email on your behalf
  5. Filter invoices by SendingReturn to Invoices
  6. Retry sendSelect stuck invoices and click Retry send
  7. Confirm status is SentShould update within a few minutes

Example for: a 14-message thread from an invoicing app where a customer's invoices were stuck in "Sending" after their email connection expired.

Invoices Stuck on "Sending" and Never Reach Clients

Who this affects: Accounts that send invoices through a connected Gmail or Outlook address instead of the default app sender. It usually appears 90 days after connecting the mailbox.

Symptoms

  • "My invoices just say Sending and never go out"
  • "Client says they never got the invoice"
  • "The spinner next to the invoice won't stop"
  • "Nothing in my Sent folder from the app"

Cause

When you connect your own mailbox, the email provider grants access for a limited time. Once that access expires, the app can't send on your behalf, so invoices wait in the queue. No error appears on the invoice itself.

How to fix it

  1. Open Settings and select Email Sending.
  2. Check the status next to your connected address. If it shows Reconnect required, continue.
  3. Click Reconnect and sign in to the same email account.
  4. Approve the Send email on your behalf permission when your provider asks.
  5. Return to Invoices and filter by status Sending.
  6. Select the stuck invoices and click Retry send.
  7. Confirm each invoice now shows Sent within a few minutes.

Don't delete and recreate the stuck invoices. This creates duplicate invoice numbers.

If this didn't work

Contact support and include:

  • The invoice numbers still showing Sending
  • A screenshot of the Email Sending settings page
  • Whether you use Gmail, Outlook or another provider

Search keywords

  • invoice stuck sending
  • invoice not delivered to client
  • invoice email not sent
  • reconnect gmail invoices
  • outlook invoice sending failed
  • sending status won't change

Notes for the editor

  • Removed: customer name, business name, account ID, two invoice numbers, the client's email address, and a link to the customer's dashboard.
  • Assumed: the 90-day expiry applies to both Gmail and Outlook. The thread only confirms Gmail; check with the product team.
  • Gap: the thread doesn't say whether the app emails the user when the connection expires. If it does, add that to Symptoms.
  • Excluded: the agent's first suggestion to clear the browser cache, which did not help.
Written by AI from this prompt. Your results will vary.

Tips and common edits

Why this works

  • Writing symptoms in the customer's own words makes the article match real search phrases rather than internal product jargon.
  • Verb-first, one-action steps that name exact buttons are easy to scan and follow without contacting support.
  • The editor notes flag removed data, assumptions and gaps, so a reviewer can check accuracy before publishing.

Use after closing a ticket you expect to see again. Have the full thread ready, including the agent's final fix. Works in ChatGPT, Claude or Gemini; check your company's data policy before pasting ticket text.

Common edits

  • Add your help center's tone rules, such as second person, no exclamation marks, or a reading-level target.
  • Ask for a short internal macro version that agents can paste into future replies to the same issue.

Prompt details

By
Prompts-GPT editors
Published

Did this prompt work?

Keep exploring

More in Customer Support