AI Agent Management
Procedures
Write a repeatable customer process with instructions, conditions, and actions.
Overview
Procedures organize a multi-step support process. The editor also uses the term Playbook for the saved document. Define when the process should run, write its steps, reference the actions it needs, and publish it when the preview is ready.
Create a procedure
- Open Build → Procedures and create a new procedure.
- Describe the process to start with AI assistance, or write the instructions in the editor.
- Set the name and When to trigger description.
- Add the instructions, conditions, actions, and context values needed for the process.
- Save the draft and test its branches in Preview.
- Choose Publish and confirm the procedure becomes Live.
Start it by itself
The When to trigger sentence starts the procedure when a customer's message matches it. Add more ways to start from the trigger menu; each one is a chip inside the sentence, where you added it, and a line below reads back how the procedure starts.
| Chip | What it does |
|---|---|
| No reply | Starts when the customer has not answered an AI reply for 1 minute to 24 hours. The procedure then starts only from this chip, never from a customer's message. One per channel. |
| Repeat | Starts again at a set interval, 2 to 10 times in total, until the customer replies. Needs a No reply chip. |
| Schedule | Starts at set times: once, every few minutes or hours, daily, weekdays, weekly, monthly or by cron, in a chosen timezone. More options sets start and end dates, skip dates, business hours, retries, a time limit, pausing after failures and email alerts. A procedure can have up to 10. |
| Channel | Limits the procedure to the channels you pick. A follow-up is only sent on channels where the business may write first. |
| API | Starts the procedure for one contact from your own systems, or for contacts you select on Contacts. Use it for messages about their own business with you, such as an order that shipped. |
A procedure with a Schedule chip cannot ask the customer anything, because a scheduled run has no customer; publishing says so. Once published, each Schedule chip has its own switch to pause it and Run now to start it at once. Its runs show in Runs. Pausing the procedure pauses all its schedules.
Use a procedure in a campaign
Campaigns are sent from Outbound. On a campaign's AI actions tab, tick the procedures the AI may use for replies. When a contact replies, the AI picks one by what they write, matching it against each procedure's When to trigger sentence, the same way it does in chat.
Write the instructions
| Input | What it inserts |
|---|---|
| Enter | A new instruction. |
| / | If / Else, or a Message step, which sends your exact words with no AI writing. A Message can also go inside a branch. |
| @ | A referenced Action. |
| {{ | A context value, such as customer name, email, phone, customer ID, conversation ID, or channel. |
Keep each step focused on one outcome. State the condition before the action it controls, and give each branch a clear end or next step. Use the action picker so the document refers to the configured action rather than only its name in prose.
Use actions
A procedure can reference actions that retrieve data or perform a task. Configure and test those actions first. Check their required inputs, response fields, channel support, and approval requirements before using them in a procedure.
When asking the authoring assistant to use private actions, save the procedure first so it has a saved scope to work in. Review AI edits as changes to the draft before publishing.
Preview the process
- Test the request that should start the procedure.
- Exercise both sides of every condition.
- Try missing input, unavailable actions, and a failed external operation.
- Check that the next step uses the previous action's result correctly.
- Verify customer input and approval pauses before the process continues.
Draft, Live, and Paused
| State or control | Meaning |
|---|---|
| Save | Stores the authoring draft. Published conversations keep using the existing published version. |
| Publish | Publishes and activates the current saved procedure when validation succeeds. |
| Live | The published procedure is active. |
| Paused | The deployment is disabled until resumed. |
| History | Review saved revisions and publication information from the procedure's management controls. |