Field notes
When self-service coverage lags ticket themes
A field note on matching knowledge and portal forms to the ticket themes that actually arrive each month.
Many support portals publish dozens of articles while three ticket themes absorb half the queue. Coverage lags when content owners celebrate publish counts instead of theme overlap.
Map the top ten ticket categories to portal entry points: form, article, chatbot intent, or none. Gaps become obvious: a busy VPN category with only a generic network article, or an access-request form buried three menus deep.
Hold a short clinic with agents and content owners. Agents bring recent ticket examples; content owners bring article analytics. The meeting ends with five concrete coverage fixes, each with an owner and a date—not a vague content roadmap.
Revisit the map after one release cycle. Themes shift when products launch or offices change. A static portal catalogue drifts from the desk within a quarter.