Knowledge & tools
Post-call hooks
A post-call hook runs a tool automatically when a call ends — to log the outcome, create a ticket, push a summary somewhere, or trigger a follow-up. Hooks belong to a bot and run in the order you choose.
What a hook does
Each hook ties a bot to a tool configuration that fires after the call completes. The conversation's context can be passed into the tool through a parameter template, so the tool receives the details it needs (for example, the caller, the outcome, or a summary).
Configuring a hook
- Tool configuration (
tool_configuration_id) — which tool runs. Required. - Run order (
run_order) — hooks run in ascending order when a bot has more than one. - Enabled (
enabled) — turn a hook on or off without deleting it (default on). - Parameter template (
params_template) — maps call data into the tool's inputs.
A bot can have at most one hook per tool configuration. Manage hooks in the bot editor or via the post-call hooks endpoints (gated by the same bots:read / bots:write abilities).
Hooks pair naturally with voice agents — close out every call with a consistent action like writing the outcome to your CRM.