Skip to content
The part of the process nobody writes down
What Nobody ExplainsThe part of the process nobody writes down

Behind The Counter

What “we’ll be in touch” is actually committing to

The phrase stands in for a target, a queue position and a contact method, and only one of those three is normally written down anywhere.

By Nikhil Bose3 min read

A barista reads an order in a cozy café with a pastry display and warm lighting.
Photograph by Ron Lach via Pexels
Editorial note. Independent reporting and analysis. Nothing here is sponsored or paid for. How we work.

One sentence covering three separate questions

The closing line of most service encounters is doing a lot of quiet work. It is answering, all at once, when somebody will make contact, who that somebody will be, and how they will try to reach you. Those are three independent questions with three independent answers, and compressing them into four words loses all of the detail that would let you plan around it.

It is not usually evasion. The person saying it often knows the answer to only one of the three, because the other two get decided after the case leaves their hands. What they can honestly tell you is that the work has been logged and will be picked up. Everything else is inference on your part.

Behind it sits a target rather than a promise

Most organisations attach a response target to each type of work: a number of working days within which somebody should make contact. The target is a planning figure used to size teams and to spot work that is drifting, and it is the thing that the phrase is standing in for. It is expressed as an upper bound, which means the whole distribution sits underneath it and most cases land well before the limit.

Two details in that definition cause most of the confusion. Working days exclude weekends and public holidays, so a five-day target crossing a long weekend is nine calendar days. And the clock starts when the case was recorded, which may be later than the day you called, particularly if the work was written down at one desk and entered at another.

The contact method decides more than the timescale

How the organisation intends to reach you shapes what silence means. A team that works by telephone will typically make a set number of attempts, at times that suit its own rota, and record each failure. A team that works by post produces one letter that either arrives or does not. A team working by email is subject to filtering nobody on either side can see.

This matters because a case can be genuinely progressed and genuinely invisible to you at the same time. Two unanswered calls from a withheld number and a letter to a previous address is, from the inside, a file showing three contact attempts and a customer who has not engaged. From the outside it is a fortnight of nothing at all.

Nobody in particular is going to be in touch

The natural reading is that the person you spoke to will call you back. In most structures they will not, because the work has gone into a queue read by a team rather than to an individual. Whoever picks it up next is decided by who is available and what they are trained to handle.

That has a practical consequence worth knowing. The person who eventually contacts you will start from the written record, which is a summary rather than a transcript of your conversation. If something mattered enough that the summary needs to carry it, saying so explicitly at the time — and asking for it to be noted — is far more effective than assuming the detail travelled because it was said aloud.

Silence is ambiguous by construction

The hardest thing about the phrase is that it makes waiting and being forgotten look identical. A case sitting in a queue, a case paused because somebody is waiting on a third party, and a case closed in error all produce the same experience: nothing arrives.

Many workflows also pause their own clock when a case is waiting on somebody else, which is reasonable — a team should not be measured on the time a supplier takes — but it means the target you were quoted has stopped running without any announcement. A case can therefore be comfortably inside its service level while being three weeks old.

Converting the phrase into something you can check

The useful questions are unglamorous and they almost always get answers. What is the target for this type of case, and is it working days? What date was the case recorded, which is the date the target counts from? How will contact be attempted, and from what sort of number? And is there a reference, so the next conversation does not begin from nothing.

A follow-up is then a factual matter rather than a complaint. You are not asking anybody to hurry; you are asking whether the case is where it should be by now, which is a question the system is built to answer. It also produces a second entry in the record, and a case with two entries is noticeably harder to lose than a case with one.

Common questions

How long should I leave it before chasing?

Until the stated target has passed, counted in working days from the date the case was logged rather than from your conversation. Chasing earlier rarely moves anything, because the case has not yet reached the point where anyone is expected to have looked at it.

Does chasing push the case back in the queue?

Not normally in the sense people fear. It usually creates a linked contact record rather than a new case, though occasionally a fresh enquiry gets raised separately, which is why quoting the original reference is worth the extra few seconds.

Why does nobody give an exact day?

Because the date depends on a queue whose depth changes daily and on staffing nobody can forecast precisely. An exact promise would be wrong often enough to generate more contact than it prevents, which is the outcome the target system exists to avoid.

Behind The Countercountersserviceexpectationsprocess
Nikhil Bose
Reporter, What Nobody Explains

Nikhil writes the explanatory pieces on behind the counter, paperwork, queues & waiting and would rather show the working than assert the conclusion.