Skip to content
Writing & content

Get help articles and product documentation written

Support answers the same questions every day, and the help center describes a version of the product from two releases ago. A technical writer can turn your product and your tickets into articles people can follow. Give them access to the product and to the questions customers actually ask.

TW-DRAFTDraft

Write 20 help articles from our most common support tickets

Budget
You set this
Timeline
4 weeks
Category
Writing & content

Scope

Our support team answers the same setup and billing questions every week. We want 20 help articles written from our top ticket topics, with screenshots, and published in Intercom. A support lead will review each article, and we will provide a test account.

Deliverables

  • Topic list from the ticket export
  • 20 articles with screenshots
  • Articles published in Intercom, with categories
  • Style notes for future articles

Skills

  • Technical writing
  • Intercom
  • SaaS
  • Documentation
An example brief. Describe your task and the brief writer drafts one like it.

What the work involves

The scope a provider will expect to cover. Leave out what you don't need, and say so in the brief.

  • Finding the topics that matter from support tickets, help center searches and the product itself
  • A structure for the help center, so articles are easy to find
  • Step-by-step articles with screenshots, in plain language
  • Review with your product and support teams for accuracy
  • Publishing in your help desk, or delivering ready-to-paste files

What to put in the brief

The facts a provider needs to give you a real price instead of a guess. Write it in your own words: the brief writer turns it into scope and deliverables, asks about anything missing, and you can edit every line before it goes out.

Start the brief
  1. 1The product, and the parts the documentation should cover
  2. 2Where the articles live: Zendesk, Intercom, Notion, your own site
  3. 3How many articles, or the ticket topics you most want answered
  4. 4The access the writer gets: a test account, a ticket export, a product expert
  5. 5Your tone, and any existing style guide

Ask each provider

Every proposal opens a conversation, so you can ask before you accept. The answers are often what separates two similar prices.

  • Can you show documentation you've written for a similar product?
  • How will you check the steps are accurate?
  • How would you keep the articles current after releases?

Questions companies ask

Which articles should be written first?

Start from your support data: the most common ticket topics, and searches in your help center that find nothing. Attach a ticket export or the top topics to the task so writers can see the scope.

Can't the support team write the articles?

They know the answers but rarely have the time. A writer can interview them and draft the articles, so their time goes on review rather than writing.

Ready to hand it off?

Describe it in a sentence or two. The brief goes to every provider who lists Writing & content, and you compare their proposals side by side. Posting is free, and you set the budget.

Post a task

More writing & content guides

All guides