---
id: KB-ET-003
url: https://app.codecontract.io/help/your-workspace/your-contact-book
idioma: en
categoria: espacio-de-trabajo
subcategoria: contactos
audiencia: usuario
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-ET-002, KB-TL-004, KB-PR-001]
citadoPor: [KB-TL-010, KB-ET-018, KB-ET-020, KB-TL-027, KB-ET-001, KB-ET-002, KB-CC-001]
enLaApp: https://app.codecontract.io/contacts
---

# Your contact book, and why it decides whether people reply

_A properly recorded contact is the difference between people delivering and you chasing._

**Responde a:** how do I add a contact · import contacts from a spreadsheet · contact groups for batch sending · why is a contact not receiving notices · change the language a supplier receives

The contact book looks like the boring part and it is the one with the biggest effect on whether people reply. Most of the "nothing ever arrives" cases that reach support are an email with one letter wrong, or a landline where a mobile should be.

**En corto**

- Email and mobile: with both, if one fails you can chase on the other.
- The contact's language decides what language they receive.
- Groups let you request from or send for signature to fifty people at once.
- A bounce is flagged on the case: you do not wait weeks to learn the address was wrong.

## What to record for each contact

| Field | Why it matters |
| --- | --- |
| Name and company | It appears in the notice; without it, it reads as a mass mailing |
| Email | The default channel |
| Mobile | Essential for advanced signature and very useful for chasing on another channel |
| Language | Decides what language the notice arrives in, with nothing for you to translate |
| Preferred channel | Some people never read email but do read WhatsApp; respecting that raises replies |

> [!WARNING]
> A landline in the mobile field saves without complaint, but breaks advanced signature: the code goes by SMS and never arrives. It is the single biggest time-waster.

## Groups

A group is a set of contacts you can request from or send for signature in one go: "raw material suppliers", "subcontractors on the Valencia site", "all staff". Each person gets their own link, not a shared send, so traceability stays individual.

## When something does not arrive

1. **Check whether the email bounced** — The case flags it. A bounce means a mistyped or non-existent address.
2. **Check whether the link was opened** — It separates "it never arrived" from "they have not looked", which are two different problems with two different fixes.
3. **Try another channel** — If you hold the mobile, resending by SMS or WhatsApp usually solves it immediately.

## Frequently asked questions

**Can I import my contacts from a spreadsheet?**

Yes. It is worth checking the mobile numbers first: that is the field that travels worst from a spreadsheet, especially with international prefixes.

**Can one contact cover several people?**

Each contact is one person. If two people handle you at a supplier, that is two contacts, so each receives their own.

**What happens if I edit a contact with running processes?**

Later sends use the new details. What was already sent stays as it was, with its record.

**Can a contact be deleted?**

Yes, but whatever took part in a case stays in the history: if it vanished, traceability would stop being traceability.

## Ejemplos

**A company imports 200 contacts from a spreadsheet and a week later 15% have received nothing.**

- Filters the bounces flagged on the cases
- Fixes mistyped addresses and mobiles missing their country code
- Resends only to those, without rebuilding the requests

→ Bounces drop to zero, and what was a data problem stops being blamed on "suppliers never reply".

**The request goes to a generic mailbox and nobody replies.**

- Records the specific person at each company

→ The request reaches somebody who can act.

**The contact no longer works there.**

- Updates the contact on the first bounce

→ Notices stop getting lost.

**Each person keeps their contacts in their own inbox.**

- Centralises the address book

→ Follow-up does not depend on who is in.

**Contacts from the same company get duplicated.**

- Reviews and merges the duplicates

→ The supplier receives one message, not three.

**A contact does not read email but does read their phone.**

- Records the channel they actually use

→ The notice arrives where it gets read.