Sales automation in Bitrix24 is built from short scenarios: a trigger on an event or a stage, one or two robots, a measurable result. Big "turnkey processes" break the first time the pipeline changes; short chains live for years. Below are eight working scenarios across the deal stages — taking an enquiry, the first contact, invoice and contract, payment and repeat sales. Each is assembled in the workflow designer from stock actions and Roboteka robots, with no programming.
How do I automate taking an enquiry?
Scenario 1, phone normalization. Trigger: a lead is created from a web form. The Format phone robot brings the number to a single format — +7, 8 or international — stripping spaces, brackets and dashes, and returns a recognized flag (Y/N). Result: duplicate search and telephony work with one spelling of the number, and an unrecognized phone goes to the manager as a task.
Scenario 2, linking to an existing client. Trigger: a lead or deal is created. The Find contact by phone/email robot looks up a contact by the normalized number or email and returns the ID, name and a "Found" flag (Y/N). Result: on Y the record is attached to the client's card — the enquiry history is not broken and no duplicate contact is created.
How do I automate the first contact?
Scenario 3, first-call deadline skipping weekends. Trigger: a lead is taken into work. The Date + N business days (RU) robot adds one business day to the current date by the Russian production calendar — accounting for weekends and holidays — and returns the date in YYYY-MM-DD and DD.MM.YYYY formats. A stock robot then sets a task with that deadline. Result: the first call is never scheduled for a Saturday or a holiday, and task deadlines are achievable.
Scenario 4, a number for SMS. Trigger: an enquiry confirmation is sent to the lead. The Format phone robot returns the "digits only" variant — no plus, brackets or spaces. Result: the SMS gateway and messenger integrations get the number in the form they accept without errors.
What to automate on the invoice and contract?
Scenario 5, currency rate in the invoice. Trigger: the deal moves to the Invoice stage. The Central Bank of Russia exchange rate robot fetches the official rate for today by currency code — USD, EUR, CNY and others — and returns the rate to the ruble, the rate per unit accounting for the denomination, the rate date and a "found" flag. Result: the ruble amount on the deal is calculated from a fixed official rate, not from a number off the top of the manager's head.
Scenario 6, the rate on the contract date. Trigger: the contract date is filled on the deal. The same robot accepts a date as a separate parameter and returns the rate for the given day. Result: the rate on the signing date is fixed in a deal field — if the amount is ever disputed, there is documentary grounding.
How do I control payment and repeat sales?
Scenario 7, payment deadline in business days. Trigger: the "Contract signed" stage. The Date + N business days (RU) robot adds five business days to the transition date — exactly as the contract is worded. A "check payment" task is set for the resulting date, and if needed the deadline is written into a deal field. Result: payment control does not land on a weekend and does not fire ahead of time.
Scenario 8, a repeat enquiry. Trigger: a new enquiry from the site. The Find contact by phone/email robot locates the old client's card by the number. Result: the deal is created on the existing contact — the manager sees the purchase history and talks to the client as someone familiar, not as a new lead.
How do I assemble a scenario in the designer?
The order is always the same. Open the automation rules of the right pipeline, pick the trigger stage and add a robot from the list — after Roboteka is installed, its robots appear next to the stock ones. A robot's outputs — IDs, Y/N flags, dates, rates — are available to the next steps of the template: build conditions on them and write values into deal fields with the stock modify-document action. Test the chain on one trial deal before turning it on at scale. A step-by-step walkthrough of the setup is in the guide on Bitrix24 robots, and how to spread scenarios across stages is in the article on pipelines.
Bottom line
Eight scenarios cover the deal's path from enquiry to repeat sale: a clean number on entry, linking to an existing client, achievable deadlines in business days, a fixed rate in the calculations, and payment control. Start with the two enquiry-intake scenarios — they pay off on the very first day. The full set of robots is in the CRM robot catalog. If the robot you need is missing — describe the task, we build it for free and add it to the shared library.