# How to write good support articles

## 👋 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.

<figure><img src="/files/oxZBjRf2uiuqbmjLFJAo" alt=""><figcaption></figcaption></figure>

### Start with a verb

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

<figure><img src="/files/qxDFKd1pXcbm6qMsgR98" alt=""><figcaption></figcaption></figure>

### 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.

<figure><img src="/files/EuoZ3e1A9Gw3QepPLBl0" alt=""><figcaption></figcaption></figure>

***

## 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.

<figure><img src="/files/sPnkdcmEbncZO1WGCp9X" alt=""><figcaption></figcaption></figure>

### **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.

<figure><img src="/files/vA0OgypZvcPE928KDoJr" alt=""><figcaption></figcaption></figure>

### M**ake it scannable**

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

<figure><img src="/files/lP2ToZgpCLvrfXw5R1YI" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/RHbbs4H1ReEMNpWhZp2l" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/r31GVm6WlauVpeGoHdVj" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/gkhgevnBV3LPbZO9tlwF" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/cAtAZIU6loYqrnSZQnYl" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/Kn6p7IgUfDVlDXKp4lPa" alt=""><figcaption></figcaption></figure>

***

## 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).

<figure><img src="/files/e7m0a8FlmxflC4sS5C6H" alt=""><figcaption></figcaption></figure>

### L**ink 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.

<figure><img src="/files/mxge45AmwefPFawZ8sI3" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://university.obvious.in/working-with-features/building-help-and-support/how-to-write-good-support-articles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.