🏫
Obvious University
Website
  • 👋Welcome to Obvious University!
  • Strategy
    • Sprints
      • 1️⃣Map
      • 2️⃣Sketch
      • 3️⃣Decide
      • 4️⃣Prototype
      • 5️⃣Test
    • Benchmarking
    • Research
      • 1️⃣Research guide
      • 2️⃣How to recruit users
      • 3️⃣How to conduct an interview well
      • 4️⃣How to take notes
      • 5️⃣How to prep for remote research
      • 6️⃣How to throw a watch party
      • 7️⃣How to create artefacts
  • Working with Features
    • Building with AI
      • 1️⃣Understand the tech
      • 2️⃣Map your product
      • 3️⃣Build a proof of concept
      • 4️⃣LLM Inputs
      • 5️⃣LLM Responses
    • Building Help and Support
      • 1️⃣How to scope a support experience
      • 2️⃣How to design discovery for support
      • 3️⃣How to design a support centre
      • 4️⃣How to write good support articles
  • Product Design
    • Microcopy
      • 1️⃣How to write well
      • 2️⃣How to write phrases
      • 3️⃣How to write messages
      • 4️⃣How to create a voice
    • Typography
      • 1️⃣How to compose type
      • 2️⃣How to create a type scale
      • 3️⃣How to pick typefaces
      • 4️⃣How to pair typefaces
    • Design System
      • 1️⃣Introduction to design systems
      • 2️⃣How to audit a design system
      • 3️⃣How to run a design system pilot
      • 4️⃣How to set up a design foundation
      • 5️⃣How to build components
      • 6️⃣How to document a design system
      • 7️⃣How to enable adoption and govern a design system
    • Mobile Engineering
      • 1️⃣Trunk based development
      • 2️⃣Agile development terminology
      • 3️⃣Git commit messages
      • 4️⃣Code review and pull requests
      • 5️⃣Readings
  • Delivery
    • Project Management
    • Collaboration
  • Hiring and Growth
    • Growth
      • 1️⃣Design growth framework
      • 2️⃣How to give ongoing feedback
      • 3️⃣How to check-in every quarter
      • 4️⃣How to address underperformance
      • 5️⃣FAQs
    • Hiring and careers
      • 1️⃣The Hiring Process
      • 2️⃣Diverse and Inclusive Hiring
  • PEOPLE EXPERIENCE
    • Benefits and Perks
      • 1️⃣Paid time off
      • 2️⃣Insurance and healthcare
      • 3️⃣Continuing education
      • 4️⃣Speaking at conferences
    • Starting at Obvious
      • 1️⃣Introducing Obvious
      • 2️⃣Set up your workspace
      • 3️⃣Onboarding
      • 4️⃣Finances
      • 5️⃣Code of Conduct
    • Employment policies
      • 1️⃣Equal opportunity employment
      • 2️⃣At-will employment
      • 3️⃣Employee records and privacy
      • 4️⃣Prevention of sexual harassment
      • 5️⃣Drugs and alcohol
      • 6️⃣Fraternisation
      • 7️⃣Non-compete and non-solicitation
      • 8️⃣Non-disclosure
Powered by GitBook
On this page
  • 👋 Introduction
  • 1️⃣ Title
  • Address a specific query
  • Start with a verb
  • Maintain consistency for terms
  • 2️⃣ Content
  • Use a “Who, What, How” structure
  • Be action-oriented, not apologetic
  • Make it scannable
  • 3️⃣ Footer
  • Get feedback
  • Link to related articles
  1. Working with Features
  2. Building Help and Support

How to write good support articles

PreviousHow to design a support centreNextMicrocopy

Last updated 1 year ago

👋 Introduction

In a self-serve support experience, users read articles to resolve their queries. The articles should be easy, direct and remove chances of miscommunication. This should be done while being strongly aligned to the product vocabulary. Here’s how to strike this balance well:

1️⃣ Title

Address a specific query

Write specific articles addressing a query instead of writing articles for a feature. Redundancy is okay as long as users are able to get to resolution as soon as possible.

Start with a verb

The user is seeking support because they were trying to complete a task and couldn’t. Make your titles actionable.

Maintain consistency for terms

Use the same words for the same features across articles. Using synonymous words for the same features across articles is disorienting for users.

2️⃣ Content

Use a “Who, What, How” structure

Introduce the task the user is trying to complete. If the task is applicable to a specific user group, mention that and tell the user how to complete the task.

Be action-oriented, not apologetic

In help articles, using phrases like “We’re sorry for the inconvenience” reinforces that the user ran into a problem and needed help. Instead, jump into the solution and help the user complete the task.

Make it scannable

Use UI elements to make it scannable. The last thing a frustrated user wants to see is a block of text.

3️⃣ Footer

Get feedback

This will help you improve your articles. Poor feedback on the article can trigger the high-touch flow (Example: Open up a chatbot, or create a ticket).

Link to related articles

Anticipate what related queries the user might have — these could be queries related to that feature or queries with a similar intent. This helps the user find what they need easily.

4️⃣