A customer reads your revised estimate and replies “thanks.” That tells the garage the message reached them, not whether they approved the additional work or understood the new total.
For WhatsApp car repair quotes, keep the current estimate and the customer's decision together. When scope changes, explain the difference, name the version awaiting approval and hold the additional work until the decision is clear.
Keep the earlier agreement visible
Imagine an adult customer has approved a hypothetical estimate A for an oil service at £120, including tax. During the visit, the garage identifies a separate repair to propose. This example concerns communication, not a recommendation about mechanical work.
Do not silently replace estimate A. Keep its scope and amount visible, then create estimate B explaining what remains, what changes and what is excluded. A customer comparing messages should not need to calculate the revised total themselves.
The practical issue for workshop teams is knowing which work already has permission and which work is still waiting. A newer document alone does not answer that question.
Send a revision someone can actually decide on
Here is a hypothetical message, with illustrative amounts rather than recommended prices:
“Estimate B replaces estimate A for this visit. The oil service remains £120. The proposed additional repair is £180. The revised total is £300 including tax. No other work is included. The additional repair is on hold. Please confirm whether you approve estimate B at £300, want only the previously approved oil service, or would like us to explain the change.”
Before sending, check those words against the actual scope, charges and shop policy. If the original work cannot proceed independently, explain that instead of offering an unavailable choice. State any changed collection expectation without promising an unconfirmed completion time.
Put the important terms in text even when you also discuss them by phone. Clear WhatsApp communication should let the customer revisit the same proposal without replaying a voice note.
Match the response to the next action
Use this decision table for the hypothetical revision. It separates message activity from permission to proceed.
| Customer response | Record | Next action |
|---|---|---|
| Message marked read | Estimate B seen | Keep additional work on hold |
| “Thanks” | Acknowledgement only | Ask which option they choose |
| “Approve estimate B at £300” | Explicit decision on B | Check scope matches before release |
| “Only the oil service” | Additional repair declined | Confirm original work remains feasible |
| “Why is it needed?” | Explanation requested | Answer before asking again |
Avoid interpreting a thumbs up in isolation. Ask a short clarification tied to the version and total. That is less awkward than discovering later that the customer meant “I have seen it.”
The Business app features page describes quick replies and labels. These can help organize the exchange; neither replaces the customer's actual decision.
Leave a record the next advisor can use
Record the estimate reference, version, scope, exclusions, total, customer response, response time and responsible advisor. Distinguish “awaiting decision” from “approved” rather than leaving a vague “customer contacted” note.
Keep the original message alongside your summary. If approval happens by telephone, record who spoke, which version and total were discussed, and what was agreed; send a written recap and resolve any discrepancy before additional work starts.
DripTell can support this handoff through shared inbox assignment and notes and contacts and lead stages. Conversation history is not an immutable audit log, and any connection to garage software needs separate confirmation.
At handover, ask the receiving advisor to identify the approved version and outstanding question. If they cannot, improve the note before moving the conversation. Never make the customer reconstruct the garage's internal discussion.
Follow up without muddying the decision
A reminder should refer to the pending revision, not sound like a collection notice for work that has not been authorized. Offer an explanation or a conversation with an advisor.
Configure follow up automation to pause or end when a customer or teammate replies, and test that behavior. Do not assume every reply means approval. Under the WhatsApp Business Messaging Policy, subsequent contact requires opt-in, and requests to stop must be respected.
Frequently Asked Questions
Does a read receipt count as approval?
No. It indicates message activity, not an explicit decision about scope and price. Keep the additional work on hold and ask the customer to choose.
What if the customer approves only part?
Restate the accepted work and its total. Confirm that this smaller scope is workable under the shop's actual policy before proceeding. Do not attach the refused work to that approval.
What if the estimate changes again?
Create another clearly identified revision. Explain the new difference and ask for a decision on that version. Earlier approval should not silently become permission for newly added work.
Want help applying this guide?Ask the DripTell team
From reading to action
Want help applying this to your business?
Share your details. We will read the article you are on and start with a useful answer for your team.
DripTell Editorial
Practical guidance reviewed by the DripTell product and customer workflow team.
See how DripTell checks product claims, uses primary sources and handles corrections.
Editorial and source policy
