Car wash customer notifications: telling people their car is ready

A customer who does not know how long the wait is will ask. They ask at the bay, by phone, or by walking back every ten minutes — and each time, the work stops to answer. The interesting part is that the customer is not being difficult: they simply have no way of knowing. Customer notification is the part of car wash software that fixes an information problem, and it is worth evaluating separately, because the channels differ enormously in cost, reach and whether the customer has to install anything.

Four channels, and what each really costs

"Notifies the customer" can mean any of these. They are not interchangeable.

• A message you send — WhatsApp or SMS, one tap from the job. Reaches everyone with a phone, arrives reliably, and is the only channel most customers already expect. SMS may cost money per message depending on your country and operator.
• A tracking page behind a QR code — the customer scans a code, a page opens on their own phone showing status and estimated time. Nothing to install, no sign-up, no cost per car. It is a pull channel: the customer looks when they want to.
• A wallet card — on iPhone, the customer adds a pass to Apple Wallet from that page. When the status changes, the card updates and the phone shows a notice on the lock screen. No app, no message fee.
• A browser notification — where the browser supports it, the customer allows notifications once and the "ready" message arrives as a push. Again free per message; support varies by browser and by how the page was opened.

The practical answer is usually a combination: a free channel by default, and a message for the customer who did not scan anything.

What to ask before you rely on a notification feature

1. Does the customer have to install an app?

This is the question that decides whether the feature is ever used. A customer who washes their car once a month will not download a car wash app. Any system whose customer-facing side requires an installation will, in practice, fall back to phone calls.

2. Who pays per message?

SMS is usually billed per message. Over a year, at a wash doing forty cars a day, that is not a rounding error. Ask which channels are free and whether the free ones are the default.

3. What does the customer actually see?

A tracking link should show the status and the estimated time — and not the price, not other customers' vehicles, not your internal notes. Check this on the live page rather than in the sales deck.

4. What happens when the wash has no connection?

Notifications leave the building, so they need the line. A well-built system still lets you finish and hand over the job offline and sends the notice when the connection returns. What it must not do is block the handover because it could not send a message.

5. Does the notification link to a job or to a person?

If a customer has to give a phone number before you can tell them anything, intake slows down and some customers refuse. A code attached to the job asks for nothing.

How WashPro handles this

• A QR code created with the job. The customer scans it and follows their own vehicle: position in the queue, current status and estimated handover time. No app, no account, no phone number required.
• Apple Wallet card. From that page an iPhone customer can add a pass. When the car moves to ready, the pass updates and the phone shows it — with no message fee.
• Browser push where supported. Instead of the pass, the customer can allow notifications in the browser and receive the "ready" notice the same way.
• WhatsApp or SMS in one tap. For the customer who scanned nothing, the message is prepared from the job and sent from your own phone number.
• Amounts stay private. The customer's tracking view and the television board in the waiting area show plate, status and time — not money.
• Offline does not block the work. Intake, queue and handover run on the device with the line down; the customer is informed when the connection is back.

The honest limits

• The wallet card is an Apple feature. Android customers use the browser notification or a message instead.
• Browser notifications depend on the browser. Support and the way the customer opened the page both matter; treat it as a bonus channel rather than the only one.
• Live tracking needs both sides online. The page is served from the cloud; a customer in a basement car park will see it when they have signal.
• Nothing is sent unless the status is moved. If the job is not marked ready, no channel fires. The board and the notification are the same record.

Who benefits most

Washes with a waiting area and a peak hour, where the same question is asked twenty times a day. Also anyone whose customers leave the car and go elsewhere — a shopping centre wash, a valet arrangement, a mobile service — because there the customer genuinely cannot see the car and the alternative is a phone call each time.