Keep training up to date when the playbook changes
Updating a playbook leaves you with another job: finding the places where the old instructions still appear in training. The document may now say to contact the on-call lead, while a lesson still tells new hires to contact the support lead.
Honen connects those two pieces of work. Source sync brings updated documents into the Knowledge Base, and a scheduled Agent can check a course against them and propose changes for your team to review.
Give the Agent current knowledge and a clear task
Honen AI can build you a full course from a topic or your team’s documents. Once people start using it, the same documents can help you keep the training current.
You can connect sources such as Google Drive, SharePoint, OneDrive, or GitHub documentation and configure them to sync into the Knowledge Base. When a connected playbook changes, source sync refreshes Honen’s copy. The course still needs to be checked against it.
That’s a task you can give an Agent. Give it access to the relevant playbook and permission to propose changes to the course, then explain what it should look for:
Check the support onboarding course against our escalation playbook. If the instructions differ, propose a course update and explain what changed in the source.
In Automations, you choose when the Agent runs and which time zone the schedule uses. A weekly check might suit a playbook that changes occasionally. You can choose a schedule that fits how often your team revises the material.
Review the difference before it reaches learners
In this example, the Agent finds that the lesson names the support lead even though the playbook now names the on-call lead. It proposes changing the instruction so the course reflects the new process.
Your team can compare the proposal with the earlier version and check it against the source. The order of the actions matters too: “Contact the on-call lead before handing off the case” teaches something different from “Send the case to the on-call lead.” A reviewer who knows the process can check that distinction before approving the update through the team’s publishing process.
Source sync, the Agent’s check, and human review each do a different job. Together, they give you a proposed change to assess, with a reason for it. When the playbook changes again, the next scheduled check can pick up the comparison.
