---
id: KB-CC-018
url: https://app.codecontract.io/help/contacts-and-channels/when-someone-replies-and-it-does-not-register
idioma: en
categoria: contactos-canales
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CC-011, KB-CC-015]
citadoPor: [KB-CC-003]
---

# When someone replies and it does not register

_They answered, and for you they are still silent. It is nearly always one of three things, all fixable._

**Responde a:** a supplier says they already replied · the reply does not show in the platform · still getting reminders after replying · replying to a noreply address

It is one of the most awkward conversations: you ring a supplier to chase and they tell you, quite rightly, that they sent it two weeks ago. And they did. They sent it — it just landed somewhere it does not count as an answer.

## The three reasons, by frequency

| What happened | How it shows | How to avoid it |
| --- | --- | --- |
| They replied to an automatic notice | The reply appears nowhere | Have the company mailbox connected |
| They wrote a new email instead of replying | It arrives, but loose: not tied to what you asked | Ask them to reply to the message, subject unchanged |
| They answered from another address | It arrives from someone the address book does not know | Hold the real address of whoever answers, not their boss's |

> [!IMPORTANT]
> There is a fourth situation, harder to spot, and worth knowing: **if you asked that person for several things at once and they reply without the reference, their answer is tied to the most recent open request**. It arrives, it registers, and it lands in the wrong place: one request looks answered when it is not, and the other keeps chasing. That is why asking for three things in three separate messages is not bureaucracy — it is what makes each answer land where it belongs.

## What to do once it has happened

1. **Ask them to resend by replying to the original message** — Subject untouched: that is where the reference that ties it lives.
2. **If they no longer have it, send again from the platform** — Better a new, properly linked message than one attached by hand.
3. **And note on the card the address they answered from** — It is usually the one they will always use, and it stops the repeat.

> [!WARNING]
> Before chasing anyone, look at the company mailbox. **What a third party replies lands in your usual email**, and if that mailbox is not connected the platform cannot know anyone answered: it will keep counting the days and sending reminders to someone who already did their part. It is not the supplier's fault, and it is the cause most often mistaken for someone else's neglect.

## How to stop tripping over this

**En corto**

- One request, one message: answers stop getting mixed up.
- Always ask for replies on the same thread, subject unchanged.
- Mailbox connected, and checked now and then.
- And before chasing by phone, check whether the answer is there and went unseen.

> [!NOTE]
> Chasing someone who already replied carries a cost that shows up nowhere: next time they take longer, because they no longer assume that sending it achieves anything.

**Can I reply to an incoming message?**

Yes, and it is best done from the platform so it stays on the same thread.

**What if they answer a message by WhatsApp?**

It arrives, but elsewhere; say in the message where you want the reply.

**Are the attachments they send kept?**

They are tied to the request if the message is. Hence the fuss about the subject.

## Ejemplos

**A company chases a certificate by phone that the supplier insists was sent.**

- Checks the connected mailbox and asks them to resend by replying to the message

→ The certificate shows up tied to its request, and the supplier stops getting reminders.

**Somebody replies by email and it is not on the file.**

- Uploads the reply to the file

→ The history reflects what happened.

**The reply lands in one person's inbox.**

- Agrees a single channel for replies

→ Invisible replies disappear.

**Somebody who already replied gets chased.**

- Checks the file before chasing

→ An unfair chase is avoided.

**The reply comes by phone.**

- Records what was said in the file

→ What was said leaves a trail.

**Nobody knows whether a reply closes the request.**

- Marks the status on receipt

→ The file moves on.