---
id: KB-CC-003
url: https://app.codecontract.io/help/contacts-and-channels/keeping-contacts-up-to-date
idioma: en
categoria: contactos-canales
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CC-001, KB-CC-002, KB-CC-018]
citadoPor: [KB-CC-008, KB-ET-012, KB-CC-010, KB-CC-005, KB-CC-006, KB-CR-010]
---

# Keeping contacts up to date

_A wrong contact costs two weeks, and it was almost always knowable in advance._

**Responde a:** the supplier's email is wrong · update contact details · duplicate contacts · the person no longer works there

Most stalled cases are not stalled because the other side does not want to: they are stalled because the notice went to an address nobody reads any more. And the system knew that from day one.

**En corto**

- A bounce is information: the address is wrong, not that they are ignoring you.
- Duplicating a contact splits their history in two and neither half tells the whole story.
- Asking for a mobile number at onboarding saves weeks later.

## The three things that most clutter it

| Problem | How you notice | Fix |
| --- | --- | --- |
| Bouncing addresses | The case flags it on the first send | Fix it on the contact record, not just that send |
| Duplicate contacts | The same person with two records | Merge them so the history is not split |
| People who have left | They never open anything | Ask the company for their replacement |

## The review worth doing

Once a quarter, look at contacts that have bounced or have opened nothing for months. There will be half a dozen, they take twenty minutes to fix, and they are exactly the ones about to block your next case.

> [!WARNING]
> Fixing the email only on one send leaves the record wrong, and the next case fails the same way. Fix the record.

> [!NOTE]
> When a third party tells you their contact person has changed, update it that day. It is the only moment you have the right detail without hunting for it.

**Can a company have more than one contact?**

Yes, and it helps: one for paperwork, another for invoicing.

**What happens to history when merging?**

It joins up. That is the reason to merge rather than delete one.

**Can I import contacts from our system?**

Yes, and it is the fastest way to start.

## Ejemplos

**A company has eleven stalled cases and none are moving.**

- Filters contacts that bounced
- Fixes seven addresses on their records
- Asks for replacements for two people who have left

→ Nine of the eleven cases move that week.

**An email bounces and nobody corrects it.**

- Updates the contact on the first bounce

→ Notices stop getting lost.

**Each person has their own version of the contact.**

- Centralises the company record

→ The supplier receives a coherent message.

**The contact has not been updated in two years.**

- Reviews contacts at every campaign

→ The address book reflects reality.

**You discover the contact left when chasing.**

- Asks for the new contact before the next round

→ The chase reaches somebody who can act.

**There are duplicate contacts at the same company.**

- Merges the duplicates

→ The supplier receives one, not three.