A support article was probably opened by someone in a hurry, and possibly annoyed, scanning for the step they are currently on. Anything before the first instruction serves as a barrier unless it directs them to the wrong article.
Structure is key. Each article should include one task. Match the problem’s description with the article title. Explain the next steps after each point.
Stress makes people skim, so extra words are a liability. Use single sentence instructions. Use the labels on the interface, unless they, like most interface elements, are on the wrong case. The button label is Add member, not Invite colleague.
A generated walkthrough makes sensible steps that the users might take. This particular one makes the user open Settings and Accounts because that is what other applications usually have under account-related settings, even though in your case that is behind a profile menu. The generated walkthrough correctly describes the situation, guides the users to the incorrect location, and creates the ticket in the process that it should have prevented.
The author performs the task step by step on a newly created account. The author adds their step-by-step notes as they go. After drafting their notes, the author performs the steps in order and amends their draft, noting where steps are missing. Administrator permissions related steps are placed at the top of the draft. That way, potential issues resulting from admin permissions are not discovered at the bottom of the draft.
Support content is worth the cost when it is linked to the product. An article answering the concerned question prompted by an error message should be accessible from that message. We tag each article with the screens and errors they relate to which provides your team a map to target the help where the confusion is.
One rate, whatever the format: $10 per 100 words. You are paying for the writer’s time and judgement, so the price scales with the words rather than with a package tier.
| Typical support article | Words | Writing | Fee (1%) | You pay |
|---|---|---|---|---|
| Single article | 400 | $40 | $0.40 | $40.40 |
| Five articles | 1,600 | $160 | $1.60 | $161.60 |
| Full section | 4,000 | $400 | $4 | $404 |
The writer receives 100% of the writing price. Our 1% fee is added on top of it, and 0.5% is donated to tree planting. Full pricing breakdown.
Ask on the contact page and a person will answer, usually the same working day. For a live order, reply to your confirmation email and it reaches whoever is handling it.
Ask on the contact page and a person will answer, usually the same working day. For a live order, reply to your confirmation email and it reaches whoever is handling it.
We mark the location of a screenshot and give specifics of what should be on the screenshot. We do not prepare the final images. The appearance of GUIs changes regularly, and screenshots taken by an external contributor get stale in your database with no one aware. The majority of teams prefer capturing screenshots for their own builds.
Each article provides a list of interface labels it relies on. Even if just one of those labels changes, you know which articles you must reopen. It makes a big redesign into a short, five minute, list check, instead of having to read the entire help center.
Completely. Copyright transfers to you on delivery, with no attribution requirement and no licence back to us. Nothing written for you is resold, repurposed or republished.
Reviews from completed, paid orders in this category.
Mostly excellent. Your improvements to the auth section are better than what our engineers wrote. Your pagination endpoints, however, were explained in the spec according to how they behave rather than how they are, which required two revisions. Our spec is incorrect in that area as well.
Our release notes went unread, but they serve the purpose of listing what breaks and what doesn’t when considering whether to upgrade. Two customers actually took the time to send thank yous in the same week, something that had never happened before.
Our releases happen every fortnight, and our notes have evolved into change logs. To keep things organized, the writer has noted what changed within a card or view and what changed underneath. Each note is a brief summary of the change. The biggest metric I’m interested in post release is the volume of support tickets. It always dips.
We do not ask you to take the no-AI promise on trust. Each draft is run through these platforms and the reports are attached to your delivery email.
Originality.aiAI detection + plagiarism
GPTZeroAI detection
TurnitinAI detection + similarity
CopyleaksAI detection + plagiarism
Winston AIAI detection
ZeroGPTAI detection
SaplingAI detection
Content at ScaleAI detection
Send the brief, get a human draft back within 3 days. No account, no subscription, no AI.
$10 per 100 words · all of it to the writer · 0.5% to trees