How to Write Knowledge Base Articles That Reduce Email Volume

Write for the Question Behind the Question

Customers who email about their refund status are not just asking "where is my refund?" They want to know: Has the refund been processed? How long will it take? Will it go back to the original payment method? Can I get it faster? A knowledge base article that only answers the surface question will reduce some emails, but an article that addresses all of these related concerns will reduce significantly more.

For every article you write, ask yourself: "What would the customer ask next?" Then include that answer in the same article or link to it prominently. The goal is to resolve the entire chain of questions in one visit, not just the first question.

Match the Language Customers Use in Emails

Read your actual support emails and note how customers describe their problems. They rarely use your product's terminology. If customers email asking "why can't I get in to my account," your knowledge base article should be titled "Why You Cannot Access Your Account" rather than "Authentication Error Troubleshooting." Match the exact phrases and vocabulary your customers use so the article appears in search results when they look for help.

Place Articles in the Email Path

An article can only deflect an email if the customer sees it before sending the email. Place your most relevant articles in these locations:

• Contact page: Before showing your email address, display suggested articles based on common reasons for contact.
• Auto-reply emails: When a customer sends an email, the auto-reply should include links to the three to five most relevant knowledge base articles based on the email subject.
• Help center landing page: Make your most-viewed articles prominent on the help center home page so customers see them before searching.
• In-app help: Surface relevant articles contextually within your product where customers are most likely to encounter issues.

Include Specific Actions

Articles that tell customers exactly what to do reduce emails more than articles that explain concepts. "Click Settings, then Billing, then Update Payment Method" generates fewer follow-up emails than "You can update your payment method through your account settings." Specific, actionable instructions give customers confidence that they can resolve the issue themselves.

Address Common Edge Cases

The articles that fail to prevent emails are often ones that cover the standard case but miss common variations. The password reset article works for customers with standard accounts but does not mention what to do if you have a social login. The return policy article covers standard returns but does not mention sale items. Every unaddressed edge case is an email waiting to happen.

Review the emails you still receive about topics that have knowledge base coverage. Those emails reveal the gaps: the edge cases, exceptions, and situations your current articles do not address. Add those scenarios to the existing articles.

Measuring the Impact on Email Volume

Track email volume by topic before and after publishing knowledge base articles. If you receive 100 emails per week about password resets and publish a comprehensive article, monitor whether that number drops over the following weeks. A 30 to 50 percent reduction for well-covered topics is a realistic target. See How to Measure Knowledge Base Effectiveness for the full measurement framework.