What customer expectation caused you the most problems?

Question

One expectation I wish I had defined earlier was arrival times.

When I first started, it was easy to tell a customer:

“I’ll be there around 10.”

Or:

“We should be there between 12 and 1.”

At the beginning, that felt like good customer service.

The schedule was smaller.
The routes were lighter.
I had more control over the day.

As the business grew, specific arrival times became harder to keep.

All it took was:

one chatty customer talking for 10 minutes
a locked gate
a dog outside
extra waste in a yard
traffic
road construction
an accident
a customer note that needed attention

Suddenly the whole route was pushed back.

And once you miss the arrival time you gave the customer, even if the work itself is done well, you’ve created frustration because the expectation was set wrong from the beginning.

That forced us to change how we communicate scheduling.

Now we set the expectation that we scoop from sunrise to sunset.

Customers know their service will happen on their scheduled day, and they’ll receive an “on the way” message 30–60 minutes before arrival.

That one change reduced a lot of unnecessary pressure.

It also made the route easier to manage because we weren’t trying to force the day into exact arrival windows that didn’t hold up once real life happened.

I think a lot of service businesses run into this.

You create an expectation early because it feels manageable, then growth exposes how hard it is to keep that promise consistently.

For us, the lesson was pretty simple:

If the business cannot deliver it consistently at scale, be careful promising it casually in the beginning.

What expectation did you set early on that later became hard to manage as the business grew?

brand · Answer

Great question and one that always seems to be learned the hard way. Contract verbage that is descriptive but also gives allowances for us to avoid contreversy. Replacing a 10 ft. board turns into a customer wanting money off if we ended up installing 9 feet of it. terms like "up to" or "as needed up to" helps back-end discounts from being a thing.

Legal terms in contracts to avoid people that work the system against you is huge if you have have ever experienced it.

Just last week I corrected a homeowner who told me that he wanted the remaining material from his roof replacement. I explained that he paid for a new roofing system, not a surplus of materials. I buy extra so I'm not short and return what is returnable. Educating clients on the front end is best while managing expectations throughout the project, however, some people just want a deal however they can get it *smh

anthonysalazar · Answer

This is a solid point.A lot of customer expectation problems come from wording that feels clear to us, but leaves too much room for interpretation by the customer.I’ve had to learn this in my own business too.If the scope is vague, the customer will often define the scope for you after the work is already done.That creates problems fast.Your roofing material example makes a lot of sense.The customer hears “materials for my roof” and thinks anything left over belongs to them.You know the extra material was purchased to make sure the job could be completed properly without delays, and anything returnable gets returned as part of managing the project correctly.That’s the kind of thing that feels obvious to the contractor, but it may not be obvious to the homeowner unless it’s explained upfront.I think this is where wording matters a lot.Terms like:“up to”“as needed”“as required to complete the scope”“remaining materials may be returned”“service includes X, does not include Y”“access must be available at time of service”&nbsp;Those details can prevent a lot of awkward conversations later.In my business, we’ve had to do this with things like:arrival windowsweather policieslocked gatesaggressive dogswhat counts as serviceable wastewhat happens if a yard is inaccessiblewhat’s included in a standard visit&nbsp;I used to think some of that was overkill. Then you deal with enough misunderstandings and realize clear terms protect both sides.The customer knows what to expect.The business has something to point back to when someone tries to reinterpret the agreement after the fact.I also agree that educating the client upfront is better than trying to defend yourself later.Once someone feels like they were promised something, it’s much harder to walk that back.Clear expectations before the work starts make everything smoother.

Forum Discussion

What customer expectation caused you the most problems?

2 Replies