Why kept promises matter more than bold ones
The customer experience foundations hub makes the case in its section on expectations: experience is judged against expectation, marketing sets the expectation, and the cheapest fix for a mismatch is sometimes to change the promise. Advertising that promises effortless setup makes an adequate setup feel like a failure. The hub sets out the discipline in three sentences: take the main claims, find the step in the journey where the customer will test each one, and where the test fails either fix the step or soften the claim, as a recurring review rather than a one-off project. This tutorial runs that review. The expectation-disconfirmation model describes the mechanism: satisfaction is the experience judged against the expectation the marketing set.
A bold promise that is broken costs twice. It costs the customer who feels misled, who complains, returns the item or quietly leaves, and it costs every later customer who reads that customer's review. The customer retention strategy guide lists the reasons customers leave; a gap between what was promised and what arrived sits behind several of them, and it is one of the few that marketing can close on its own. A kept promise, even a modest one, does the opposite: it produces a customer whose experience matched what they were told, which is the basis for staying and recommending. Many promises are first tested in a customer's early weeks, which is why the tutorial on onboarding customers for services and products designs the path from paying to first value with the promise in view.
There is also an obligation side, which the site's guides state at a general level. In the UK the Advertising Standards Authority's codes are the reference for whether a marketing claim was acceptable, and the Competition and Markets Authority, the UK's central consumer protection enforcer, enforces consumer protection law on misleading practices. The practical consequence for this check is simple: a broken objective claim, such as a stated time, price, result or feature, is corrected or withdrawn, not merely reworded in a gentler tone. Whether a particular claim is acceptable is a question for the business's approvals process and qualified advisers, not for this tutorial. This is educational, not legal advice.
The check sits beside three existing practices and repeats none of them. The claims library tutorial records objective claims with their approved wording and evidence; the promise check adds the promises customers infer and asks whether the experience delivers them. The tutorial on walking the customer journey walks the journey as a customer; the promise check uses that walk as one source of evidence. And the service recovery and complaints guide traces complaints back to promises after the fact; the promise check looks for the gap before the complaints arrive.
Before you start
- Read the claims library tutorial. If the business has a library, it is the starting list of stated claims and their approved wording. If it has none, this check will surface the claims a library should hold.
- Have a journey map or stage list. The journey stages guide defines the stages from awareness to loyalty, and the customer journey mapping framework summarises the map. A simple list of the steps a customer goes through is enough to start.
- Gather the evidence sources. Complaints, returns and their reasons, reviews on your own site and elsewhere, support contacts tagged by reason, cancellation reasons and sales notes. Remove names and contact details before the material is shared.
- Bring the right people. Someone who writes the marketing, someone who runs the operation the promise depends on, and someone from support who hears what customers say when a promise breaks.
- Know who approves claims. Any change to a claim with a legal dimension goes through the business's approvals process; identify that route before the check produces changes.
The steps
Collect the promises from every channel
Gather everything the business currently says to customers before they buy and while they are new: adverts, the website and each Landing PageThe page a visitor arrives on from a campaign, built to turn that visit into one action., product and service descriptions, leaflets and signage, sales scripts and proposals, booking and order confirmation emails, onboarding messages and the help centre. Copy each promise word for word with its source and where it runs. Include promises in the message structure as well: the messaging house template holds the core message and pillars every channel is meant to express, and each pillar is a promise in its own right. Expect the list to be longer than anyone thought.
Include the promises customers infer
Customers hear more than the words. A photograph of a spotless room implies a result; "we're a small family team" implies personal attention; "book in seconds" implies the rest of the process will be quick too. For each channel, write down what a reasonable customer would expect after reading it, in their words. The value proposition canvas helps: the gains and pain relievers the marketing describes are promises about the customer's outcome, and each can be tested later in the journey. Ask support what customers say they expected when they complain; those sentences are the inferred promises.
Find the moment each promise is tested
For each promise, name the step in the journey where the customer first finds out whether it holds: the first delivery, the first visit, the first bill, the first time they need help. Use the journey stages or the map to place it. Some promises are tested once, such as a delivery date; others are tested repeatedly, such as a promise of reliability, and each repetition is a TouchpointAny interaction between a person and a brand, paid, owned or earned, before, during or after a purchase. that can break it. Where several promises are tested at the same step, that step deserves the most attention. Where the business wants to see what sits behind a step, the service blueprint tutorial draws the staff actions and systems that decide whether the promise holds.
Gather evidence from complaints, returns, reviews and contacts
For each test moment, collect what customers did and said there. Complaints that mention what they expected, returns and their reasons, with the Return RateShare of orders or units sold that customers sent back. for the products concerned, reviews that compare the experience with the description, support contacts tagged to that step, and cancellation reasons. A reason list applied consistently makes this far easier, which the tutorial on tagging support contacts by reason builds. Add a walk-through of the step yourself, and for promises about time, the business's own records of how long the step actually takes. Count with a base, such as contacts per orderSupport contacts in a period divided by orders, active customers or bookings in the same period, showing how often customers need help., and keep a few quotes in the customer's own words.
Judge each promise as kept, partly kept or broken
Set the promise beside the evidence and judge it in one of three ways. Kept: the step delivers what was promised for nearly every customer, and the evidence shows no pattern of disappointment. Partly kept: it holds most of the time but fails under conditions customers cannot see, such as busy periods, bad weather or certain locations. Broken: it fails often, or it fails for a group of customers in a way the promise does not mention. Write one sentence on what the evidence shows for each judgement, so the decision can be checked later. Mark objective claims that are broken separately; they need the stricter treatment in the next step.
Decide whether to fix the step or change the claim
For each partly kept or broken promise, choose between fixing the experience and changing what is promised. Fix the step when the promise is why customers choose the business and the fix is affordable. Change the claim when the business cannot keep the promise reliably, or when keeping it would cost more than it is worth. Often the best answer is both: make the claim specific and conditional, and improve the step towards it. For an objective claim that is broken, correct or withdraw it in every place it runs and record the change in the claims library; do not simply soften the tone while the stated time, price or result stays wrong. For one common promise, the delivery promises guide shows what to do when a promise breaks: tell affected customers first, then update the promise for new orders.
Give each decision an owner and a date
Every decision needs one named owner and a date. A changed claim belongs to whoever owns the channel; a fixed step belongs to whoever runs it, often outside marketing. Write each decision in the promise register with what will change, who owns it, the date, and how the business will know it worked: fewer complaints tagged to that step, fewer returns for that reason, better reviews of that part of the experience. Where the gap affects whether customers stay, the measure might include the Churn RateShare of customers at the start of a period who left during it. of customers who went through the step.
Tell the teams who repeat the promise
A promise changed in the advert but not in the sales script, the confirmation email or the agents' saved repliesA pre-written answer a support agent inserts and then edits for the customer in front of them, keeping facts and tone consistent across the team. is still being made. List everyone who repeats each changed promise, including agencies, partners and support, and tell them what changed and why. Update the messaging house and the claims library so new work starts from the corrected wording. Brief support on what customers were told before and after the change, so agents can answer customers who bought under the old promise.
Put the check on the marketing calendar
Campaigns change promises faster than operations change delivery, as the foundations hub notes, so the check has to recur. Put a full check on the marketing calendar at a fixed interval, and add a short version to campaign planning: before a campaign launches, list its new promises and find where each is tested. At each full check, start by reviewing the last round's decisions: whether they were done and whether the evidence moved. The register becomes the record of what the business promises and how well it keeps it.
The promise register: a table
The register is a single table, kept where marketing and operations can both read it. The rows below show its columns with generic entries; each business fills it from its own promises and evidence.
| Promise (exact words or inferred) | Where it is made | Stated or inferred | Where it is tested | Evidence | Judgement | Decision | Owner and date |
|---|---|---|---|---|---|---|---|
| "Delivered next working day" | Product pages, checkout, adverts | Stated | Delivery | Delivery records, contacts tagged to late delivery | Partly kept: fails for orders after the cut-off | Show the cut-off beside the promise; fix the cut-off message at checkout | Web lead, next release |
| "Set up in minutes" | Homepage, onboarding email | Stated | First use | Support contacts at setup, cancellation reasons | Broken for one product range | Change the claim for that range; add a setup guide | Product marketing, this month |
| Personal attention (from "small family team") | About page, leaflets | Inferred | First support contact | Complaints about scripted replies | Partly kept | Review tone guidelines with support | Support lead, next quarter |
| Spotless result (from photographs) | Adverts, social posts | Inferred | Service visit | Reviews comparing result with images | Kept | No change; recheck at next cycle | Marketing lead |
| "No hidden fees" | Pricing page | Stated | First bill | Billing contacts, refunds | Broken: a booking fee appears at checkout | Correct the claim and show the fee upfront, through approvals | Pricing owner, immediately |
Two columns do most of the work. "Where it is tested" turns a slogan into a step someone can inspect, and "Owner and date" turns a finding into a change. The register also feeds the customer journey mapping framework: a promise that is broken at a step is a pain point the map should show, with the promise beside it.
A window cleaning company checks its promises (illustrative)
Gruvenda Window Cleaning finds the promise rain keeps breaking
Gruvenda Window Cleaning, an invented window cleaning company with 5 rounds and about 1,400 regular customers, lists the promises on its leaflets, website and booking emails. It finds 17, of which 6 are inferred, such as "you won't need to be home", implied by a leaflet photograph of a cleaner working at an empty house.
One stated promise stands out: "same day every month". Support contacts tagged to missed or moved cleans make up the largest reason, 46 of 132 contacts over a quarter, and almost all fall in weeks after rain, when rounds slip by one to three days. The team judges the promise partly kept: it holds in dry weeks and breaks whenever weather moves a round, which customers cannot see coming.
Fixing the step would mean cleaning in the rain, which the owner rules out. The team changes the claim instead. Leaflets and the website now promise "a clean in the same week each month, with a text the evening before", and a rain-day message tells customers on the affected round that their clean moves and the new day. The booking email and the agents' saved replies are updated the same week. Over the following quarter, contacts tagged to missed cleans fall from 46 to 14, and two reviews mention the evening-before text by name.
Common mistakes
- Checking only stated claims. Inferred promises, from images, tone and words like "easy", break just as often and are missing from any claims library.
- Collecting from one channel. The advert may be careful while the sales script or the confirmation email promises more. Collect from all of them.
- Judging without evidence. A promise judged kept because nobody remembers complaints has not been checked. Use contacts, returns, reviews and records.
- Softening the tone of a broken objective claim. A wrong time, price or result has to be corrected or withdrawn, through the approvals process, not reworded gently.
- Changing the claim in one place. A promise still made in a script, an email or a saved reply is still a promise.
- No owner outside marketing. Many fixes sit in operations. Without a named owner and a date there, the gap stays.
- A one-off project. Campaigns change promises constantly. The check belongs on the calendar.
- Making every promise modest. The aim is promises the business keeps, not promises nobody wants. Fix the steps that carry the promises customers chose you for.
