Approved sources
Product documentation, runbooks, incident records, network procedures
Telecoms, IT and support teams work from product guides, runbooks and incident records that grow every week. During an incident, engineers need the right runbook immediately, and support agents need consistent answers across chat and tickets. Knowledge is often split across Confluence, Jira, GitHub and shared drives.
Who uses it: Network operations and IT support, customer support agents, site reliability and engineering teams.
Illustrations of what teams could test. Not customer data.
Start with the material approved for the topic: product documentation, runbooks, incident records, network procedures.
Search product guides and incident runbooks: step-by-step response procedures. Guide support with approved Jira, Confluence and GitHub read actions. Review channel details and recorded human handovers in configured Chatwoot / OMNI conversations. Prepare reusable knowledge articles.
Apply topic permissions and approve access to external tools and services.
Product documentation, runbooks, incident records, network procedures
Search product guides and incident runbooks: step-by-step response procedures. Guide support with approved Jira, Confluence and GitHub read actions. Review channel details and recorded human handovers in configured Chatwoot / OMNI conversations. Prepare reusable knowledge articles.
Apply topic permissions and approve access to external tools and services.
Choose a real business question, approved source material and a reviewer. Test missing information, exceptions and access restrictions before expanding use.
These examples show possible evaluation tasks. They are not customer case studies, verified results or a guarantee of regulatory compliance.
Bring sample sources and clear requirements. Review the answers and controls before rollout.