What it means
Record the commitment clearly by linking the promised date and time, time zone, case, customer contact and chosen channel. Some contracts prescribe status updates, while other promises arise in a conversation, and both matter.
Do not set a vague "soon" if the customer is relying on a decision for their own schedule, because for a critical outage the update cadence may be much shorter than for a minor billing question. Define meaningful contact.
An automated "we are working on it" message sent with no current review may technically touch the customer but not fulfil a specific promise, whereas a follow-up should contain a verified status, owner, action or next time, expressed without disclosing another customer's details. Internal notes, failed outbound calls and bounced emails need separate status, since they may not show that the customer actually received an update.
Measure lag consistently: the clock starts at the promised or required update time and ends when the appropriate message or call reaches the agreed channel. Early updates can be on time but may create a new next-update promise.
Record the actual timestamps and whether a delay was caused by an unverified contact route, internal handoff or missing technical input, because a customer-initiated call after the missed deadline does not turn the original commitment into an on-time update. Route ownership: a case worker may need a technician or finance decision, but the customer-facing owner should still know when an update is due, with reminders and a deputy when the owner is away.
Escalate if a promised resolution date is at risk, because an update is not a substitute for fixing the problem. Avoid changing the due time silently to make the KPI look better; if the issue genuinely changes, tell the customer and record the new agreement.
Review patterns by severity, team and cause, since a few minutes late on a routine update differs from days of silence after a safety concern. Track the share of promised updates met, the median and longest lag, and repeat cases.
Sample message quality so staff do not send empty updates just to meet a timestamp, and improve access to information and cross-team handoffs when agents repeatedly wait for answers. For owners, follow-up lag measures reliability of communication after the first impression.
Keeping an update promise can protect a relationship even when the business cannot yet provide the outcome the customer wants.
In practice
Real-world examples.
Example
A repair team tells a customer the part is still in transit before the promised Friday update deadline, then gives a verified next check.
Example
A support agent leaves for holiday and hands a Monday update commitment to a named deputy.
Example
A billing case receives an internal finance note on time, but the customer is contacted two days late; the measure records the customer lag.
Formula
Calculation
Follow-up lag = Actual meaningful customer update time - Promised or required update time
Worked example. An invented agent promises an update by Thursday 15:00 but sends a verified status Friday 10:00.
- Follow-up lag is 19 hours after the promised time.
- Record the reason and whether the customer faced a material decision during that period.
Use the customer's relevant time zone and separate an attempted contact from one delivered through the agreed route.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Meadow Devices, an invented equipment service firm. It acknowledged a customer's broken machine within an hour and promised an update the next afternoon. Engineering needed more time to diagnose the fault, and support waited for a complete repair plan before writing again. Three days passed.
The customer arranged an expensive alternate service because it thought Meadow had stopped working on the case. Meadow assigned a customer-facing case owner and recorded the next update time separately from the repair deadline. The owner checked engineering's actual status and sent an honest note when diagnosis was still open. A deputy covered promised updates outside the agent's shift.
Managers sampled follow-ups for useful facts rather than counting a template email as success. The owner learned that a quick first reply did not compensate for silence afterward. The team could not always repair a machine on schedule, but it could keep the communication promise while deciding what came next.
Watch out
Common mistakes.
- Treating a fast first response as proof that later update promises were met.
- Sending generic messages with no verified status simply to stop the KPI clock.
- Moving a promised update deadline internally without telling the customer.
Questions
People also ask.
Does a follow-up require a final resolution?
No. It can give a truthful current state and next check when the issue remains open.
Does an internal case note count?
Not as a customer update unless the agreed customer channel actually receives meaningful information.
How should teams use the measure?
Review missed promises and message quality together, then fix ownership and information gaps.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%