How do I stop AI customer service replies quoting old prices?

Last week I sat in front of twelve customer service replies on one screen. An AI agent had drafted every one. A counter at the top read 0 of 12 approved, and nothing could leave that page until a human changed the number.

The replies themselves took an hour. The part around them took the rest of the build.

What sits around the replies?

Every fee the agent is allowed to mention (late cancellation, no-show, account pause) lives in one settings file, and the reply text only holds a placeholder for it.

The owner reviewing the drafts can rewrite any sentence she wants. If she types a dollar amount in by hand, the page warns her that she just created a second copy of a fee, which is the exact thing the system exists to prevent. She can approve anyway. The warning is there to inform her, and nothing locks. No reply sends until she sends it.

In effect, I built a page whose main job is to stop a business owner from typing a dollar sign.

How should AI customer replies be structured?

If you let AI talk to your customers, split what it says into three layers before you write a single reply.

• Facts that change over time (prices, fees, policies, notice periods) live in one file the AI reads.
• Details that change per customer (first name, appointment date) are fill-in slots.
• The wording in between is the only thing a human edits.

The approval step exists to keep those layers from bleeding into each other. The person editing the wording should never also be responsible for remembering the current fee.

Can you build this without a developer?

Yes. Take your ten most common customer emails and write one reply for each. Go back through and circle every number and every policy. Those come out of the replies and go into a single reference document, and the reply keeps a placeholder like {{LATE CANCEL FEE}}. Per-customer details get a slot like [FIRST NAME].

Then hand the drafts to whoever owns the customer relationship with two choices per reply: approve as written, or edit and approve their version. That is the whole system.

Why does one price file matter?

The typical failure with AI customer service is a polite, correct-sounding reply that carries last year's price. The reply reads well, so nobody checks it, and the customer receives a number you changed months ago.

Prices change. Prices typed into templates stay frozen at whatever they were the day someone typed them. Put the number in one place and the agent can never be more out of date than your settings file. When a fee changes, you update one line, and every future reply picks it up.

Do this today

1. Open the last five customer emails your team sent.
2. Count how many contain a price, a fee, or a policy typed by hand.
3. Treat that count as the number of places your business currently has to remember to update.
4. Move those numbers into one reference file and replace them in your templates with placeholders. One file replaces all of them.