↑↓ selectEnter openEsc close

    1. Elbuz
    2. AI in CRM

    Create a flow in plain words: how to describe a rule to the AI consultant

    8 min readUpdated

    The AI consultant turns a plain-words rule like “if a deal is stuck for 5 days, remind the manager” into a CRM flow. No builder needed: read the explanation, confirm with one button.

    When you need this:

    • Managers forget deals and quotes — the flow finds them daily and proposes a follow-up to the owner in “Pulse”.
    • You need your own rule — you see the explanation before saving.
    • A threshold needs changing — write “make it 5 days instead of 3”; the old version stays in history.
    • Tickets need routing — a ticket-event flow sets priority, assignee or tag.

    Where to start: send a ready-made phrase to the consultant.

    What a flow created in words can do

    How to create a flow in words

    1. You write the rule in the consultant chat.
    2. The generator builds a diagram from the builder blocks; an automatic check and a second AI “critic” compare it with your task — up to three rounds of fixes. This can take up to a couple of minutes.
    3. Every “AI agent” block is forced to “Changes require approval”: an email to a customer from such a flow arrives in “Pulse” and waits for a person until “Management” turns on “Act on its own” for this type in “Trust”.
    4. If a similar flow already exists, the consultant may skip creating a duplicate and offer to turn on or change the existing one.
    5. The consultant explains in its own words what the flow will do and opens the “Confirm action” window with the “Create the process “…”” button (for an edit — “Change the process “…””).
    6. “Create the process “…”” saves the flow and turns it on right away — it appears on the “Automations” tab. “Cancel” saves nothing.
    AI consultant chat with the “Confirm action” dialog for creating a process
    1What will be created
    2Create the process
    3Cancel
    1. The dialog names the process that will be created.
    2. Confirming creates and turns on the process.
    3. Cancel leaves everything as it was.

    After saving, the consultant writes “The process “…” is created and switched on — see it in the process builder and on the Automations tab of the Pulse window.”.

    The draft is kept on the server for 24 hours; the button carries only its number, so nobody can swap the diagram between showing and saving. Later you get “The process draft has expired — describe the task again.”.

    If you click “Cancel”, the chat shows “Cancelled. Confirm again with the button below, or describe the change in words.” and the “Create the process “…”” button, so you don't have to describe the task again.

    Bottom of the chat after cancelling: the “Cancelled” line and a retry button
    1Cancelled line
    2Retry button
    1. A line says the action was cancelled.
    2. The same button lets you confirm again.

    How much it costs

    • The consultant's reply (a regular one is about $0.05) and building the diagram (generator and check, up to three rounds) are billed as automation.
    • Saving with the button does not call the AI.
    • The flow itself costs money if it has an “AI agent” block or paid actions such as product enrichment.

    What a flow is made of and what it lacks

    The generator sees the full set of builder blocks, and the flow is made only of them:

    • When to start: “Manual trigger”, “Schedule” (for example, daily at 9:00, every Monday), “On event” — a rule from the trigger list, “AI analyzed an email or call” (gives the intent, tone, complaint flag, summary, customer and owner) or “Ticket: event” (below).
    • Find records: deals, follow-ups, customers and contacts, documents and orders, document lines, products — by conditions on fields; up to 200 records.
    • Propose in Pulse: create a deal, plan a follow-up, move the deal stage, reschedule a follow-up, assign an owner, create a task, close the order — limited to “At most one per record” per day, hour, week, month, once or per event.
    • AI agent: writes an email to the customer, picks related products, writes a summary or a translation — the email goes out only after confirmation in “Pulse”.
    • Data actions: price list import, base catalog update, export and export of all templates, exchange rates, product enrichment (), a document “based on” another, document status changes, notifications.
    • Calling the customer: the generator builds “call the customer and confirm the order” with the “AI call” block — the voice AI employee makes the call if outbound calls are set up for it (AI employee on the phone).
    • Tickets: the “Ticket: update” block — status, priority, assignee, department, tags, internal note. It sends nothing to the customer (below).
    • Logic: “Condition (If)”, “End”, “Note”.

    Blocks that refer to fields of the found records run for each record separately — the run log shows this as a step per record. A diagram has at most 25 blocks, at most 8 of the same kind, and exactly one trigger.

    What is missing — and what the consultant replies

    There are no blocks for SMS, messenger messages, payments or external services. For such a task the consultant builds the closest substitute from the available blocks — most often a follow-up for the manager via “Pulse” — and says plainly what the flow does not do. Whether to create the substitute is up to you and the button.

    Consultant explains that a process cannot send SMS and suggests an automatic rule instead
    1What a process cannot do
    1. The consultant says plainly that a process cannot send SMS and offers an automatic rule.

    In the screenshot: to “every day at 10:00 send an SMS reminding about payment” the consultant replied that the flow does not set up SMS sending; instead it will find unpaid orders every day and propose a reminder follow-up to the manager.

    • Elbuz does have SMS, but in document “Automatic rules” (the “Send SMS” command), not in flows. So the consultant may also talk you out of the substitute and recommend an automatic rule instead — that is a correct answer too.
    • An email to the customer can only be proposed by a flow through the “AI agent” block: “Propose in Pulse” has no separate “send an email” type.

    How to word a rule

    A rule works well when it names when, whom to look for, what to propose and to whom. The generator always reads the imperative (“every day…”, “do…”, “if… — remind”) as a task. A sentence with a question mark may be taken as a question and answered with advice instead of a flow.

    What to writeWhat you get
    “If a deal has had no activity for 5 days and nothing is planned for the customer, propose that the owner contact the customer (a follow-up for tomorrow).”a daily flow: deal search → “Plan a touch”
    “If a customer hasn't replied to a quote for 3 days, remind the manager, and a week later propose a reminder email.”a follow-up for the manager, then an email via the “AI agent” with confirmation
    “Every Monday check dormant customers and propose that the manager call them.”a weekly customer search → follow-up
    “When the AI has analyzed an email with a complaint, create a task for the head of department.”an “On event” flow — similar to the ready-made “Complaint → manager”
    Poor wordingWhyBetter
    “Can you set up reminders for deals?”with a question mark the generator may answer with advice rather than a flow“If a deal is stuck for 7 days, remind the owner”
    “Keep an eye on customers”it doesn't say whom to look for or what to do“Every day find customers with no follow-up for 30 days and propose a follow-up to the owner”
    “Send an SMS when an order is shipped”there is no SMS block — you only get a substitute with a follow-up for the managerSMS on a status event — the “Send SMS” command in document “Automatic rules”
    “Change the deal stage yourself if the customer has paid”flows propose, they don't change things on their own“…propose moving the deal stage”; autonomy is turned on in “Trust” in “Pulse”
    Before “Create the process “…””, read the consultant's explanation: it says when the flow will run, whom it will look for, what it will propose to whom, and what could not be done. If you see “request passed to the developers”, the flow does less than you asked for.

    Ready-made phrases: deals and orders

    Below are phrases we sent to the generator ourselves on 14.10.2026 and what it built. The diagram is similar in all of them: trigger (“Schedule” or “On event”) → “Find records” → for each record found, “Propose in Pulse” or “AI agent” → “End”.

    The generator makes up the flow name itself; you can change it in the builder. Replace the numbers and times in the phrase with your own.

    1. Stuck deal (all formats with deals)

    Write: “If a deal has had no activity for 7 days and nothing is planned, every day at 9:00 propose that the owner plan a call to the customer for tomorrow”.

    It builds: “Schedule” daily at 9:00 → “Find records”: open deals with no activity for 7+ days and no planned follow-up → “Propose in Pulse”: “Plan a touch” for the owner for tomorrow.

    Important: if such a flow already exists — every account has the ready-made “Stalled deal” — the consultant may skip the duplicate and offer to change the existing one. Then edit the number on the flow card.

    2. Quote with no reply (wholesale, services)

    Write: “If a customer hasn't replied to a quote for 3 days, remind the owner to call”.

    It builds: daily at 9:00 → “Find records”: customers who haven't replied to a quote for 3 days or more → “Plan a touch” for the owner for tomorrow.

    To adjust: “make it 5 days instead of 3”.

    3. Order stuck in a status (online store)

    Write: “If a customer order has been in the “Confirmation” status for more than 2 days, every day at 10:00 propose a follow-up to the owner: confirm the order with the customer”.

    It builds: daily at 10:00 → “Find records”: open customer orders in the “Confirmation” status for more than 2 days → “Plan a touch” for the person responsible for the order.

    Important: write the status name exactly as in your status list — the generator searches by it.

    4. Overdue payment (online store, wholesale)

    Write: “If a customer order is unpaid 3 days after creation, every day at 11:00 propose a follow-up to the owner: “remind the customer about payment””.

    It builds: daily at 11:00 → “Find records”: unpaid open documents 3+ days old → “Plan a touch” for tomorrow, 11:00. The proposal repeats every day until the order is paid.

    Important: in our test the generator didn't find the “customer order” type code and added no type filter, so other unpaid documents may end up in the results. Check the explanation before “Create the process “…”” and, if needed, add in words: “customer orders only”.

    5. Order not picked up (pickup point)

    Write: “Every day check orders in the “Reserved” status for more than 3 days and propose a follow-up: remind the customer to pick up the order”.

    It builds: daily → “Find records”: open orders in the “Reserved” status for more than 3 days → “Plan a touch” for tomorrow with the order number in the note. The ready-made “Order not picked up” flow does the same — the “Store with a pickup point” format turns it on.

    6. Service renewal (services)

    Write: “Find customers whose next payment is expected in a week or sooner and who have no planned follow-up, and every day at 9:00 propose a reminder about renewing the service”.

    What you get: this flow already exists as a ready-made one — “Service renewal”. In our test the consultant didn't create a duplicate and offered to turn on the existing one. The “Services” format turns it on by itself.

    Ready-made phrases: customers, emails, catalog

    7. New chat customer with no follow-up (all)

    Write: “If a new customer from the chat hasn't had a single follow-up within a day, propose that the owner write to them”.

    It builds: daily at 10:00 → “Find records”: customers from the website chat created more than a day ago, with no follow-up and no pending proposals → “Plan a touch” for the owner. The flow skips customers without an owner — the ready-made “Lead without an owner” picks them up.

    8. Complaint in an email or call (all)

    Write: “When the AI has analyzed an email or call and it's a complaint, create a task for the head of sales”.

    It builds: “On event” “AI analyzed an email or call” → “Condition (If)”: complaint → “Create a task”.

    What won't work: in our test the generator couldn't assign the task specifically to the head of department or set a high priority. The ready-made “Complaint → manager” flow already does this — better keep it.

    9. Dormant VIP customers (stores, wholesale)

    Write: “Every Monday at 10:00 find VIP customers who haven't bought for over 60 days and propose a personal email to each in “Pulse””.

    It builds: every Monday at 10:00 → “Find records”: VIP customers with an email address and no documents for 60 days → an “AI agent” that writes the email.

    Important: when we wrote “send only after my confirmation”, the generator built an agent that only drafts the text and puts it nowhere. Write explicitly “propose the email in “Pulse”” and check in the explanation that the email will arrive in “Pulse”. More reliable: the ready-made “Win back dormant customers”, whose thresholds are numbers on the card.

    10. Wholesale inquiry in an email (wholesale)

    Write: “When the AI has analyzed an email and it's a wholesale inquiry, propose creating a deal”.

    It builds: “On event” “AI analyzed an email or call” → an “AI agent” checks whether it's a wholesale inquiry → “Condition (If)” → “Create a deal”. Such a flow is paid: the agent is called for every analyzed email. “Pulse” does the same without a flow if “Track deals” is on (Replies to customers).

    11. Zero stock (catalog)

    Write: “Every day at 8:00 find active products with zero stock and create a task for the catalog manager to check the supplier”.

    It builds: daily at 8:00 → “Find records”: active products with stock 0 → “Notification” with the name and SKU.

    What won't work: a task from “Pulse” is linked to a customer, deal or document, not to a product, so the generator replaced it with a notification. Who receives it is set in the “Notification” block.

    12. Viber message to the customer after payment — substitute only

    Write: “When a customer has paid for an order, send them a thank-you message on Viber”.

    It builds: daily at 9:00 → “Find records”: paid customer orders → “Plan a touch” for the manager: “thank the customer for the payment”.

    What won't work: there is no Viber block and no trigger for the moment of payment — the consultant says so: “a follow-up for the manager is only a substitute, not a message to the customer”. The manager sends the thank-you; a reaction to a document status change is set up in Trigger rules.

    How to run a flow on ticket events

    The “On event” block with the source “Ticket: event (created, status, assignee, customer reply, SLA breached…)” runs the flow on every ticket event. What happened is in the ticket_event field; next to it is the ticket's state at that moment. Field values are codes, not window labels, and these codes are what you write in “Condition (If)”.

    Ticket events in the ticket_event field
    ticket_eventWhenWhat is in old_value
    createda ticket appeared: from an email, chat, callempty
    status, priority, assignee, department, tagsa person, routing, another flow or a customer reply changed this fieldthe previous value
    customer_replythe customer wrote in an open ticketthe status before their message: if it was “Waiting for customer” or “Solved”, the ticket becomes “Open” by itself, and a status event follows
    csatthe customer rated the replygood or bad
    sla_breacha response or resolution deadline passed, once per deadlinefirst — first response, next — next response, resolve — resolution
    Other event fields
    FieldValues
    statusnew, open, pending — “Waiting for customer”, on_hold — “On hold”, solved, closed
    prioritylow, normal, high, urgent
    channelemail, web — website chat, telegram, viber, whatsapp, facebook, instagram, phone — call
    department_id9 — Sales, 10 — Customer service
    segmentthe customer's segment by orders from their card: new, repeat, regular, vip, sleeping (dormant), lost; empty for a ticket without a customer or a customer without orders
    othersticket_id, assignee_user_id, tags, subject, intent, contractor_id

    The “Ticket: update” block changes only what is filled in:

    • “Status”, “Priority”, “Assignee” (from the employee list), “Department” (), “Add tags” (comma-separated, added to existing ones), “Internal note” (the customer doesn't see it; {{step:…}} placeholders work);
    • “Ticket” is the ticket_id from the “On event” step; an empty field means the ticket whose event started the flow;
    • the block sends nothing to the customer, even when it sets “Solved”;
    • the flow writes changes and the note to the feed on behalf of “System”, so an @-mention in the note reaches everyone mentioned; the new assignee gets both the ticket chat and the “Ticket #N is assigned to you” notification.
    Properties panel of the “Ticket: update” block with all its fields
    1Ticket
    2Status
    3Assignee
    4Internal note
    1. Empty — the ticket that started the process.
    2. An empty field is left unchanged.
    3. The ticket assignee also becomes the chat assignee.
    4. The customer does not see the note — the block sends nothing to the customer.
    Always narrow the event in “Condition (If)” (ticket_event = …), otherwise the flow fires on every ticket change, including changes made by other flows. A change made by the flow itself is also an event, but the same flow won't run on it: while it is running, a new event skips it rather than queuing — and so does an event of another ticket that arrives at that moment.

    The generator knows both blocks and the ticket events from the table above, including csat: name the event in words (“when the customer gave a “Bad” rating”) and check the built diagram in the builder before saving. Ready-made diagrams are in the scenarios.

    How to change a flow in words

    Write the change in words: “make it 5 days instead of 3”, “add a condition: only deals over UAH 10,000”. The consultant finds the flow by name or by the window you are writing from, and the generator rebuilds the diagram with the rule “keep all blocks, change only what was named”.

    • The button is then “Change the process “…””, and after saving — “The process “…” is changed. The previous version is kept in the builder version history.”.
    • The flow description and its on/off state don't change.
    • Ready-made templates from the gallery can't be changed in words — only your own flows.
    In the ready-made “Pulse” flows, the number of days is a parameter on the flow card. An edit in words may write the number straight into the diagram, and then the field on the card no longer affects the flow. To change only the number, edit it on the card on the “Automations” tab — details in CRM automations.

    Scenarios

    Quote with no reply

    Before: a manager sent a quote and forgot to follow up.

    What to write: “If a customer hasn't replied to a quote for 3 days, remind the manager”.

    After: every day the flow finds such deals and puts a follow-up for the owner in “Pulse” (phrase 2).

    Payment reminder by SMS

    Before: you want an SMS reminder every day at 10:00.

    What you get: the consultant offers a substitute with a follow-up for the manager or recommends “Send SMS” in document “Automatic rules” (what is missing).

    Threshold too high

    Before: your flow reminds after a week, but you need 3 days.

    What to write: “make it 3 days instead of 7” in the same conversation.

    After: the diagram is rebuilt; the previous version is in the builder version history.

    Tickets: quality check, calls, dormant customers

    Diagrams for flows on ticket events (n1 is the ID of the “On event” block in your diagram).

    TaskCondition (If)“Ticket: update”What you get
    Solved — send to quality checkticket_event = status and status = solved“Add tags” — quality-check, “Internal note” — “Check the reply: {{step:n1.subject}}”the supervisor picks solved tickets with a tag filter; the customer notices nothing
    Call — high priority and a person right awayticket_event = created and channel = phone“Priority” — “High”, “Assignee” — the employee who calls backa ticket from a call doesn't wait for routing and gets a shorter deadline if deadlines depend on priority (ticket settings)
    A dormant customer wrote — to the win-back managerticket_event = created and segment = sleeping“Assignee” — the manager, “Add tags” — win-back, note “The customer hasn't bought for a long time — offer terms”the customer reaches not the on-duty operator but someone who can win them back

    The consultant may not add the segment condition by itself — then enter it in “Condition (If)” in the builder. VIP customers don't need a separate flow: a checkbox in the ticket settings gives them “High” priority (VIP customers).

    What to do when a flow is not created

    Common problems
    What you seeWhyWhat to do
    “The process draft has expired — describe the task again.” More than 24 hours have passed, or the draft has already been used Send the task again (how to create a flow)
    The consultant says only “Management” creates flows from text Your role doesn't have the “Management” right Ask your manager (who has access)
    The explanation says “there is no … block”, “instead …” There is no block for the task (SMS, messenger, payment) — the consultant built a substitute Decide whether the substitute fits, or set up what you need with another tool (what is missing)
    The consultant replied with advice and offered no flow The generator took a sentence with a question mark as a question Use the imperative: “if… — remind…” (wording)

    FAQ

    Does a flow created in words work right away?

    Yes. After “Create the process “…”” it is saved, turned on and visible on the “Automations” tab in “Pulse” and in “Flows”.

    Will such a flow send emails to customers on its own?

    No. An email from the “AI agent” block arrives in “Pulse” and waits for a person until “Management” turns on “Act on its own” for this type in “Trust”.

    How do I turn off or delete a flow I created?

    To turn it off, use the “On” switch on the “Automations” tab. To delete it, use the “Flows” window.

    Can a flow close tickets or change the assignee on its own?

    Yes, with the “Ticket: update” block after “On event” with the “Ticket: event” source. It sends nothing to the customer, even when it sets “Solved” (flows on ticket events).

    Can I change the ready-made “Stalled deal” flow in words?

    You can, but it's better to change the number of days on the flow card: an edit in words may write it straight into the diagram, and the field on the card stops working.

    Where it is and who has access

    Where to write
    AI consultant — the round robot button in the lower right corner of the desktop
    Result
    Directories → Contacts → Pulse → the “Automations” tab; the diagram — Directories → Flows
    Access right
    only “Management” can create and change flows in words
    Prepare
    a rule in one or two sentences: when, whom to look for, what to propose and to whom

    To other roles the consultant replies that only “Management” can create and change flows from text. The “Create a process in words” hint on the consultant's start screen is also shown only to “Management”. A diagram with the “Find records” or “Propose in Pulse” blocks built manually in the builder can likewise be saved only by “Management”.

    Related topics

    Was this article helpful?

    Missing a feature? Tell us.

    We will add it for free if other users need it too.

    If only you need it, we will agree on it separately.

    Article contents

    Suggest an improvement

    Try Elbuz free