Skip to main content
idapt
HomeCodeAI ModelsPricing
Sign inStart free
  • Home
  • Pricing
  • AI Models
  • Image models
  • Voice models
  • Video models
  • Rankings
  • New models
  • Model status
  • Multi-Model Chat
  • Voice Mode
  • Voice HUD
  • Web Search
  • Image Generation
  • Video Generation
  • Audio Generation
  • Transcription
  • Drive
  • Credentials
  • Sharing
  • Workspaces
  • Tasks
  • Memory
  • Agents
  • Subagents
  • Automations
  • Skills
  • idapt Code
  • Code Execution
  • Computers
  • Computer Use
  • Computer Assist · Soon
  • Containers
  • Cloud Computers
  • Local AI
  • AI Gateway
  • API & SDK
  • CLI
  • MCP
  • Tunnels
  • All features →
  • LLM cost calculator
  • Token counter
  • Context window checker
  • Can I run it
  • Model picker quiz
  • Savings finder
  • Video cost estimator
  • Text to speech cost
  • Transcription cost
  • API endpoint tester
  • All free tools →
  • Blog
  • Use cases
  • Comparisons
  • Best of
  • Skills
  • Learn
  • Changelog
  • Help center
  • FAQ
  • Privacy
  • Compare all models
  • Support
  • idapt Code
  • Developers
  • Quickstarts
  • API reference
  • API pricing
  • CLI
  • MCP
  • Downloads
  • Desktop
  • Badges and embeds
© idapt[email protected]TermsPrivacy PolicyLegal noticeReport content
X (Twitter)
All skills
Writing

Turn a ticket into an article

A resolved conversation becomes a help-centre page the next person finds.

Fill it in

Paste it, however messy.

How to avoid hitting it again.

Your prompt

Turn this into a help-centre article.

[the conversation]

Title it as the SYMPTOM, in the words someone would search. The person who needs
this does not know the cause, so "Fixing OAuth token refresh" is unfindable while
"Why am I being logged out every hour" is the thing they typed.

Strip the conversation. An article is not a transcript: no greetings, no
apologies, no back-and-forth where the agent asked for information. Just the
problem and the steps.

Numbered steps with what each one should show. Include the thing that is obvious
to support and not to a customer.

End with how to avoid hitting it again, if there is a way.
Never include anything from the customer: no names, accounts, emails or IDs.
Use Turn a ticket into an articleOpens with everything above already filled in.

Why this works

The person who needs the article does not know the cause, so it has to be titled as the symptom in the words they typed. This strips the conversation down to problem and steps, and removes anything identifying the original customer.

More writing skills

  • Translate a document
  • Write a first draft

Use it now in a chat in 1 click

Use Turn a ticket into an article
Rewrite and polish
  • Proofread
  • Summarize this
  • Draft a reply