What sales promised that operations has to deliver
Talk to anyone who handles complaints in a trades business and the same pattern appears: the customer is not usually angry about the work, they are angry that it was not what they were told. And the thing they were told was almost never a lie. It was a reasonable sentence said in a ninety-minute conversation that never reached the crew, because the paperwork carried the scope and the price and none of the promises. The handoff is the point where a sale becomes a job, and it loses everything that was not written down.
What gets lost, and it is always the same category
The quote travels perfectly. Dimensions, materials, the price, the start date: all of it is structured, all of it is in a system, all of it arrives. What does not travel is the set of small commitments that made the customer say yes.
That the crew would work around the dog. That they would not park across the neighbour's drive because there is already a dispute. That the customer works nights and cannot have noise before ten. That the old material would go rather than sitting in the garden for a week. That someone would text before arriving because the customer has a baby who sleeps at eleven.
None of these are in the quote and every one of them is a promise. When one is broken the customer does not experience an administrative gap, they experience being lied to, and the rep who made the promise in good faith gets the reputation.
The reason it happens is structural rather than careless. The rep is the only person who heard those sentences, the CRM has no field for them, and by the time the crew is on site the rep is four appointments away and cannot remember them either.
Why this is a sales problem rather than an operations one
It is tempting to file this under scheduling, but the promises are made in the appointment and the appointment is where they can be captured. An operations team cannot honour a commitment it was never told about.
It also loops back into the sale. Reps who have been burned by this start under-promising, which is a rational defence and it costs them jobs, because the small accommodations are frequently what closes an appointment where the price is competitive. The answer is not fewer promises, it is promises that survive.
And it is the largest single source of the thing that determines a trades business's growth, which is whether a finished job produces a recommendation. A technically perfect installation that broke three small promises does not get recommended.
Making the handoff carry the promises
- Write the promises down separately from the scope
- They are a different kind of information and they get lost inside a specification. A short list attached to the job, in plain sentences: text before arriving, park on the road not the drive, dog in the kitchen, no noise before ten.
- Say them back to the customer before you leave
- "So to be clear on the bits that are not on the quote: we text before we come, we park on the road, and the old material goes the same day." Ten seconds, and it does two things. It confirms you have them right, and it tells the customer these were heard rather than nodded at.
- Name what you cannot promise
- This is the half reps skip. If you do not control the crew's arrival window, say so rather than agreeing to a time you hope will hold. "I cannot promise a morning start, what I can promise is a text the night before" is a smaller commitment that will actually be kept.
- Hand over to a person, not to a system
- Where you can, tell the crew lead directly, or make sure someone does. A note in a field that nobody reads is the same as no note. If the business has no route from the rep to the crew, that is the thing to fix and it is module 11's problem.
- Close the loop after day one
- One message on the first evening. "Did they text before they came?" You find out immediately whether the handoff worked, and the customer sees that the promises were real.
What it sounds like
Day one of an installation. The customer had been told the crew would text before arriving and would park on the road.
What to notice. The work has not started and the relationship is already damaged, over parking. Notice the customer's own line: "it is not the end of the world, it is just, you did say." That is the entire mechanism. The size of the promise is irrelevant; what matters is that one was made and not kept. The rep handles it well, and the cost is that this job now needs managing where it did not before.
The mistake: assuming the quote is the handoff
The quote is a specification and it does its job well. Reps treat it as the complete record of the sale because it is the only artefact that formally travels, and everything not in it quietly becomes something the customer was told and nobody knows about.
The second mistake is promising to be personally present. "I will be there on the first morning" is said constantly and kept rarely, because by then the rep has four more appointments and one of them overruns. It is a promise that generates a specific kind of disappointment, because the customer was relying on continuity of person, and the person is who they trusted.
The third is agreeing to things you do not control, which is nearly always about timing. A rep who does not schedule crews should not be committing to a start time, and the honest alternative, a smaller promise that holds, closes almost as well.
And the last one is going quiet after the sale. The gap between signing and starting is where confidence decays, and it is where cancellations happen. A rep who disappears the moment the paperwork is signed has confirmed the customer's suspicion that the attentiveness was part of the pitch.
Before you hand the job over
- What did I promise that is not on the quote?
- Is that written down somewhere separate from the scope?
- Did I say those promises back to the customer before leaving?
- Did I agree to anything I do not personally control?
- Did I promise to be there myself, and will I be?
- Does the crew lead know, from a person rather than from a field?
- Am I going to check on the first evening?
Read next
- When it is not as bad as they think The other place trust is built or lost, and by the same mechanism.
Is this not just the office's job?
The office can only pass on what it was told, and the promises were made in a room where nobody from the office was present. Capturing them is the rep's, and only the rep's, because they are the only person who heard them.
What if there is no system for this at the company?
Then a note to yourself and a direct word with the crew lead is better than nothing, and the absence is worth raising. Businesses tend to treat this as unavoidable friction, and it is usually one short list attached to a job away from being solved. Module 11.1 covers the version of this an owner can fix.
Should I promise less to avoid this?
No, promise the same and capture it. Under-promising loses jobs, because the small accommodations are frequently what wins an appointment where the price is close. The failure is in transmission, not in generosity.
How much does a broken small promise actually cost?
More than its size suggests, because the customer does not scale their reaction to the importance of the thing. It is read as a signal about whether what you said can be relied on, which then colours everything else including work they cannot themselves assess.