This week I made three real bookings on a Fairfax Islamic-wellness clinic's system, then opened the inbox and read every message that came back. That is how I found the sentence. The automated customer emails going out after every booking told the client: "Your appointment is booked and paid for."
No payment is collected anywhere in that booking flow. Not a card field, not a deposit, nothing. The sentence was false for every single client who had booked since the system went live.
The sentence nobody had read in months
What makes this worth writing about is that the rest of the email was good. The client's first name filled in correctly. The date and time were right and different on each booking. The address, the parking note, the what-to-bring list and the fasting guidance all matched what the clinic actually tells people. The reschedule link worked, and it was the right link for that specific booking. There were no broken placeholders anywhere.
Everything was correct except the one line about money — and that line ran all the way through the cancellation paragraph too. Cancel late and the message told you "the payment isn't refunded." Cancel early and it promised "you are refunded in full." A refund of money the clinic had never taken.
Why did the email say something untrue?
Not because anyone lied, and not because the writing was sloppy. The message was accurate when it was written. At that point the plan was for clients to pay in full at the moment of booking, so the wording described the plan exactly.
Then the plan changed. Payment moved to the session itself, and later to a deposit-plus-balance model. The booking form changed. The calendar changed. The prices changed.
The email did not change, because an automated message has no owner once it is switched on. It just keeps sending. This is the quiet failure mode of business automation: you update the process and forget the paperwork that describes it.
What to check in your own automated customer emails
You almost certainly have some — a booking confirmation, a receipt, an abandoned-cart nudge, a reminder. Here is the check I would run.
Make a real booking and read the mail as a customer
Not a preview, not the template in the editor. Go through your own flow the way a stranger would, then open your inbox and read what arrives. Every one of the problems above was invisible in the builder and obvious in Gmail.
Read every sentence about money out loud
Money claims are the expensive ones. Anything that says paid, charged, refunded, deposit, free or included is a promise a customer can hold you to. A message telling someone they were refunded creates an expectation of a refund, whether or not you ever took the money.
Re-read the whole set after you change how you sell
Price change, new deposit, new booking form, new cancellation window — each of those quietly turns a paragraph of your automated customer emails into fiction. Put the re-read in the same job as the change, not on a list for later.
The two honest ways out
When something you are sending is untrue, there are only two exits: make it true, or change the words. The clinic picked the first — a deposit-plus-balance model and a finalized cancellation matrix are decided and built into every calendar, deposit collection tested end to end. It is deliberately still switched to test mode while that gets confirmed, so no client is charged by accident. The confirmation email hasn't been rewritten yet, which means the sentence stays false until the switch flips — a known, tracked gap, not a forgotten one.
The wrong exit is the tempting one: leave it indefinitely, because nobody has complained yet. Nobody complains about being told they already paid. They complain later, when they cancel and ask for the refund your email promised them.
Your automation is a member of staff who speaks to every customer and never gets reviewed. Book something on your own system this week and read what it says back.