> 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/general/contacts/leads-common-questions/contacts-merge-leads-and-resolve-data-conflicts/contacts-how-to-merge-leads-that-have-no-conflicts.md). # Contacts - How to merge leads that have no conflicts In SprintHub, you can merge Leads even if there are no conflicts. This feature is extremely useful in cases where support is handled on one device, but another action is performed on another. In this case, two identical leads are created, but with different phone numbers, which are fields that have unique validators and would normally indicate a conflict if there were two leads with the same phone number. In this case, we have two identical leads, but on one of them the support was handled and on the other a meeting was scheduled.

In this example, we will call the profile that has all the Lead information the "Main Profile", and the profile where the scheduling was done the "Secondary Profile".

Enter the support of the secondary profile, that is, the profile you want to merge into the main one. Within the support in SAC360, click the three dots in the upper-right corner and then click "Remove Relationship"
Now, your support will not be linked to any lead.
Click "Relate" and search for the name of the Main Lead
Click "Relate"; this way, the support cases, meetings, and all other information will be transferred to the Main Lead.
If a confirmation box appears for the action, read the message carefully, and if you agree with the procedure performed, click "Yes". This way, there will be only 1 lead, bringing together the information from 2 leads.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sprinthub.com/en/topics/general/contacts/leads-common-questions/contacts-merge-leads-and-resolve-data-conflicts/contacts-how-to-merge-leads-that-have-no-conflicts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.