Before you merge contacts in Follow Up Boss, verify that the profiles represent the same person, decide which record should survive, and resolve conflicting ownership and field values. Treat the merge as a reviewed data change, not a shortcut for getting the next call started.
This focused guide interprets Follow Up Boss help documentation, accessed October 2, 2026. It is not a tested account walkthrough. Callion publishes it and has a commercial interest in lead-response software; no Callion integration or automatic cleanup capability is claimed.
Start with the consequence, not the button
Follow Up Boss says a merge cannot be undone. Merge Contacts documentation
Make the decision before executing it. If identity, ownership or retained information is uncertain, leave the records separate while a responsible team member investigates. Do not perform a real merge merely to see what happens.
The document also discusses older Action Plan behavior. This article does not generalize that wording to every current automation version. Have the account owner establish the effect on your actual workflows before approving a change.
Matching a record and approving a merge are different decisions
Follow Up Boss documents automatic matching by email, or by phone number together with first and last name. Lead Deduplication documentation
That describes the documented matching rule, not proof that any particular pair belongs together. For a manual cleanup, inspect the underlying requests and conversations through your authorized account access. Similar names, shared household details or a repeated property interest should prompt investigation rather than an automatic conclusion.
Keep a separate question in view: even if both records represent the same person, do they contain distinct requests that the agent still needs to handle? Your review should preserve those tasks rather than treating the second inquiry as disposable.
Choose the main record deliberately
The main contact retains its assigned agent, stage and marketing source. Merge Contacts documentation
Existing custom-field values on the main contact are not overwritten by a merge. Merge Contacts documentation
The practical implication is to decide the intended result field by field. Do not select the newest profile merely because it appears first, or assume combining records will select the most accurate value for you. If a desired correction is separate from the merge, identify it explicitly and use the account's authorized change process.
A pre-merge decision sheet
This proposed worksheet is an editorial contribution, not a claim that Follow Up Boss automatically performs these checks. Keep it in your team's approved system; avoid exporting personal contact details to an unapproved document.
| Question | Evidence to review | Decision to record before proceeding |
|---|---|---|
| Is this one person? | Source requests and existing conversation context | Same person established, or investigation still needed |
| What is the intended surviving record? | The candidate profiles and their current owners | Selected profile and a reason, not just its position in a list |
| Which information conflicts? | A field-by-field comparison | Desired value and the authorized person responsible for any separate correction |
| Are there separate open requests? | Unfinished questions or appointments across the profiles | Who will handle each remaining request |
| What other processes use these records? | Account-owner review of connected workflows | Expected effect confirmed, or change held pending clarification |
| Who accepts the result? | Named reviewer and intended outcome | Post-change review owner and escalation route |
Do not replace unknowns with guessed answers to finish the sheet. A held merge can still have an owner and a next step.
A synthetic conflict to work through
Imagine two profiles that the team has already verified belong to the same buyer. Profile A is assigned to Jordan and records an open-house source. Profile B is assigned to Casey and contains a later website request. Their custom notes disagree about the buyer's preferred appointment time.
The review is not simply “A or B?” First decide who should own the next response. Then resolve the appointment-time conflict from the underlying conversation. Finally, identify what must remain visible about both requests and what the account owner must check before combining the profiles.
This example does not establish that either source label is wrong, that a source should be replaced, or that a merge repairs attribution. It demonstrates a decision that should precede the click. No customer records or actual results are represented.
Check the result without assuming recovery
After an authorized change, compare the surviving profile with the approved decision sheet. Confirm the responsible agent understands the outstanding work. If the result differs from the intended one, stop further cleanup and ask the account owner or vendor support to review it; do not promise that creating another profile will restore the earlier state.
This article deliberately does not prescribe bulk cleanup, automation migration, legal permission to contact a lead or a complete recovery procedure. For workflow configuration, use the Follow Up Boss automation guide. For other source-specific operating questions, see the lead sources and integrations library.
A useful outcome is not simply fewer rows. It is a reviewed record with understood ownership and no forgotten request.