Why promises made on service calls get lost, and how to keep them

"I'll call you back tomorrow." "We'll send the corrected invoice this week." Service agents make promises like these all day, and most of them are kept. The ones that slip through cause a disproportionate amount of work: repeat calls, escalations and customers who stop trusting what they are told. This article looks at why promises get lost between the call and the follow-up, and at practical habits that keep them.

What a broken promise really costs

A missed callback rarely shows up as a line in a report. It shows up somewhere else, a few days later.

• A repeat call. The customer calls again to ask what happened. That call is longer than the first, because the agent has to reconstruct what was said and by whom.
• A complaint. The original problem may have been small. Being forgotten is what turns it into a formal complaint.
• An escalation. The second or third call often goes to a team lead, which takes time away from coaching and other work.
• Lost trust. Once let down, a customer treats the next promise with suspicion.

None of this needs a statistic to be convincing. Ask any service team lead how many of their difficult calls this week started with "nobody called me back", and you will get an answer.

Why promises get lost

Promises rarely get broken on purpose. They get lost because of how they are made and recorded.

There is no note

The agent agrees to something at the end of a busy call, intends to write it down, and then the next call comes in. The commitment lives only in the agent's memory and in the customer's.

The wrong person owns it

"We'll look into it" leaves open who "we" is. The agent assumes the back office will act, the back office never hears about it, and the customer waits. Handovers between teams, shifts and channels are where ownership disappears.

The date is vague

"Soon", "in a few days" and "as quickly as possible" mean different things to the agent and to the customer. The customer usually hears the shorter version. Without a clear date, nobody knows when the promise has become overdue.

The words get lost in translation

Even when a note exists, it is often a summary written after the call: "cust wants refund, will check". The exact commitment, such as "I'll refund the delivery charge and email you the confirmation by Friday", is gone. The next person to pick it up may promise something different.

Make commitments explicit on the call

The most effective fix happens during the conversation itself. Train agents to state every commitment with three parts.

Owner, what and when. If one of the three is missing, the promise is not finished.

A few practical habits help:

• Only promise what you control. If the agent depends on another team, say so: "I'll pass this to our returns team today, and they'll contact you by Monday."
• Give a date the team can meet. A slightly later date that is kept beats an optimistic one that slips.
• Name the channel. Will the customer get a call, an email or a letter? Saying it removes another source of misunderstanding.

Confirm the next step before you hang up

The last thirty seconds of a call are where commitments become clear or stay fuzzy. A short closing summary works well:

"So to confirm: I'll email you the corrected invoice by Thursday, and if you don't see it by then, call us and quote this reference."

This does three things. It gives the customer a chance to correct a misunderstanding while they are still on the line. It forces the agent to put the commitment into words, which makes it easier to record accurately. And it sets a shared expectation, so a slightly delayed follow-up does not come as a surprise.

The confirmation should cover the customer's side too. If they need to send a document or make a payment, say what and by when.

Track promises as tasks, with the original words

A promise that is not tracked somewhere will eventually be forgotten. The simplest reliable approach is to treat each commitment as a task with:

• An owner, a named person rather than a team.
• What was promised, ideally in the words used on the call.
• A due date, if one was agreed. If none was agreed, leave it empty rather than inventing one, and make that gap visible.
• A link to the call, so anyone picking it up can hear or read the context.

Keeping the original wording matters more than it sounds. "I'll refund the delivery charge" and "I'll see what I can do about the delivery charge" are very different commitments. When the task carries the exact quote, the person following up knows precisely what the customer was told, and does not over-deliver or under-deliver.

Review overdue promises every day

Tracking only helps if someone looks at the list. A short daily routine is enough:

1. Check what is due today and what is overdue. Each team lead looks at their team's open commitments.
2. Act or reassign. If the owner is off sick or on another shift, move the task to someone who can complete it today.
3. Call before the customer does. If a promise is going to slip, a proactive call ("the invoice will be a day late, here's why") preserves far more trust than silence.
4. Look for patterns. If the same kind of promise keeps going overdue, the problem is probably the process, not the agent. Maybe refunds need a faster approval path, or agents are promising dates another team cannot meet.

Use checks to build the habit

Coaching works best when it is based on what actually happens on calls. Simple yes/no checks, applied to every call, show whether the habits above are sticking. Some examples:

• "Did the agent confirm the next step and when it will happen?"
• "If the agent promised a callback, did they give a specific day or time?"
• "Did the agent say who will handle the follow-up?"
• "Did the agent summarise what the customer needs to do, if anything?"

Each check should have a clear answer that can be backed up by something said on the call. If the call does not settle it, for example because no follow-up was needed, an honest "not answered" beats a forced result. For more on writing checks that give reliable results, see our guide to yes/no QA checks.

The results are useful in two ways. For individual agents, a failed check with the exact quote is a concrete coaching point. For the team, trends show whether a new closing script is being used, and which teams need more support.

How VOIX helps

VOIX records and transcribes every call it receives from your phone system and turns commitments made on the call into suggested follow-up tasks, each with the words behind it. A person reviews and approves each task, so nothing is created behind the team's back; see follow-up tasks for more. Checks such as "Did the agent confirm the next step and when?" run on every call, and every answer is backed by the words from the call. Team leads see these results per team and rep, which makes coaching specific; the customer service use case shows how it fits together.

This article is general information, not legal advice. Check the rules that apply to your organisation with your legal adviser or data protection officer.

New to a term? See the glossary.

VOIX for customer service teamsCatch every promise, complaint and callback.