2.3Manage deadlines & follow-up
The essentials in 30 seconds
- Promise right: estimate the real, add a margin, announce the total — under-promise and over-deliver (early delights, late betrays).
- Inform before being asked: proactive milestones, early warning at the first delay risk, scheduled callback — every chase is a follow-up failure.
- Delay = early + honest + compensated: announce early, real reason with no jargon, new deadline kept + gesture — a well-managed delay builds loyalty.
Threaded mini-case — Rania turns a delay into loyalty
Karim's reshipped parcels are stuck: a part missing at the supplier, 2 days before the promised deadline. Rania hesitates: stay silent hoping it passes, or call right away? She calls: likely 2-day delay, real cause explained simply, new Friday-noon deadline kept 100%, free delivery and tracking SMS. Friday 10am, it's delivered — Karim leaves a review recommending the service.
Sequel to cases 2.1–2.2 — Rania's promise meets the test of reality.
1. Promise right: a realistic deadline + margin
Estimate the real time, add a margin, announce the total ("Thursday" for a likely Wednesday). Better to deliver early than late: being early delights, being late betrays — even by a day.
2. Follow up: inform before you're asked
Proactive milestones ("it's started", "it's on its way", "delivered"), early warning as soon as a delay threatens (with a new deadline + gesture), scheduled reminders (CRM: follow up on date). Customers who are informed don't chase: every chase is a follow-up failure.
3. Delays: announce, explain, compensate
Early (as soon as the risk appears, not on the day), frank (the real reason, no jargon), a new deadline kept + a gesture (free shipping, upgrade). A well-managed delay builds loyalty; a hidden delay fuels anger.
🔎 Concrete example — 🔎 Hands-on example — A delay turned into loyalty
J-2 : risque détecté → appel immédiat : « retard probable de 2 jours, cause : pièce manquante, nouveau délai vendredi 12 h tenu à 100 %, livraison offerte + SMS de suivi » Vendredi 10 h : livré + SMS → client qui recommande (avis cité)
Takeaway: early + frank + compensated = reinforced trust.
Lesson: the gesture costs less than a lost customer.
Section vocabulary
- Deadline keeping
- Respecting announced deadlines; a broken promise shatters reliability and trust.
Simple example: Rania delivers Friday 10am for a Friday-noon promise.
What it is not: promising Monday to please then delivering Thursday.
Reflex: only promise what you can keep, keep what you promise.
- Proactive information
- Keeping customers spontaneously informed of progress, without waiting for them to chase.
Simple example: Rania calls from 2 days before, then sends milestone SMS.
What it is not: leaving Karim in silence until D-day.
Reflex: warn before customers notice: milestones + early warning.
- Follow-up
- Supporting the request through to full resolution, never leaving customers uncertain.
Simple example: Rania schedules her callback and checks Friday that all is settled.
What it is not: closing the case at dispatch with no delivery check.
Reflex: log each commitment with a recontact date.
- Reliability
- Keeping what you promise (deadlines, commitments); the bedrock of trust and loyalty.
Simple example: Karim recommends the service because the new deadline was kept.
What it is not: seductive but hollow promises, never kept.
Reflex: under-promise and over-deliver, systematically.
- Realistic promise
- A commitment you're sure you can keep (better a prudent deadline kept than an untenable promise).
Simple example: “Thursday” announced for a likely Wednesday: built-in margin.
What it is not: the shortest possible deadline to reassure in the moment.
Reflex: estimate the real, add a margin, announce the total.
In practice — Hands-on - Manage deadlines and follow through
- Only promise what you can keep (a realistic, even cautious deadline) and keep what you promise.
- Inform proactively about progress, without waiting for customers to worry and chase (especially if a deadline slips).
- Follow through until full resolution; get back in touch to check everything is settled.
- Stay organised (log commitments and due dates, via a tool) so nothing is forgotten.
Ready-to-say script — announcing a delay that builds loyalty (1 min)
“Karim, I'm calling today because I see a likely 2-day delay: a part is missing at our supplier. I guarantee delivery Friday before noon, and I offer free delivery for this hitch. I'll SMS you at each step, and I'll call you back Friday to check everything arrived well. Does that suit you?”
Say it as soon as the risk is spotted (not on D-day), then keep the new deadline 100%.
Copy-paste template — deadline + follow-up sheet
COMMITMENT MADE (what, by when): _______________
BUILT-IN MARGIN: estimated real _______________ + margin _______________ = announced _______________
PROACTIVE MILESTONES (dates + channel): _______________
IF RISK: warn on _______________ + real reason _______________ + new deadline _______________ + gesture _______________
CALLBACK SCHEDULED on: _______________ / FINAL CHECK: _______________
Small business / low volume
A simple shared diary with promised dates + reminders is enough to never leave a customer without news.
Heavy load
Prioritize early warnings on at-risk cases: one call 2 days before beats ten excuses on D-day.
Email / SMS
Short written milestones (“gone”, “on its way”, “delivered”): customers track with no chasing.
SME in Algeria
Build local hazards (supplier, transport, wilaya) into the announced margin, without detailing them to customers.
✓ Best practices
- Margin in every announced deadline.
- Proactive milestones (CRM + reminders).
- Delays: early + frank + gesture.
✗ Common pitfalls
- Over-optimistic deadline to please.
- Silence until the due date.
- Delay without a gesture.
Key takeaways
- Keeping your deadlines is a pillar of trust: a broken promise is a sure way to lose a customer.
- Only promise what you can keep (a realistic deadline) and keep what you promise.
- Proactive information: spontaneously keep customers informed (a customer informed of a delay is calmer than one left in silence).
- Follow through until full resolution; it takes organisation (logging commitments).
48h Challenge — apply tomorrow
Take 1 ongoing commitment: check its margin, schedule 1 proactive milestone and 1 dated callback. If at risk, call today (early + honest + gesture). 15 minutes is enough.
- I promise realistically (real + margin) and I keep it.
- I inform proactively: customers never chase.
- I did the 48h challenge or scheduled its date.
Frequently asked questions
Is it better to promise a short deadline to reassure, even if you overrun it?
No — it's a false good idea that almost always backfires. Promising a short (or over-optimistic) deadline to please in the moment brings temporary relief, but if you miss it, you create far greater disappointment and break reliability — the foundation of trust. A customer promised "tomorrow" and delivered "in three days" is far more unhappy than one honestly told "three to four days" and delivered on time. The golden rule is the "under-promise and over-deliver" principle: better to announce a realistic, even cautious deadline (with a small margin) and meet it (or do better — which creates a pleasant surprise) than to promise the impossible and disappoint. A deadline kept, even a slightly longer one, builds trust; a short deadline missed destroys it. Customers hugely value reliability: knowing they can count on what you say. A company that systematically keeps its commitments, even modest ones, inspires more trust than one that promises the moon then disappoints. So resist the temptation to "please" with an unkeepable deadline: be honest about what you can really keep, and keep it. When unsure about a deadline, better to announce a cautious range and, if you do better, delight the customer. Trust is built on kept promises, not on seductive but hollow promises. It's a simple but fundamental customer-relations rule.
Why is informing customers "proactively" so important?
Because silence is one of the worst enemies of customer relations, especially when something drags on or runs late. A customer left without news while waiting for an answer or a resolution doesn't stay neutral: they worry, imagine the worst ("I've been forgotten", "my case is stuck", "they're not handling it"), get annoyed, and end up chasing — sometimes repeatedly, with growing frustration. Proactive information means taking the lead: spontaneously keeping customers informed of progress, before they have to worry and chase ("your request is well received, I'm handling your case and will get back to you by Friday"). It radically changes the experience: an informed customer, even of a delay or a slipping deadline, stays calm and confident, because they know they're being looked after and haven't been forgotten — uncertainty, more than the wait itself, is what distresses and irritates. In practice: acknowledge a request, flag that you're handling it, warn before a deadline is missed (rather than letting customers discover it), keep them posted at key stages. It takes a little organisation (logging commitments, remembering to call back) but it pays off enormously in satisfaction: a customer kept in the loop feels considered and reassured, and forgives hiccups far more easily. Conversely, leaving customers in silence lets them imagine the worst and turns an ordinary wait into a major irritant. Proactive information is one of the most appreciated marks of attentive customer service: it turns endured waiting into mastered waiting. Taking the lead to inform shows you're in control and care about the customer.
Rania spots 2 days before a delay risk on Karim's parcels. What to do?