Sales
Lead capture and distribution, follow-up reminders, automatic tasks on stage change, quotes from templates, mandatory loss reasons.
Business process automation
Business process automation: what a Moldovan company can automate, and what it looks like in practice
Process automation isn't about robots, and it isn't “digital transformation” either. It means a lead reaches the right employee on its own, a client who hasn't replied gets a reminder without anyone having to remember, the manager is notified when something important changes, and the Monday report builds itself. Bsmart sets up exactly these automations — in your existing CRM or in a new one.
Automations built in custom CRMs and in Bitrix24, for companies in Chișinău and across Moldova.
What is business process automation?
Business process automation means the repetitive steps in a company — capturing a request, assigning it, reminding the client, notifying the manager, updating a report, filing a document — run on their own, following rules defined once, instead of depending on an employee's memory and time. In practice, automations live in the CRM and its integrations (website, Meta, telephony, Telegram, databases), while people remain responsible for the decisions that require judgement.
Concrete automation examples
Every row below is an automation we have configured or built. All of them are “if X, then Y”, with rules we define together.
| When | Then |
|---|---|
| A lead comes in (website, Meta, phone, Telegram) | It is assigned automatically: round-robin, by area, by product or to whoever is available. The owner gets a Telegram notification with action buttons. |
| The client hasn't replied to a quote in 3 days | A reminder is created for the employee; after another 3 days, a suggested follow-up message; the manager sees the list of unanswered quotes. |
| An employee changes the status (e.g. “Viewing done”, “Quote sent”) | The manager is notified where relevant; the next task is created with a deadline; the client receives a confirmation message, if configured that way. |
| A sale is closed | The daily and monthly reports update themselves; accounting receives the data; the client goes onto the “come back in N months” list. |
| A document arrives (signed contract, photo, invoice) | It is attached to the client or the deal automatically; the responsible employee is notified; the document doesn't get left behind in a personal chat. |
| A lead from Meta | Meta → CRM (campaign preserved) → responsible employee → Telegram notification → “first contact” task with a deadline → escalation to the manager if it is missed. |
| An overdue task | Reminder for the employee; after the set deadline, a notification to the team lead; the list of overdue tasks per employee, in the morning report. |
| Monday, 9:00 | The weekly report — leads by source, conversion by stage, response time, performance per employee — lands in Telegram or by email, without anyone compiling it. |
One lead, from Meta to the right agent: an example flow
A complete example, with fictional figures, to show how the automations chain together.
Example flow
- A client fills in a Lead Ads form on Instagram, from one of the company's campaigns.
- The CRM creates the lead, with source and campaign preserved, and assigns it round-robin to the next employee on the team.
- The employee receives a Telegram message with the key details and the buttons “Take it”, “Call now”, “Not for me”.
- They take the lead; the CRM records the time (response time) and creates a “First contact” task with a 30-minute deadline.
- After the call, they update the card from the buttons and move the stage to “Quote sent”; a “Follow-up in 3 days” task is created automatically.
- The manager sees the lead, source, stage and response time in Web Admin; on Monday they receive the report with all of the week's leads.
The figures and names in the example are fictional; they illustrate the flow, not any client's results.
The processes we automate most often
By department. Almost all of them start with “the data enters the system on its own”.
Marketing
Leads from Meta and the website with source and campaign preserved; report by source; reactivation lists for past clients.
Support and service
Requests become tickets with an owner and a deadline; escalation when the deadline is missed; history per client.
Operations and deliveries
Orders with statuses, client notifications at every step, tomorrow's delivery list, overload alerts.
Management
Automatic daily/weekly/monthly reports, real-time dashboard, alerts for unanswered leads and overdue tasks.
Documents and invoicing
Documents attached to the client automatically; generation from templates; export to accounting — without replacing the accounting software.
Where the automations live
Automation isn't a separate program; it's a property of the system the team works in.
- Bsmart custom CRMRules written for your process; a Telegram interface for the field, Web Admin for management.
- Configured Bitrix24The platform's robots, triggers and automation rules, configured on your pipeline.
- IntegrationsWebsite, Meta, telephony/PBX, Telegram, databases, accounting — the sources and destinations of the data.
- AI, where it helpsClassifying a request, extracting data from a message, summaries for the manager — with human review.
How we approach automating a company
In three steps, without a 40-page “digital transformation audit”.
We map the repetitive processes
In a 45–60-minute conversation: what is done by hand, how many times a day, by whom, where time is lost or things get forgotten. We prioritise by impact and simplicity.
Outcome: the list of automations, in the order they are worth doing
We implement gradually
The first automation is the one with high impact and low risk (usually lead capture and distribution). We test with real data, then add the next one.
Outcome: automations that run, one at a time
We adjust to reality
After the first few weeks we look at what worked and what produced noise (too many notifications, rules that were too rigid). We adjust.
Outcome: automations that stay in use
Estimate the savings with your own numbers — the ROI calculator on the use cases page
Frequently asked questions about process automation
Short answers.
Where do we start if we don't have a CRM?
Usually with lead capture and distribution plus a weekly report — that is, with a CRM configured on your process and integrations for your lead sources. The remaining automations are added one by one.
We have Bitrix24. Can our processes be automated there?
Yes. We configure Bitrix24 robots, triggers and rules on your pipeline; where the platform doesn't reach, we add integrations or an external module.
How long does it take?
The first automations are usually configured as part of the CRM implementation. A standard customised CRM can be implemented in roughly 14 days, depending on integrations and process complexity. On an existing CRM, a few days for the first rules.
Can lead distribution from Facebook and Instagram be automated?
Yes. Leads from Meta Lead Ads enter the CRM with the campaign preserved and are assigned according to the company's rules, with a Telegram notification to the owner.
Do employees get too many notifications?
It's the most common reason automations get ignored. That's why we start with a few rules and adjust after the first weeks.
What can AI do in automations?
Classify requests, extract data from messages, produce summaries for the manager, suggest replies. With human review — not automatic decisions.
How much does it cost?
It depends on the number of processes, the integrations and whether a CRM already exists. You get a clear quote after a conversation.
Continue with
Request a demo
We show you, on an example close to your company, what the first three automations would look like — and tell you honestly which one is worth starting with. No commitment.
- A 45–60-minute conversation about your repetitive processes
- The list of automations, in the order they are worth doing
- A clear quote after the conversation