---
title: "How to Onboard a Support Hire With Your Docs"
canonical: https://supportpages.io/guides/onboard-a-support-hire-with-your-docs
updated: 2026-08-13
---

You will finish with a new support hire answering real tickets from your public help centre within their first fortnight, and a written list of every gap they hit along the way - which is the most honest documentation audit anyone in your company can produce.

## Before you start

Give them the same access a customer has, and nothing more, for the first few days. That is the whole mechanism: a new starter using only public documentation experiences your help centre exactly as a customer does, and they are the only person in the building who cannot fill the gaps from memory.

Set up somewhere for them to record gaps before day one. A shared document is enough. If logging a gap takes more than about ten seconds, it will not happen while they are busy.

## Steps

1. **Hand over the public help centre on day one, not the internal wiki.**
   No shadowing, no product tour, no private runbook. Give them the URL a customer would land on and a task that requires reading it.

2. **Give them a stack of closed tickets to answer from documentation alone.**
   Pick real, already-resolved tickets spread across topics. They draft an answer using only what is publicly published; the original resolution is the answer key.

3. **Have them log every gap as it happens.**
   One line each: the question, the article they expected to find it in, and what was missing or wrong. That log becomes the audit and the backlog at the same time.

4. **Let them ask for help, but have them log first.**
   The instinct is to ask a colleague straight away. An answer given in chat fixes the person and destroys the finding, because the gap is now invisible to everyone else.

5. **Move them onto the live queue with the log still running.**
   Real tickets surface different gaps from closed ones, particularly around the questions customers ask badly.

6. **Have them draft the articles they needed and could not find.**
   They are the only person in the company who has recently not known the answer, and that state has a short shelf life. Their draft is worth more than a subject expert's rewrite of it.

7. **Review the log at two weeks and again at four.**
   Sort by how often the gap would hit a customer rather than by how much it frustrated the hire. Those two orderings are different more often than you expect.

8. **Close the gaps inside their first month.**
   The value is in the fixes, not the list. A log that stays open until the next quarter has cost the hire's time and bought nothing.

9. **Keep gap logging running for the whole team.**
   Once the habit exists, everyone answering tickets is generating the same signal at a lower rate.

## Common mistakes

**Onboarding from an internal wiki.** It gets the hire productive and leaves the help centre untouched, so the next starter hits the same gaps, and so does every customer in between.

**Giving them read-only access to the documentation.** The person finding the gaps should be able to fix the small ones the moment they find them, even if a review step follows.

**Answering their questions in chat.** Every answer given verbally is a documentation gap that has been closed for exactly one person.

**Front-loading a week of product training.** Demos and slide decks fill the head with context that a customer will never have, which is precisely the context that makes the audit worthless.

**Leaving the gap list unactioned.** The second hire finds the same gaps, notices nothing changed, and stops logging by the end of their first week.

## When this stops scaling

This is a one-shot signal per person. Fresh eyes last roughly a month, then the hire knows too much to see what is missing, and no amount of process brings that back. You cannot hire people to generate documentation feedback, so the audit only happens as often as you happen to recruit.

That gives a clear threshold. If you take on support staff a few times a year, this is one of the best documentation audits available and costs nothing beyond the onboarding you were doing anyway. If you hire once every couple of years, the gaps go unmeasured for the whole gap between starters, and the help centre decays with nobody noticing.

For the periods in between, the continuous version of this signal is what readers searched for and did not find. [SupportPages](https://supportpages.io) records the questions a help centre could not answer, which is the same list a new hire produces, generated by customers rather than by recruitment. A new starter tells you what was missing in one fortnight; you still need something telling you the rest of the year.