Designing a Contact Centre Intranet Hub Agents Will Actually Use
Contact centre agents do not browse the intranet for fun. They search it under pressure, often mid-call, with a customer waiting and a timer running. If your hub buries a refund policy three clicks deep behind a carousel, agents will stop using it and rely on memory or side chats instead. The fix is not a redesign; it is a content structure built around the call.
Start With the Question, Not the Department
Most intranets are organised by who owns the content: HR, Operations, Compliance. Agents think in customer questions. Restructure the top level around the ten to fifteen things callers actually ask, such as billing disputes, delivery delays, returns, and account security.
Each topic page should open with a one-line answer, not background. Put the full policy underneath for the rare deep dive. This single change cuts search time because agents recognise the question before they read the answer.
Use a Consistent Page Template
Agents move fast. Predictability beats cleverness. Every knowledge page should use the same blocks in the same order, so the eye knows where to land without reading.
- A plain-language summary in bold at the top.
- Step-by-step actions in a numbered list.
- Escalation rules and who to contact.
- Last reviewed date and owner name.
When every page looks the same, training time drops and mid-call scanning becomes almost automatic.
Write Policies as Answers, Not Documents
A twelve-page policy PDF is not a call tool. Break it into short question-led chunks that each stand alone.
- Can I waive this fee?
- What if the customer refuses?
- When must I escalate?
Link the original PDF at the bottom for audits. Agents get the answer, compliance keeps the source.
Design FAQs for the Second Screen
Keep answers under forty words and lead with the verb. Use tables for comparisons, such as delivery windows by region, because a table answers in one glance what prose takes a paragraph to explain.
| Scenario | Answer | Escalate? |
|---|---|---|
| Late delivery | Offer credit | Over 7 days |
| Duplicate charge | Refund now | Never |
Remember that many agents read this on a second screen or a narrow panel. Short lines and tables survive that layout; long paragraphs do not.
Govern, Review and Measure
A hub decays without ownership. Assign a named owner per topic and a quarterly review date, and remove anything older than twelve months unless it is confirmed.
If an agent cannot find it in fifteen seconds, the intranet has failed the call.
Track search terms that return nothing and pages agents abandon. Those gaps tell you exactly what to write next, and they are a better roadmap than any survey. Build the hub around the call, and agents will finally use it.
