Why you are asked the same question three times in one visit

Nobody forgot to write it down

The natural interpretation of being asked your date of birth three times is that the first two answers went nowhere. Occasionally true. Much more often all three answers were captured, and the repetition exists because three distinct processes each required an answer of their own and none of them is permitted to borrow another’s.

That sounds like poor design, and sometimes it is. But a surprising amount of it is deliberate, and the deliberate parts are usually protecting something you would want protected. The trick is that the deliberate repetition and the accidental repetition look identical from a chair on the customer side, which is why the whole experience gets filed under incompetence when only part of it belongs there.

Identification is a gate, and there is more than one gate

The first request is generally about finding you. The second is about confirming that the record found is genuinely yours. Those are separate operations with separate failure modes: the first can retrieve the wrong file, the second is what catches it.

A third request often appears at the point where something irreversible is about to happen — money moving, an address changing, a document being issued. Verification is deliberately placed immediately before consequence rather than at the start of the conversation, because a check performed ten minutes and three topics ago has quietly stopped being a check on the thing about to occur. Anyone who has been asked to confirm a card number they gave at the beginning of the same call has met this pattern.

A handover loses more than it appears to

When you are passed from one person to another, what travels is the record, not the conversation. The record holds fields: name, reference, status, perhaps a short note. It does not hold the shape of what you explained, the order you explained it in, or the detail you mentioned that turned out to matter.

Notes help, but they are written under time pressure by someone summarising a discussion they were also participating in. The second person reads three lines and reconstructs a fifteen-minute exchange from them. Asking you to repeat the essentials is not laziness; it is the cheapest available way of finding out whether the summary matches reality, and the summary quite often does not.

Structured data travels, free text does not

Systems move information reliably when it sits in a defined field with a defined format. A postcode field arrives intact. A tick-box arrives intact. A paragraph typed into a notes box arrives as a paragraph in a notes box, which the next system may display, may truncate, or may not carry across at all.

This is why the interesting part of your situation is the part most likely to be asked for again. The routine details are structured and portable. The explanation of why your case is unusual is free text, and free text is the first thing to fall off the back of a transfer between two systems that were never designed together.

The third asking is often a different question

Listen closely to the wording and the repetitions stop looking identical. "What is your address" and "can you confirm the address we hold" are not the same question: the first collects, the second tests. One expects you to supply information; the other already has an answer and is comparing yours against it.

The same applies to being asked what you are calling about after explaining it twice. Early on, that question routes you. Later, it scopes the specific action about to be taken. A person who has decided the two are identical will find the third asking maddening, which is entirely understandable and also slightly unfair to the person doing the asking.

Making the repetition cheaper

You cannot remove the checks, but you can reduce their cost. Get a reference number early and lead with it, since a reference resolves the finding step in one move. Keep a short factual summary of your own case ready in the same words each time, because varying your description makes it look like new information and invites new questions.

And when a handover is coming, ask what is being passed on. The answer is a useful diagnostic. If it is a reference and one line, you now know that everything else is about to be asked again, and you can stop taking it personally.

One further habit helps more than it should. Where an organisation offers a way of submitting the unusual detail in writing — an email to a case address, an upload, a note attached to a reference — use it, because written attachments tend to survive transfers that spoken notes do not. It converts the part of your situation that keeps getting lost into the sort of object these systems are actually good at carrying.