Last updated:
Procedures and team approval for actions
Write playbooks your agent follows step by step, ask visitors to confirm before an action runs, and let a person approve sensitive actions first.
- NewProcedures on the Actions tab: steps to give an instruction, ask the visitor, call an action, check a condition or end.
- NewStart from a template: Refund request, Cancel a subscription or Reschedule an appointment.
- NewAsk the visitor to confirm first on a step, and mark actions Only inside procedures so they never run on their own.
- NewOn Pro, Requires team approval holds an action until someone approves or rejects it on the new Approvals page.
- NewThe visitor is told the request is with your team, can keep chatting and sees the outcome in the same chat.
- ImprovedApproval requests arrive by email, as a Slack alert and as webhooks, and a waiting approval brings its conversation into the Inbox.
Some requests need more than an answer: a refund, a cancellation, a new appointment. Procedures let you write down how your team handles them. Open the Actions tab, go to Procedures and click Add procedure, or start from a template. Each step is an instruction, a question for the visitor, an action to call, a condition or the end, and the agent works through them in order. Procedures are included from Starter.
For steps that change something, tick Ask the visitor to confirm first, and intoCHAT's server only runs the action after the visitor has seen the values and replied. Actions you mark Only inside procedures are refused anywhere else, so a refund API is only reached through your refund procedure.
On Pro you can go one step further and switch on Requires team approval for an API action or a procedure step. The agent then tells the visitor their request is with your team. Your team gets an email, a Slack alert or a webhook, decides on the Approvals page, and the outcome is posted in the visitor's chat. An approved action runs once, with exactly the values that were waiting.