AI assistant
Automations
Flows that run on an incoming message, an opportunity change or a schedule; follow-ups to customers who went quiet.
On the Automation screen (left menu, under Growth) you build flows that run by themselves when something happens: send a quick message when a customer writes, notify an advisor when an opportunity changes stage, do something every morning at a set time.
Ready-made templates
Ready-made templates above the list shows flows that fit your business, filtered by the sales model you chose in your business type. Each template says what the flow does and how to measure it. Click one and the flow builder opens with that flow; open the template step, pick your approved template under WhatsApp template, then save and activate.
- 24/7 AI replies: the AI assistant answers incoming WhatsApp messages.
- Appointment reminder: a template goes to the customer 24 hours before the appointment.
- Membership renewal: a renewal message 7 days before the membership ends (only for membership sellers).
- Win back: a message to customers who haven't written in 30 days.
- New lead follow-up: a follow-up message two days after a new opportunity is opened.
- Bulk follow-up to potential customers: every open opportunity that hasn't moved for 3 days gets the same approved WhatsApp template, once per opportunity. For a one-off bulk send today, use Campaigns.
- CRM + Meta: report qualified leads: AI classifies the incoming message, updates the contact's status in CRM and reports qualified leads to the Meta Conversions API as Lead, so ads reach similar people.
- CRM + Meta: report sales: when an opportunity is Won, a Purchase event goes to Meta.
- WhatsApp reminder for abandoned carts: customers who enter their phone at checkout but don't complete the order get an approved template with their cart link (for product sellers; needs the WooCommerce plugin).
- Shipped notification: when a tracking number is added to an order, the customer gets a template with the tracking link (same plugin).
If the person wrote from a click-to-WhatsApp ad and your WhatsApp connection carries Meta's events permission, the event goes with the ad click ID (Conversions API for business messaging) instead of the Pixel, and Meta ties it directly to that ad; the same event is sent only once per conversation. Without the permission the event goes through the Pixel and phone number as before, and the run history shows a "WhatsApp ad event not sent, used the Pixel path" line with the reason. You grant the permission in the Meta window when you disconnect and reconnect WhatsApp.
The Meta templates need a Meta Pixel and a Conversions API access token; without them the step is skipped and the run history says why. If no ad account is connected, enter them in Settings › Channels & integrations › Meta Conversions API: in Meta Events Manager, open your dataset's Settings to get the dataset ID and an access token, optionally add a Test event code, then click Save and Send test event. The token is stored encrypted; leave the field empty to keep the saved token. If an ad account is connected, the same page shows "events go automatically to the connected ad account's Pixel" and a Go to Ads link instead of the Pixel and token fields; you only enter the Test event code and click Save. Send test event works in this case too, and the event shows up in Events Manager › Test Events.
Templates tied to a sales column (message on entering a stage, remind if no reply, assign from pool, alert on idle opportunities) aren't here but behind the lightning button in the column header in Sales CRM; they open with that column selected. See Column automations.
Trigger
Every flow starts with a Trigger:
- Event: Message received, opportunity created / updated / Stage changed / tag added, score threshold crossed, contact created / updated / deleted. Time-based events: Appointment in 24 hours, Membership ends in 7 days, Customer hasn't written for 30 days, Opportunity idle in stage (checked hourly, run once per record). Store events (the WooCommerce plugin or the store events endpoint): New order received, Order shipped (the first time a tracking number or a "shipped/completed" status arrives, once per order), Cart abandoned. Old orders sent by the plugin's initial import don't start automations. For opportunity events, once you pick a Sales flow you can also pick a Stage; left empty, the flow runs for every stage. For Opportunity idle in stage, set Idle for (days); if the opportunity moves to another stage and waits again, it runs again.
- Schedule: at set times and days (e.g. every day at 09:00).
- Webhook: called from another system.
- Manual: for testing.
Events that don't fire yet (message sent, button clicked, web tracking events) are not listed; the Add step list also shows only steps you can use.
When you change the trigger, the trigger box on the canvas updates its name and second line too (e.g. Opportunity idle in stage · "No reply, 2 days"); if you gave the box your own name, it is kept. For Message received, use Only this opportunity to search by customer name and pick a single opportunity, so the flow runs only on its messages while you try it; left empty, it runs for all opportunities.
Adding steps, testing and activating
A step you pick from Add step is linked to the end of the flow: if the flow has a single Finish, it goes right before it; otherwise it is placed to the right of the last step. To link it elsewhere, delete the link and draw a new one from the dots on the edges of the boxes. The selected step's settings open in the Step settings box on the right.
Clicking Activate checks the flow. If a step isn't linked to any other step or a step's settings are incomplete (an AI agent step with no agent selected, an empty message, an Opportunity action without a stage, no quick message or template picked), the flow is not activated; the top of the editor lists what's missing in which step under Fix these before activating.
Test runs the flow once right away. For a message-triggered flow, the Run the flow now window opens; pick the conversation to try it in from Test conversation and click Test. Message steps send real messages to the person you pick, so test in a conversation with your own number. For a flow triggered by an opportunity event (opportunity created, stage changed, Opportunity idle in stage and so on), the Test with an opportunity window opens; search by customer name, pick the opportunity and click Test. The test can send real messages and change the opportunity.
The WhatsApp-not-connected warning appears only when the flow is triggered by a WhatsApp message.
Message received and channels
Message received works on WhatsApp, Messenger, Instagram, Telegram, the web chat widget and email. If no Channel is selected on the trigger it runs on every channel except email; to run on email, select E-mail explicitly (so spam that lands in the inbox gets no reply).
If the automation replied to the customer, the AI agent does not reply to the same message as well. If AI is off in the conversation, automations do not run either.
New automation opens with a starter flow triggered by WhatsApp messages. If WhatsApp isn't connected, a "WhatsApp isn't connected" warning with a Connect WhatsApp link appears above the editor; the flow won't run until the channel is connected.
Follow up with a customer who went quiet
- Add a Message received trigger.
- Add a Delay after it (e.g. 1 day).
- Add a Condition: field Customer wrote after the flow started, operator equals, value
false. - Add a Quick message on the condition's Yes branch.
The condition reads the conversation again when the delay ends; if the customer wrote in the meantime, no follow-up is sent. You can also use Last message from (customer / business) and Conversation status (open / closed).
On WhatsApp, free-form messages cannot be sent more than 24 hours after the customer's last message; for longer delays send an approved template with the Template message step.
Opportunity action step
The Opportunity action step changes the opportunity that triggered the flow. Pick it under Action:
- Move to stage / Move to another sales flow (to that sales flow's first stage).
- Assign from pool (round robin): uses the sales flow's auto-assign pool, shifts and country rules.
- Assign to a person / Assign to sales flow owner: the assignee gets a notification.
- Add tag: the tag must already exist.
- Add note, Set follow-up date (days from now).
- Notify a teammate: if nobody is picked, the opportunity owner gets an in-app notification.
On opportunity events, message steps go to the opportunity's conversation; you can use {{contact.first_name}}, {{contact.name}} and {{deal.title}}. These variables are also filled on message events, from the conversation's latest opportunity. Sent and failed messages are written to the opportunity's history. An opportunity moved by an automation doesn't run that same automation again.
Sales flow automations and your plan
In the list, each flow's Trigger column shows the event and, if set, the sales flow / stage name; filter with All, Sales flow automation and Other flows above the list. This screen opens even if your plan doesn't include automations: you see your sales flow automations and can turn them on or off; instead of new flows and templates you see an upgrade box.
A flow that starts with an opportunity event and only uses message, template, wait, condition, opportunity action or notification steps counts as a Sales flow automation; the flow builder shows this badge next to the title. Sales flow automations are available on every plan, don't count toward your plan quota and use no credits. Add AI, HTTP, a subflow, an A/B split or a loop and it becomes a regular automation: it counts toward your plan's automation quota and uses credits per step.
System automations
Jobs you set up on other screens that run on their own show up in Automations with a System badge; there's nothing extra to do — saving the setting creates and updates the automation:
| Automation | Set up in | On/off here |
|---|---|---|
| AI auto-reply: assistant | Assistant page › Auto-reply on these channels, the channel AI bar in Messages, the website chat bubble | Yes; channels can be picked here too |
| Auto-assign: sales flow | Settings › Sales & CRM › Sales CRM › Auto-assign | Yes |
| AI moves opportunities: sales flow | Stage settings › AI | No (from the stage settings) |
| Today's appointments: sales flow | Stage type "Today's appointments" | No |
| Group send, Scheduled campaign, Scheduled email | Campaigns | Yes for group sends; others from the campaign screen |
| Pause AI on phone reply | Messages › Inbox settings | Yes |
A system automation's flow is read-only; Open settings takes you back to the screen it came from. That screen's setting does the work and the automation is its view: it doesn't count toward your plan quota and uses no extra credits. Remove the setting (for example take the assistant off its channels, or a campaign finishes) and the automation leaves the list too. To customise it, build a new flow that does the same job and turn the system automation off; if both stay on, two replies may go out.
Variables in the message step
You can put the opportunity's details into the text of a Send a WhatsApp message step. Pick them from Insert variable under the message box; the variable is written where your cursor is (at the end if you never clicked into the box), with a space so it does not stick to the next word:
- Opportunity details:
{{ad}}(first name;{{isim}}works too),{{ad_soyad}}(full name),{{telefon}}(phone),{{eposta}}(email),{{randevu_tarihi}}(appointment date, e.g. "Thursday 30 October"),{{randevu_saati}}(appointment time, e.g. "15:30"). If the opportunity has no name (like an opportunity that came from Instagram), the channel profile name is used. For an appointment event such as 24 hours before an appointment it is that appointment; for other events, the opportunity's upcoming appointment. - Additional info: each of the opportunity's additional info fields by its own key (e.g.
{{gorusme_notu}}). - Message:
{{inbound_text}}(incoming message),{{ai_reply}}(AI reply).
The same variables are resolved in the Quick message and Notify the advisor steps; in a quick message {{temsilci}} is the conversation's assignee and {{isletme}} is the workspace name.
Example: "Hi {{ad}}, a reminder of your appointment tomorrow at {{randevu_saati}}." If the opportunity has no value, it is left blank and an "Empty variable" warning is written to the run history. Despite its name, this step sends a free-form message on the conversation's channel: it works on Instagram and Messenger, and on WhatsApp only within 24 hours of the customer's last message. For WhatsApp reminders sent later, use the Template message step.
Template message step
The Template message step sends an approved template to the customer, including customers outside the 24-hour window. Pick the template under WhatsApp template and choose where each variable comes from (name, first name, appointment date/time or fixed text; for store events also Order number, Order total, Tracking link, Cart link). If a store variable has no value in the event (e.g. no tracking link yet), the template isn't sent and the run history shows why. Template variables can be named ({{ad}}, {{randevu_saati}}) or, in older templates synced from Meta, numbered ({{1}}); for named variables the first choice comes from the variable name (isim → name, saat → appointment time), and you can change it. The number comes from the trigger (incoming message, opportunity or contact). Nothing is sent to people who opted out (wrote STOP) or whose variable value can't be found; the run history shows why.
Run history
Every run is logged step by step: what each node did and, on error, where. If a flow fails several times in a row, its owner is notified.