Contact center

Documenting Support Processes Agents Actually Use

Write support documentation agents open during a live call: short pages, clear owners, simple structure, easy search and a routine that keeps it current.

Call editorial team · Published · 5 min read

Most support teams have documentation. Very few have documentation that agents trust enough to open in the middle of a call. The binder is out of date, the shared drive has four versions of the refund process and the one colleague who knows the answer is on holiday. So agents guess, ask a neighbour or improvise. Customers get inconsistent answers, and new hires take months to feel confident.

A support agent reading a short procedure on a screen beside a headset
Illustrative image

This guide is about writing and maintaining documents for the people who use them under pressure. For knowledge that also feeds automated assistants, see Building a Knowledge Base for Support and AI; for the habit of turning call insights into updates, see Finding Knowledge Gaps from Call Reviews.

Why documentation gets ignored

Common reasons agents stop opening it

  • Too longPages of background before the answer. A caller cannot wait while an agent scrolls.
  • Out of dateOne wrong answer teaches agents not to trust any page.
  • Hard to findTitles written in internal jargon, not in the words callers use.
  • No ownerNobody is responsible, so nobody fixes it.
  • Written onceIt describes how the process was supposed to work, not how it works.
  • Not testedNobody has tried to follow the steps from scratch.

Decide what deserves a page

You cannot document everything, and you should not try. Start with the calls that matter most, and keep the rest in people's heads until they prove they need a page. A useful ranking combines how often something happens with how costly a mistake is.

Call typeFrequencyCost of an errorPriority
Top ten repeated questionsHighLow to mediumWrite first, keep very short
Refunds, exceptions and approvalsMediumHighWrite carefully with limits and approvers
Urgent or safety issuesLowVery highWrite as a clear step list; test it
Rare edge casesVery lowVariesAdd a short note, expand only if they recur
Internal tool how-tosMediumLowUse the tool's own guides where they exist

Write for a live call

Agents scan; they do not read. Put the answer first, then the steps, then the exceptions. Use plain language that matches what callers say. A good page fits on one screen and uses a repeatable pattern, so that agents learn where to look.

A template that works for most procedures

  1. TitleNamed after the caller's problem, not the department.
  2. When to use itOne sentence: the situation this page covers.
  3. StepsFive or fewer numbered actions, each a single instruction.
  4. What to sayOne or two phrases the agent can use, if wording matters.
  5. Exceptions and limitsWhen to stop and escalate, and to whom.
  6. Owner and dateWho maintains the page and when it was last checked.

Organise so people can find things

The most useful structure is the one agents guess correctly. Group pages by what the caller wants (billing, delivery, account access) rather than by internal team. Keep the hierarchy to two levels. Rely on search for the rest, and check what agents search for, because their search terms show what is missing. Link between related pages so that an agent who lands in the wrong place can move on quickly. Using Knowledge Sources in Call shows one way to keep content in a searchable place.

Scripts and wording

Some situations call for exact words: a recording notice, a verification question, a regulated statement. Mark these clearly and keep the rest flexible. Over-scripted calls sound robotic; under-scripted ones risk saying the wrong thing. How to Write a Sales Call Script and How to Open and Close a Support Call offer guidance on balancing the two.

Give every page an owner and a review date

Maintenance is what separates useful documentation from a graveyard. Every page needs a person responsible, a date it was last checked and a trigger to update it. Triggers include product changes, policy changes, repeated questions from agents and errors found in call reviews. Set a review cycle suited to the content: weekly for volatile pages such as promotions, quarterly for stable ones.

A light maintenance routine

  1. CollectAgents flag unclear or wrong pages with one click or a message.
  2. TriageThe owner reads flags weekly and decides what to change.
  3. UpdateChange the page, note the date, and tell the team if the change matters.
  4. VerifyCheck by following the steps as a newcomer would.
  5. RetireArchive pages that nobody has opened for a long time.

Mistakes that make documentation fail

A useful test is to hand a page to someone who has never done the task and watch what they do. Wherever they hesitate or ask a question, the page is unclear. Fix it and repeat.

Involve the people who use it

The strongest authors are often agents. They know which questions come up and which wording works. Let them draft pages, then have the owner review for accuracy. Recognise contributions publicly. A page written by a colleague is more trusted than one handed down from head office. Pair this with onboarding: ask each new hire to note where the documentation confused them, and fix those places. They see problems that experienced staff have learned to ignore. A 30-Day Onboarding Plan for New Agents includes this idea.

Check that it works

Finally, keep the effort proportionate. A team of ten does not need a documentation department. It needs a handful of clear pages, a person who cares about them and a habit of fixing a page the moment someone notices it is wrong.

Keeping documents close to the call in Call

In Call, scripts can be attached to a phone line and shown to the agent during the call, and branching scripts can be drawn as a diagram. Knowledge sources hold the content an AI agent answers from, and message templates keep written replies consistent. The how-to guides inside the product describe each screen. See Writing and Using Call Scripts in Call, Branching Call Scripts with the Script Diagram and Message Templates in Call: Writing Once, Reusing Everywhere.

Frequently asked questions

How long should a support procedure be?

Short enough to read on one screen during a call. If it is longer, split it into separate pages or move background into a linked page.

Who should write the documentation?

A mix: agents draft because they know the real questions, and an owner reviews for accuracy and consistency.

How do we keep documents current?

Give each page an owner and a review date, make it easy for agents to flag errors and update when products or policies change.

Should we use video?

Short videos can help for visual tools, but text is easier to scan and search during a call. Use both where they add value.

How many pages do we need?

Fewer than you think. Start with the most frequent and the riskiest calls and add pages only when a gap appears in real calls.

Keep scripts and answers at agents' fingertips in Call

In the demo console you can try incoming calls in a simulation.

Related guides