> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/system-settings/leads-companies.md).

# 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 guide** to carry out this configuration.

***

{% embed url="<https://youtu.be/SnXv3h5kPqk>" %}

***

#### 1. Access Settings

1. Click on **System Settings** ⚙️.
2. 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, ID number).

**➤ 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**\
  A conflict will be identified if **at least one** of the unique fields is the same between two records.
* **AND**\
  The conflict will be identified **only if all** the unique fields are the same.

This choice directly affects the level of strictness in duplicate 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 easier to read**, while maintaining the technical content and SprintHub's standard:

***

#### 3. New Group

**When should groups be used?**

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, the contacts are still considered **individual**, even though they share the same data.

**Practical example:**\
Companies that use SprintHub in a **franchise**, where different franchisees use the system and need to keep **copies of the same contact** for each unit, without creating 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 **main identifier** (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 found, the service is automatically assigned to that contact.

In this scenario, **there is no group restriction** — 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 then considers 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**, this contact **will not be used** for the service.

***

#### 4. Ignored Conflicts

In this section, you can **view conflicts that were previously ignored**, that is, duplicate records that **were not intentionally merged**.

This view helps with control and auditing of the database over time.

***

#### ✅ Conclusion

Proper 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**.
