Leads / Companies
In SprintHub, it is possible to configure smart rules to prevent data duplication, ensuring a more organized and reliable database. Check below the complete step-by-step to perform this configuration.
1. Access Settings
Click on System Settings ⚙️.
Then select the option Leads / Companies.
2. Manage Duplication Conflicts
This section allows you to prevent the creation of duplicate Leads or Companies, based on fields defined as unique (e.g.: email, phone, document).
➤ Conflict Check Operator
If you use more than one field with unique identification, choose the logical operator that will define when two records will be considered duplicates:
OR The conflict will be identified if at least one of the unique fields is equal between two records.
AND The conflict will be identified only if all the unique fields are equal.
This choice directly impacts the level of strictness in duplication control.
➤ Block Manual Creation of Conflicting Leads
Enable this option to prevent users from manually creating duplicate leads. When a conflict is detected, the system will automatically block the creation of the record.
Perfect, here is the revised text, organized and with a more fluent reading, maintaining the technical content and SprintHub's standard:
3. New Group
When to use groups?
The use of groups is recommended only when there is a need to allow multiple contacts with the same unique information (such as phone or email), without causing conflicts in the system.
👉 In these cases, contacts are still considered individual, even while sharing identical data.
Practical example: Companies that use SprintHub in the franchisemodel, where different franchisees use the system and need to keep copies of the same contact for each unit, without generating duplication conflicts.
⚠️ Important — How account assignment works in SprintHub
By default, when a contact sends a message to any account connected to the system, SprintHub performs an automatic search for an existing contact, using its primary identification (usually the mobile phone number).
🔹 Default behavior (without an assigned group)
Example:
The contact with the number AAA sends a message to the account BBB.
The system searches for a registered contact with the number AAA.
If it finds one, the service is automatically assigned to that contact.
In this scenario, there is no restriction by group — any contact with the same number can be used.
🔹 Behavior with an account assigned to a group
When an account is assigned to a group, the search logic becomes more restrictive.
The system starts considering only:
Contacts that are within the assigned group, or
Contacts that do not belong to any group.
Example:
The contact with the number AAA sends a message to the account BBB.
The account BBB is assigned to the group CCC.
The system searches for a contact with the number AAA that is:
In the group CCC, or
In no group.
➡️ If there is already a contact with the number AAA in a different group, that contact will not be used for the service.
4. Ignored Conflicts
In this section, you can consult the conflicts that were previously ignored, that is, duplicate records that were not intentionally merged.
This view helps in controlling and auditing the database over time.
✅ Conclusion
Correct configuration of duplication rules in SprintHub is essential to keep the leads and companies database organized, avoid rework and ensure more reliable data for automations, reports and decision making.
By adjusting conflict operators, manual blocks and groups, you adapt the system to your business reality, balancing control, flexibility and scalability.
Last updated
Was this helpful?