How My Help Center Articles Cut Support Tickets by 58%

A great feature delivers value only when users know how to use it. I developed help center content for every release cycle, helping customers quickly understand new features and gain confidence in using them effectively.

At a glance

Role: Technical Writer
Client: A technology client with B2B and B2C products in mining industry

Worked with: Product owners, editors, developers and the customer support team
Duration: 2.5 years
Tools: RoboHelp, Madcap Flare, Whatfix, Git, Word, Snagit, mining machinery software
Result: Support tickets fell 58% in the three months after the new help center went live.

The challenge
The client kept releasing new features across several products, and customers needed to understand them quickly. They needed an experienced writer who could learn each feature fast and publish clear help content for both business and consumer users.

What I did

  • Worked with product owners to understand each feature before writing, so the articles matched how the product really works
  • Wrote help articles in simple language that end users could follow without technical knowledge
  • Worked with editors, developers and the support team to review, correct and publish each article
  • Captured clear screenshots and formatted the content so it was easy to scan and use
  • Created a separate section for troubleshooting and added the steps for customers to do it themselves.
  • The Frequently Asked Questions section was used to understand beyond user feedback, it was used to decide what section users needed help and content was curated accordingly.

The result

In the three months after the client put the new help center in place, support tickets dropped by 58%.

What the client said


Skills shown: Technical writing, product understanding, working across teams, user-focused content


Comments