{"Status":true,"Message":"","Response":{"post":{"postuid":"6505c145-b06f-43f4-82d2-6e7ccd9144fb","tenantuid":"d8b744fc-2e70-4089-bb80-dd1d08f6c7b2","projectuid":"fc6490ac-7527-4f49-b06e-46f701280e85","title":"Chat Procedures","slug":"article/chat-procedures","html":"\u003Cp\u003EA procedure is a step-by-step flow your messenger\u0027s AI agent follows for requests that need more than an answer: cancelling an order, issuing a refund, starting a return or changing a booking. It asks the customer for details, looks things up in your systems, checks what it found, and makes a change only after the customer says yes.\u003C/p\u003E\u003Ch2 id=\u0022procedures_rules_and_actions\u0022\u003EProcedures, rules and actions\u003C/h2\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EFeature\u003C/th\u003E\u003Cth\u003EWhat it\u0027s for\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ca href=\u0027/article/chat-question-rules\u0027\u003EQuestion rules\u003C/a\u003E\u003C/td\u003E\u003Ctd\u003EOne response to a kind of question: hand off, reply with set text, guide the AI\u0027s answer, show a button or call an action.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ca href=\u0027/article/chat-actions\u0027\u003EActions\u003C/a\u003E\u003C/td\u003E\u003Ctd\u003EConnections to your own systems, such as looking up an order or cancelling a subscription. Actions that look something up can be used by the AI while it answers.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003EProcedures\u003C/td\u003E\u003Ctd\u003EA whole flow made of steps, using your actions in a fixed order. The only way an action that changes something can run.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003EDocent walks the steps one at a time. The AI only reads details out of what the customer wrote, picks among options you list and writes the wording. It never chooses the next step and can never make a change by itself.\u003C/p\u003E\u003Ch2 id=\u0022open_the_procedures_page\u0022\u003EOpen the Procedures page\u003C/h2\u003E\u003Col\u003E\u003Cli\u003EIn the account sidebar, click \u003Cb\u003EMessengers\u003C/b\u003E and open your messenger.\u003C/li\u003E\u003Cli\u003EIn the messenger\u0027s sidebar, click \u003Cb\u003EProcedures\u003C/b\u003E (under Actions). Owners and Admins can see it.\u003C/li\u003E\u003Cli\u003EThe page lists your procedures with when each starts, its number of steps, its runs in the last 30 days and whether it\u0027s on. Click one to open it in the designer, or click \u003Cb\u003ENew procedure\u003C/b\u003E.\u003C/li\u003E\u003C/ol\u003E\u003Cp\u003E\u003Cb\u003ENew procedure\u003C/b\u003E offers templates you can adapt: \u003Cb\u003ECancel an order\u003C/b\u003E, \u003Cb\u003EOrder status\u003C/b\u003E, \u003Cb\u003EReport an issue\u003C/b\u003E, \u003Cb\u003EStart a return\u003C/b\u003E, \u003Cb\u003EChange a delivery address\u003C/b\u003E, \u003Cb\u003ECancel a subscription\u003C/b\u003E, \u003Cb\u003ERefund within 30 days\u003C/b\u003E and \u003Cb\u003EChange a booking\u003C/b\u003E, or \u003Cb\u003EStart from scratch\u003C/b\u003E. A template\u0027s Look up and Do steps need to be pointed at your own actions before it can be switched on.\u003C/p\u003E\u003Ch2 id=\u0022using_the_designer\u0022\u003EUsing the designer\u003C/h2\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EAdd a step:\u003C/b\u003E drag a step from the palette onto a \u003Cb\u003E\u002B\u003C/b\u003E in the flow, or click a \u003Cb\u003E\u002B\u003C/b\u003E and choose one. Steps connect where you drop them, and the flow arranges itself.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EBranches:\u003C/b\u003E steps such as Confirm, Check, Look up, Do and Decide split the flow (Yes/No, Success/Failed, or one branch per option). Add steps under each branch.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EEdit a step:\u003C/b\u003E click it to open its properties in the panel on the right.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EUndo and redo:\u003C/b\u003E Ctrl\u002BZ and Ctrl\u002BY. \u003Cb\u003ECopy and paste:\u003C/b\u003E Ctrl\u002BC and Ctrl\u002BV. \u003Cb\u003EDelete\u003C/b\u003E removes the selected step.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EZoom:\u003C/b\u003E the \u002B and \u2212 buttons or Ctrl\u002Bscroll. Drag the background to move around.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EIssues:\u003C/b\u003E problems are listed in the panel and marked on the steps as you work. Red ones stop the procedure being switched on; amber ones are worth fixing.\u003C/li\u003E\u003C/ul\u003E\u003Ch2 id=\u0022step_types\u0022\u003EStep types\u003C/h2\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EStep\u003C/th\u003E\u003Cth\u003EWhat it does\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EAsk\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EAsks for details: a form on the website, questions in words on WhatsApp and email. Each answer is kept as a value, such as \u003Ccode\u003E{{order_number}}\u003C/code\u003E. Details already in the customer\u0027s messages are picked up. \u003Cb\u003EAlways show the question\u003C/b\u003E (on by default) still shows the website form, filled in, so the customer can check it. \u003Cb\u003EIf they won\u0027t say\u003C/b\u003E chooses what happens after up to 3 tries.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003ESay\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003ESends a message.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EConfirm\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EAsks a yes/no question with two buttons. \u003Cb\u003EYes\u003C/b\u003E allows one change by a Do step below it. An unclear reply is asked once more, then counts as no.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EWrite up\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EThe AI writes a short, neutral summary of the issue from the conversation, kept as \u003Ccode\u003E{{summary}}\u003C/code\u003E. Show it with a Confirm and send it with a Hand off.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003ELook up\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003ECalls an action that looks something up and keeps the result (for example as \u003Ccode\u003Eorder\u003C/code\u003E, then \u003Ccode\u003E{{order.status}}\u003C/code\u003E). Continues on \u003Cb\u003ESuccess\u003C/b\u003E or \u003Cb\u003EFailed\u003C/b\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EDo\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003ECalls an action that changes something, only after a Confirm\u0027s Yes. Continues on \u003Cb\u003ESuccess\u003C/b\u003E or \u003Cb\u003EFailed\u003C/b\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003ECheck\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003ECompares values (is, is not, contains, more than, at most, is empty\u2026) and continues on \u003Cb\u003EYes\u003C/b\u003E or \u003Cb\u003ENo\u003C/b\u003E. Numbers compare as numbers and dates as dates.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003ESet\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EWorks out a value: text with values in it, or a \u003Cb\u003ECalculate\u003C/b\u003E using \u002B \u2212 * / %, round, floor, ceil, abs, min, max, days_since and days_until.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EDecide\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EThe AI reads the conversation and picks one of your options (for example, why they want a refund). Each option is a branch, plus \u003Cb\u003ESomething else\u003C/b\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EGo to\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EJumps to another step, to join paths or loop back. A loop must include an Ask or a Confirm.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EAI answers\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EEnds the procedure and lets the AI answer the question that started it from your articles, with your guidance and everything the procedure found out.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EHand off\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EEnds the procedure and brings in your team (a chosen team, or the usual one) with a note of everything it found out. It can also email the customer a copy.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Cb\u003EEnd\u003C/b\u003E\u003C/td\u003E\u003Ctd\u003EEnds the procedure, with an optional message. With no message it finishes quietly.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003EAn empty branch has a default, shown on the canvas: a \u003Cb\u003EFailed\u003C/b\u003E call hands off, a declined Confirm says nothing was changed, and anything else ends. If a path runs out without saying anything, the AI answers the customer\u0027s message with what the procedure found out.\u003C/p\u003E\u003Cp\u003EMessages the customer reads (Say, Confirm, End, Hand off, an Ask\u0027s introduction and the emailed copy) can be formatted with bold, italics, links and lists, using the bar above the box or Markdown such as \u003Ccode\u003E**bold**\u003C/code\u003E. Click \u003Cb\u003EPreview\u003C/b\u003E to see it as the customer will. It shows formatted in the messenger and in email; WhatsApp gets its own bold and italics, with links written out.\u003C/p\u003E\u003Ch2 id=\u0022how_a_procedure_starts\u0022\u003EHow a procedure starts\u003C/h2\u003E\u003Cp\u003EClick the \u003Cb\u003EStarts when\u003C/b\u003E block at the top of the flow and choose:\u003C/p\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EWhen a message matches:\u003C/b\u003E the AI starts it when what the customer asks matches your description (for example \u0022Wants to cancel an order\u0022), judged by meaning, like a \u003Ca href=\u0027/article/chat-question-rules\u0027\u003Equestion rule\u003C/a\u003E.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EWhen a new conversation starts:\u003C/b\u003E it runs on the first message of every new conversation on the channels you tick (Web chat, Email, WhatsApp), before anything else answers. Use it to sort incoming mail: a Decide step reads what the email is about, then each option hands it to the right team, answers it or carries on. On \u003Ca href=\u0027/article/chat-email-channel\u0027\u003Eemail\u003C/a\u003E you can pick single addresses. If two procedures start on the same channel, only the first in the list runs, and the designer warns you.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EProcedures only run where the AI answers, so not on an email address whose AI replies are off.\u003C/p\u003E\u003Ch2 id=\u0022values_and_formats\u0022\u003EValues and formats\u003C/h2\u003E\u003Cp\u003EPut values in messages and step settings with double braces. The properties panel lists the values available at each step; click one to insert it.\u003C/p\u003E\u003Ctable border=\u00221\u0022 style=\u0022border-collapse: collapse; width: 100%;\u0022\u003E\u003Cthead\u003E\u003Ctr\u003E\u003Cth\u003EValue\u003C/th\u003E\u003Cth\u003EWhat it holds\u003C/th\u003E\u003C/tr\u003E\u003C/thead\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003E{{order_number}}\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EAn answer from an Ask step, named after its field.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003E{{order.status}}\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EA field in a Look up result kept as \u003Ccode\u003Eorder\u003C/code\u003E.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003E{{customer.name}}\u003C/code\u003E, \u003Ccode\u003E{{customer.email}}\u003C/code\u003E, \u003Ccode\u003E{{customer.phone}}\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EThe customer\u0027s details.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003E{{customer.user_id}}\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EThe signed-in user\u0027s ID, for \u003Ca href=\u0027/article/chat-identity-verification\u0027\u003Everified\u003C/a\u003E customers only.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003E{{attributes.plan}}\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EAn attribute your website sent when it started the messenger.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003E{{today}}\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EToday\u0027s date.\u003C/td\u003E\u003C/tr\u003E\u003Ctr\u003E\u003Ctd\u003E\u003Ccode\u003E{{question}}\u003C/code\u003E\u003C/td\u003E\u003Ctd\u003EThe customer\u0027s question that started the procedure.\u003C/td\u003E\u003C/tr\u003E\u003C/table\u003E\u003Cp\u003EAdd a format after a bar to change how a value shows in a message: \u003Ccode\u003E{{total | number}}\u003C/code\u003E \u2192 1,600, \u003Ccode\u003E{{total | money}}\u003C/code\u003E \u2192 1,600.00, \u003Ccode\u003E{{total | whole}}\u003C/code\u003E \u2192 1,600 rounded, and \u003Ccode\u003Eupper\u003C/code\u003E or \u003Ccode\u003Elower\u003C/code\u003E to change the case of text.\u003C/p\u003E\u003Ch2 id=\u0022safety_rules\u0022\u003ESafety rules\u003C/h2\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EA Do step needs a Confirm\u0027s Yes before it\u003C/b\u003E on every path that reaches it. Each Yes allows one change.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003ELook up steps use actions that look something up; Do steps use actions that change something.\u003C/b\u003E On the \u003Ca href=\u0027/article/chat-actions\u0027\u003EActions\u003C/a\u003E page, an action marked \u003Cb\u003EChanges something\u003C/b\u003E is never given to the AI to call by itself: only a procedure\u0027s Do step runs it.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EOnly in procedures:\u003C/b\u003E mark a look-up action this way when its results need details collected and checked first, such as a price quote. The AI never calls it by itself; only a Look up step runs it.\u003C/li\u003E\u003Cli\u003EA procedure that would loop forever, or reaches a step that\u0027s been deleted, hands off to your team.\u003C/li\u003E\u003C/ul\u003E\u003Ccite class=\u0022warning\u0022\u003E\u003Cspan class=\u0022title\u0022\u003ETest with care\u003C/span\u003E\u003Cp\u003ERunning a Do step\u0027s action from the Actions page calls your real system, so the change really happens. Use test values.\u003C/p\u003E\u003C/cite\u003E\u003Ch2 id=\u0022when_a_procedure_runs_and_when_it_stops\u0022\u003EWhen a procedure runs, and when it stops\u003C/h2\u003E\u003Cul\u003E\u003Cli\u003EEach procedure runs at most once in a conversation. A follow-up question is answered as usual instead of starting it again.\u003C/li\u003E\u003Cli\u003EIf the customer asks for a person at any point, the procedure stops and your team takes over, with a note of everything it found out.\u003C/li\u003E\u003Cli\u003EProcedures are for the AI only. Once someone on your team has been in a conversation (taken it over, been assigned it or replied), a procedure under way stops and none runs there again, even after the conversation is closed, handed back to the AI or reopened.\u003C/li\u003E\u003C/ul\u003E\u003Ch2 id=\u0022trying_it_out\u0022\u003ETrying it out\u003C/h2\u003E\u003Cp\u003EClick \u003Cb\u003ETry it\u003C/b\u003E in the designer to play the customer, turn by turn, saved or not. The path lights up on the canvas as it runs. Do steps always use the action\u0027s sample response, and Look up steps do too unless an admin ticks \u003Cb\u003ECall Look up actions for real\u003C/b\u003E. Nothing is sent, saved or billed. Saved procedures can also be tried on the messenger\u0027s \u003Cb\u003ETest\u003C/b\u003E page; see \u003Ca href=\u0027/article/testing-the-chat-ai\u0027\u003ETesting the chat AI\u003C/a\u003E.\u003C/p\u003E\u003Ch2 id=\u0022what_your_team_sees_in_the_inbox\u0022\u003EWhat your team sees in the inbox\u003C/h2\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003EIn the conversation:\u003C/b\u003E each run\u0027s messages sit together in a box headed \u003Cb\u003EPROCEDURE\u003C/b\u003E with its name, when it started and a bar showing the steps taken. Each step\u0027s message has its number and name above it, with the buttons it offered underneath. The last line says how it ended: \u003Cb\u003ERunning\u003C/b\u003E, \u003Cb\u003ECompleted\u003C/b\u003E, \u003Cb\u003EStopped here\u003C/b\u003E, or stopped when a teammate took over. A finished run with more than six messages folds up.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EIn the details panel:\u003C/b\u003E the \u003Cb\u003EProcedures\u003C/b\u003E card shows each run with the step it\u0027s at (\u003Cb\u003ERunning\u003C/b\u003E, \u003Cb\u003ECompleted\u003C/b\u003E or \u003Cb\u003EStopped here\u003C/b\u003E) and \u003Cb\u003EWhat it found out\u003C/b\u003E, such as the order it looked up. Click \u003Cb\u003EHide\u003C/b\u003E to fold that list away.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EView path \u2197\u003C/b\u003E (Owners and Admins) opens the procedure in the designer with the run\u0027s path lit up.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EInternal notes in the conversation also record each look-up and change. For more about the conversation view, see \u003Ca href=\u0027/article/using-the-chat-inbox\u0027\u003EUsing the chat inbox\u003C/a\u003E.\u003C/p\u003E\u003Ch2 id=\u0022measuring_procedures\u0022\u003EMeasuring procedures\u003C/h2\u003E\u003Cul\u003E\u003Cli\u003E\u003Cb\u003ETraffic\u003C/b\u003E in the designer shows the last 30 days on each step: how many runs reached it, ended there or are waiting there now.\u003C/li\u003E\u003Cli\u003E\u003Cb\u003EReports \u2192 AI agent\u003C/b\u003E has a procedures table: for each procedure, its runs, how many finished, were handed off or stopped, and the step most unfinished runs stopped at. See \u003Ca href=\u0027/article/chat-reports\u0027\u003EChat reports\u003C/a\u003E.\u003C/li\u003E\u003C/ul\u003E\u003Cp\u003EA procedure that finishes after a successful Do step counts as an AI resolution, billed only if the customer doesn\u0027t then need a person. One that ends in AI answers is billed like any answer. Hand-offs, stopped runs and test chats never count.\u003C/p\u003E","publish_status":0,"post_type":"Article","author":{},"featured_image_updating":false,"meta_description":"Learn how to create and manage step-by-step AI procedures for handling complex customer requests like cancellations, refunds, and returns in your messenger.","display_toc":true,"has_workingcopy":false,"allow_indexing":true,"total_views":0,"date_published":"2026-11-15T17:38:34.033","date_updated":"2026-11-15T17:38:34.66","date_created":"2026-11-15T14:16:15.293"}}}