A robot in WazzaBee CRM is a rule: “when this happens, do that”. For example, a deal enters the “New lead” stage and the robot gives the manager a task to call. Or a deal has been sitting in “Thinking it over” for three days and the robot messages the client on WhatsApp.
Robots are run by the server. They work even if nobody has the CRM open at that moment. This article explains what a robot consists of, which events and actions exist, how to create, copy, move and turn off a robot, and where to see what it did.
Where to find robots
- Open the “Robots” section in the menu on the left.
- You will see a board similar to the deals board. The first column is “When a request comes in”: it holds robots for events that happen before a deal exists (a new message, a missed call). Next come the stages of your pipeline, from “New lead” to “Paid”. Under each stage name it says “For every deal in this stage”.
- If you have several pipelines, pick the one you need with the switcher next to the heading. The “When a request comes in” column exists only in the main pipeline: deals from incoming messages are created there.
- In the top right corner there is a line “N of M active · runs this week: K”. It shows how many robots are on and how many times they ran over the last 7 days.
On a phone the columns scroll sideways one at a time.
What a robot consists of
Every robot has three parts: an event (“When”), a delay (for some events) and an action (“What to do”). On the card the robot reads as one phrase, for example “Task “Send the price list”” and below it “As soon as the deal enters the stage”.
Events
| Event | Where it is available | When it fires |
|---|---|---|
| “Deal entered the stage” | Stage columns | As soon as the deal is in the stage: it was dragged on the board, moved in the card, moved by another robot, or a new deal was created right in this stage. |
| “Deal is stuck in the stage” | Stage columns | When the deal stays in the stage longer than the set time. If the deal was moved to another stage during that time, the robot does not fire. |
| “Client got no reply” | Stage columns | The client wrote and nobody replied within the set time, neither a manager nor a bee. The time counts from the client’s first unanswered message. If someone replied earlier, the robot does not fire. It fires only while the deal is in this stage. |
| “A new client wrote” | “When a request comes in” | When an incoming message opened a new deal: a new client wrote, or a client who has no open deal right now. |
| “Missed call” | “When a request comes in” | When an incoming call was not answered. If the same number fails to get through again within 30 minutes, the same robot does not start a second time. |
Delay
For “Deal is stuck in the stage” and “Client got no reply” a delay is required: under the event you get the “After” field with a number and a unit, “min”, “h” or “d”. Without it the robot cannot be saved and the CRM reminds you: “Set how long to wait before running”. The other events fire immediately.
The server checks robot jobs once a minute, so an action can run up to a minute late.
Actions
| Action | Where it is available | What it does |
|---|---|---|
| “Set a task” | All columns | Creates a task for the deal. Due: end of the current day; assignee: the deal’s assignee. In the “Tasks” section such a task is marked “Set by a robot”. |
| “Message the client” | All columns | Sends the client a message from the chosen line: a WhatsApp template or custom text. Details in the article The “Message the client” robot. |
| “Notify the team” | All columns | Posts to the chosen channel of the team chat (“Chats” → “Team”). The message is signed “Robot” and contains the client’s name and the stage. Only a channel can be chosen, not a direct chat. |
| “Change assignee” | Stage columns | Hands the deal to the chosen employee. On the card the robot looks like “Hand the deal to employee name”. |
| “Move to stage” | Stage columns | Moves the deal to another stage of the same pipeline. The stage where the robot itself sits cannot be chosen. |
| “Create a deal” | “When a request comes in” | Opens a deal in the first stage of the main pipeline when a new client writes. If you turn it off, incoming messages stop creating deals: the conversation stays only in “Chats”. In meal-plan delivery, a client who is currently on a plan (the deal is in “Paid” and the course is still running or starts later) does not get a new deal: their messages simply arrive in the chat. Once the course ends, the next message creates a deal again, as a renewal. The same robot decides whether a call from a new number creates a deal. |
| “Send the sale to Meta” | “Paid” only | When the deal of a client who came from a Meta ad is paid, the sale is sent to Meta. Setup is described in Ready-made niche robots and example scenarios. |
The task list for “Set a task”: “Call the new lead”, “Call the client back”, “Send the price list”, “Check the client's decision”, “Arrange a meeting”, “Prepare the contract”, “Remind about payment”, “Send the invoice” and “Confirm the booking”. The last one exists only in business types that book clients with specialists. Ready-made niche robots may use their own tasks too, for example “Send the estimate” in a car service.
How to create a robot
- Open “Robots” and, if there are several pipelines, choose the one you need.
- At the bottom of the stage column press “Add a robot”. The “New robot” window opens; under the heading you can see which stage it is being created for.
- In the “When” block choose the event.
- If you chose “Deal is stuck in the stage” or “Client got no reply”, set the delay in the “After” field.
- In the “What to do” block press the action you need and choose the details: a task (“Which task”), an employee (“Hand over to”), a stage (“Which stage”), a team channel (“Which channel”) or a line and a message for “Message the client”.
- In the “Do not repeat to the client” field enter a number of days (see below).
- Check the “On the card it will read” block: it shows the robot in one phrase, the way it will look on the board.
- Press “Save”. The notification “Robot added” appears and the new robot is on right away.
The “Save” button stays inactive until everything required is filled in: the delay, the action detail, the line and all template variables.
The “Do not repeat to the client” field
This field protects the client from identical messages in a row. If the robot already ran for this client, it stays silent for the next N days. Runs of the same robot for the same client are counted (by the client card or by the phone number).
- A new robot has 1 day.
- 0 means “The robot runs every time, even if it already ran for this client”.
- The “Create a deal” and “Send the sale to Meta” robots do not have this field.
How to manage robots
Turn on and off
At the bottom of the robot card there is a switch. A robot that is off turns grey and does not fire. Runs that already happened this week stay in the counter.
Edit
Press the robot card. The “Robot” window opens with the same fields as when creating. Make changes and press “Save”; you will see “Robot saved”.
Delete
- Open the robot and press “Delete” at the bottom of the window.
- Confirm in the “Delete robot?” window.
- “Robot deleted” appears. While the notification is on screen you can bring the robot back with “Undo”.
Copy
In the top right corner of the card there is a “Copy” button (on a computer it appears when you hover). The copy is placed right under the original and arrives turned off, so the client does not get two identical messages. The CRM shows “Copy created”. Adjust the copy, for example its text or delay, and turn it on with the switch. The “Create a deal” and “Send the sale to Meta” robots cannot be copied: each exists in a single instance.
Move to another stage
Drag the robot card to another column: with the mouse, or with a long press on a phone. Columns that will not accept the robot fade while you drag. Robots cannot be moved between “When a request comes in” and the stages: the events there are different. The “Send the sale to Meta” robot lives only in “Paid”. After the move you will see “Robot moved to “…”” with an “Undo” button.
What the labels on the card mean
| Label | What it means | What to do |
|---|---|---|
| “this week: N” | The robot ran N times over the last 7 days. | Nothing, the robot is working. |
| “did not run this week” | The robot is on, but there were no matching events. | Check that deals actually reach this stage. |
| “off” | The robot is turned off with the switch. | Turn it on if you need it. |
| “Setup needed” and “Choose a line” | The “Message the client” robot has no line and no message. | Press “Choose a line” and set up the message. |
| “Setup needed” and “Choose channel” | The team channel the robot posted to was deleted. | Press “Choose channel” and pick another channel. |
| “Setup needed” and “Pick a stage” | After the pipeline was edited, the stage the robot moved deals to became its own stage. | Press “Pick a stage” and choose another one. |
| “Setup needed” and “Connect” | No Meta dataset is connected for “Send the sale to Meta”. | Press “Connect”; “Settings → Channels and Meta” opens. |
A robot with “Setup needed” does not fire. Once you set it up, it turns back on if it was on before.
When a robot will not fire
Before every action the server checks the conditions again. The robot stays silent if:
- it was turned off or deleted before its time came;
- the deal was deleted or marked as lost;
- the deal left the stage before the robot’s time came (for stage events);
- the “Do not repeat to the client” limit applied;
- the “Change assignee” robot names an employee who is not in your account’s team, for example a sample employee from the business type set. The CRM turns such a robot off and clears the “Hand over to” field: choose your own employee and turn the robot on again;
- the CRM is in view-only mode because the subscription is not paid;
- the deals came through a transfer from Bitrix24 or another import: such deals do not start robots, otherwise thousands of old clients would get messages at once;
- one deal collected 20 runs within an hour. This is how the CRM stops robots that bounce a deal in a loop, for example from “Thinking it over” to “Meeting” and back.
Such cancellations are not written to the deal history.
Where to see what a robot did
- Deal history. The deal feed has entries signed “Robot”: “The robot created the task “…””, “The robot messaged the client”, “The robot notified the team”, “The robot changed the owner: …”. If something failed, the reason is there too, for example “The robot could not message the client: the client has not written to this line yet” or “The robot did not change the owner: there is no “…” in the team”.
- “Event log”. In the “Administration” menu group open “Event log” and choose the “Robots” filter. It collects robot actions for all deals and changes to robots (“Robots of the “…” stage changed”). The log is visible to those who have access to settings.
- “Tasks”. Tasks from robots are marked “Set by a robot”.
- Team chat. Robot messages in a channel are signed “Robot”.
Robots and pipeline changes
- Changing the business type. The sample robots of the business type are replaced with the set of the new type; your own robots stay and move across stages together with the deals. A sample robot that you edited or moved counts as your own.
- Deleting a stage that has robots. In “Settings → Pipeline” the CRM asks what to do with the robots: “Move the robots together with the deals”, “Move the robots to another stage” or “Delete this stage’s robots”.
- Deleting a pipeline. The robots of that pipeline are deleted with it; the CRM warns you about it.
- Deleting a team channel. Robots that posted to this channel get “Setup needed” and wait until another channel is chosen.
Specialist booking robots
In niches with Bookings the robots board has a «Specialist booking» column. Its robots fire by the booking time, not by the deal stage: «Before the visit» writes to the client the chosen time before the visit, «After the visit» writes to clients whose booking is marked «Visited». Actions: «Message the client» and «Notify the team». Moving a booking moves the message, cancelling removes it.
Niches with bookings get three ready robots, all turned off until you choose a line and a template: a reminder a day before the visit, a thank-you and review request 2 hours after the visit, an invitation to come back after 28 days. Details in «Booking statuses, confirmation and rescheduling».
Birthday greetings
For business types whose client card has a «Birthday» field (salon, clinic, dentistry), the robots board has a «Client dates» column. The «Client's birthday» robot greets every client with a filled-in date on its own: on the day itself or 1–30 days before, at the chosen time in the company time zone. By default at 10:00.
- One greeting per client per year.
- People born on 29 February are greeted on the 28th in non-leap years.
- If the robot is turned on after the chosen time, it skips today's birthdays and starts the next day.
- If the birth date is changed or removed, the robot takes it into account.
- No message is sent to a client without a phone number.
Actions: «Message the customer», «Notify the team» and the task «Wish a happy birthday».
FAQ
Does the CRM have to be open for robots to work?
No. Tasks, messages to clients, messages to the team, changing the assignee and moving to a stage are done by the server when the event happens.
Why can’t I set a delay for “Deal entered the stage”?
This event fires immediately. If you need the action later, choose “Deal is stuck in the stage” with a delay: the robot cancels itself if the deal is moved on during that time.
Can one stage have several robots?
Yes. In the column, robots that fire immediately come first, then robots with a delay in increasing order.
Do robots work during the trial period?
Yes, both during the trial period and with a paid subscription. In view-only mode, when the subscription is not paid, robots do not fire.
A robot gave a task to the wrong employee. Why?
A robot task always goes to the deal’s assignee. Change the assignee in the deal, or add a “Change assignee” robot before the task robot.
