Playbooks

Build and run a playbook

Automate repeatable support work with triggers, conditions, actions, and a dry run.

Playbooks cover everything from a simple assignment rule to a multi-step customer-outcome workflow. Open Playbooks and choose New playbook, or start from a template.

Define when it should run

Choose the event or timing that starts the playbook, then add conditions to keep it focused. Conditions can use conversation, customer, account, milestone, status, tag, assignment, waiting-time, office-hours, or satisfaction information.

For example: when a conversation receives a poor satisfaction rating, assign it for review and create a follow-up. Missing information doesn’t count as a successful condition match.

Choose ordered actions

Add actions in the order they should happen. Available actions include assignment, tags, priority, status, snoozing, private notes, follow-ups, notifications, saved replies, AI drafts, and webhook connectors.

More involved playbooks can collect information, wait for replies, request human approval, verify an outcome, or escalate with supporting evidence.

Choose actions by their effect. Generating an AI draft leaves something to review; a configured sending action is different. Use approval before any step where your team should make the final decision.

Dry-run before enabling

New playbooks save paused. Use the dry run to inspect how the conditions and actions apply without executing them. Review the plan and any approval requirements, then deliberately choose Enable.

A dry run does not send messages or perform the listed actions. It also doesn’t replace checking the first real executions after enablement.

Monitor and recover

Use Log to inspect executions, step results, and failures. Pause a playbook when you need to stop new steps while investigating. Pausing can’t undo a request already accepted by another service.

An ambiguous external result needs an administrator’s Reconcile / retry decision. Confirm whether the provider accepted the action before retrying, so a timeout doesn’t become a duplicate message or operation. Later edits don’t rewrite a plan that was already approved.

Browse all topics →

Still need a hand? Ask our team.