Handbook

Yes — subscribe to the handbook.procedure.created/updated/deleted webhook events so an external system can react when your procedures change.

The Search icon in the Handbook's second header row opens a field that finds procedures by title, category, keywords, or the text of the entry. It's the fastest way to find a specific procedure in a growing Handbook.

By default, every Handbook procedure is available to every AI agent. Access rules let you mark a procedure (or a whole category) confidential so it is hidden from all Agent Stacks, and tick categories or procedures for specific Agent Stacks or member agents that read only chosen categories.

Group Handbook procedures into categories so they're easy to maintain and easy to scope access rules to. Categories are managed from their own list — add one with a single button, and rename, restrict, or delete from each row.

Never. Handbook procedures shape what the AI does, not what it says. If the customer should see the words, write them in a Knowledge Base article instead.

The Knowledge Base is for customers — published, indexed, multilingual, public. The Handbook is for your AI agents — internal, private, never quoted to customers. Use both.

Open Handbook, pick a category, click New procedure, write it in instruction language, set access rules if needed, and turn visibility on. AI agents start using it within seconds.

The Handbook is your internal procedure library. AI agents read it for context — escalation rules, refund policies, who-handles-what — without ever quoting it to customers.