How to track promises made on sales and support calls

Most deals and tickets stall on a forgotten promise

Listen back to a week of lost deals and you rarely hear a dramatic objection. You hear a rep say «I'll send you the revised proposal on Thursday», and then no revised proposal. You hear a customer say «I need to check with our finance director», and then nobody asks how that conversation went. You hear a support agent say «someone from billing will call you back tomorrow», and the customer waits.

Promises are where a call turns into work. They are also the part of a call least likely to survive it. The rep writes a note from memory an hour later, after two more calls. The note says «send info» with no date. The customer's side of the bargain is not written down at all, because it did not feel like a task for the rep.

Recording a call is not the same as knowing what happened on it. The recording holds every promise, but nobody is going to listen to forty minutes to find one sentence. The promises need to be lifted out of the call and put somewhere the team actually looks.

What a trackable promise looks like

A promise you can track has the same shape every time. If one of these parts is missing, the promise is not yet trackable, and the gap itself is worth noticing.

• What. The concrete thing: a revised quote, a callback, a contract draft, a refund, a site visit. «Get back to you» is not a what.
• Who. The named person who owns it, on either side of the call. A promise owned by «the team» is owned by nobody.
• By when. A date or a moment: Thursday, end of the month, after the board meeting. When the call says only «soon», record it as undated, and ask for a date on the next call.
• Where it was said. The second of the recording, so anyone can hear the exact words when the promise is later disputed or unclear.

The customer's promises matter as much as yours

In B2B sales the most important promises are often made by the buyer. «I'll share this with our procurement team.» «The CFO has to approve anything above this amount.» «We decide after the budget review in November.» Each of these is a commitment with an owner and a date, and each one tells you what will actually move the deal.

Tracking them changes the next call. Instead of «just checking in», the rep opens with «you were going to take this to your CFO after the budget review; how did that go?» That is a better call for the buyer too, because it respects what they said.

The customer's promises also connect to the questions every sales leader asks about a deal: who decides, what the budget is, and what the timeline looks like. Callens gives each call five judgments, what the customer wanted, who decides, the budget, the timeline and the outcome, each tied to the second it rests on. Read beside the list of promises, they show whether a deal has a real path or only goodwill.

Support calls are full of promises too

Sales teams talk about follow-ups; support teams live on them. «We will call you back once the technician has checked.» «The replacement ships this week.» «I have escalated this to my supervisor, you will hear from them tomorrow.» Each of these sets an expectation, and each missed one usually comes back as a second call from a customer who is now angrier than on the first.

Tracking support promises answers two questions a support leader cares about. The first is operational: which callbacks and escalations are due today, and who owns them. The second is about policy: which promises are agents making that the company cannot keep? If agents regularly promise a delivery date the warehouse never meets, the fix is not coaching one agent. It is changing what agents are allowed to say, or changing the process behind it.

Broken promises also show up as risk on the call itself. Callens types risks, including churn, expectations and pricing, and grades each one low, medium or high, so a call where a customer reminds the agent of an earlier unkept promise does not look like any other routine call.

One queue for the team, not a notebook per rep

Promises scattered across personal notebooks, CRM notes and chat messages cannot be managed. A manager cannot see what is still open, a colleague cannot cover for a rep on leave, and a handover to a new account owner loses everything that was said out loud.

Callens lifts commitments out of each call, what was promised, by whom and by when, and puts them into one team queue. The by when is kept as it was said on the call, each promise is marked open, done or dropped, and the queue is ordered by how long each promise has waited. The point is not the software. The point is that there is one list, it is built from what was actually said, and the whole team can see it.

A simple weekly routine, run by the team itself, makes the queue useful:

• Read the by when on each open promise and pick out, by owner, the ones your team counts as due this week or already late.
• Look at undated promises and decide who will ask for a date.
• Check the customer's open promises before each follow-up call.
• When a rep leaves or changes territory, walk the new owner through the open promises on their accounts.

When a promise is disputed, go back to the second

Support leaders know this conversation well. A customer says «your agent promised me a full refund». The agent remembers offering a credit. Without the recording, it is one memory against another. With the recording, it takes a minute.

The minute only works if you can reach the right moment directly. Callens cites the second of the recording behind every claim, and every model-produced line is checked against a real segment of the transcript before it is stored. So a promise in the queue is not a model's guess about the call; it points at words someone actually said.

The same logic helps with patterns. Search finds the moment something was said however it was phrased, so a manager can find every call where a rep offered an extension or promised a callback within the day. A saved search can become an email alert that carries a count of new matches, never the content, which is enough to know when a new kind of promise starts appearing on calls.