A hypothetical buyer orders equipment and receives an offer to buy the same item again a month later. The reminder ran on schedule. Common sense had not been included in that schedule.
Repeat sales start with a suitable reason. One customer may need consumables; another may have a new project to discuss. Sometimes no offer is appropriate yet.
Separate two scenarios
In the first, the customer contacts you again. In the second, your company plans a follow-up for a previously agreed reason. These are different events, best governed by separate rules.
Bitrix24 supports repeat leads and deals. The official documentation explains their behaviour depending on CRM mode and sales history. An existing contact should not automatically be considered ready to buy again.
Check your portal’s settings. Understand when a new record is created, where an inquiry lands, and whether an employee might accidentally continue an already closed sale.
A hypothetical example: consumables after delivery
A salesperson sells equipment and asks whether discussing consumables later would be useful. The record stores the agreed reason, an approximate date, and the preferred communication method.
A new requirement becomes a separate sale linked to the same customer. The previous purchase history remains available, while its amount and outcome are preserved.
Before contacting the buyer, review the context. Was the equipment actually delivered? Is there an unresolved service request? Offering consumables while a fault remains unresolved sounds like a joke the company never intended.
Start with a reminder to an employee
For the first launch, configure an internal reminder for the owner and test the scenario using training data. Add automatic external messages after checking conditions, exceptions, and contact rules.
An automation rule is a system action governed by specified conditions. Rules, conditions and communication channels depend on the plan, settings, and provider. Do not promise an identical scenario on every portal.
For customers in Kyrgyzstan, record their chosen language and suitable contact time. A previous purchase does not replace agreed rules for further communication.
Exceptions matter more than an attractive template
Before launch, answer these questions:
- who removes the reminder if the customer declines further contact;
- what happens after cancellation or an unresolved complaint;
- who follows up when ownership changes;
- how simultaneous messages from different employees are prevented;
- where the conversation outcome and next action are stored.
Track returning inquiries and company-initiated contacts separately. Otherwise reports mix customer demand with salesperson activity.
Assessing usefulness
Start with a small agreed customer group. Check whether contact reasons are relevant, outcomes are clear, and unnecessary records are avoided. Message volume alone does not establish value.
QQDev configures Bitrix24 automation and checks exceptions. Use the automation page to discuss a specific follow-up cycle, from its trigger to stopping it. One anonymised purchase example is enough to begin.