By Hassan, Technical Lead at Cellbot
Published: 20 February 2025 · Fully reviewed: 26 August 2026
Use the WhatsApp Business App when people can manage conversations manually and a standalone inbox is acceptable. Use the WhatsApp Business Platform when repair events must trigger approved templates, several people need an accountable workflow, or conversations must connect to customer and job records.
The channel is not automatically better than SMS, email, telephone or a customer portal. Choose it when the customer expects it, the shop can secure the data, and every automated path has a clear human escalation. Do not choose from unsupported open-rate or cost comparisons.
App or Platform?
WhatsApp describes the Business App and Business Platform as separate business services. Exact features, eligibility, pricing and availability can change, so check the current product pages before committing a workflow.
| Decision | Business App | Business Platform |
| Operating model | Staff handle conversations in the app | Software sends and receives through the business platform |
| Best fit | A small manual inbox with simple customer conversations | Event-driven updates, routing, templates and system integration |
| Business-initiated messages | Governed by WhatsApp policy and available app features | Require an approved Message Template |
| Customer reply | Staff reply in the app | Free-form replies are allowed within the platform's 24-hour customer-service window |
| Repair-system connection | Manual copying or separate records may be required | Can connect message events to customer and repair records |
| Control burden | Access, backup, handover and separate record keeping | Integration, template, webhook, access, delivery and failure controls |
| Cost model | Check current app terms | Meta and provider pricing can vary by message type, country and service |
Do not set an arbitrary “messages per day” threshold. Move to the Platform when the manual process cannot preserve ownership, consent, repair context and recovery reliably.
Download the WhatsApp repair-message control register. Use one row per event and template; do not treat a generic opt-in as permission for every future purpose.
Start with the business identity and customer expectation
WhatsApp's current Business Messaging Policy requires an accurate Business Profile with customer-support contact information. It says a business may contact a person only where the person has supplied the mobile number and the business has received opt-in permission for subsequent messages or calls. The business is responsible for lawful notices and permission.
At intake or booking, tell the customer:
- which shop and number will message;
- whether the route is for enquiry replies, repair updates, marketing or calls;
- the categories of message they are choosing;
- how to change channel or opt out; and
- where to find the privacy information.
Preserve the wording, action, time, source and purpose. Respect an opt-out made inside or outside WhatsApp. A telephone number in a repair record is not, by itself, evidence that every WhatsApp purpose was expected.
For UK businesses, the ICO distinguishes routine customer-service messages from direct marketing and explains when PECR consent or the products-and-services soft opt-in may apply to electronic mail. This article does not determine the lawful route for an individual shop; document the purpose and obtain appropriate advice.
Understand the Platform's 24-hour window and templates
Under the current WhatsApp Business Messaging Policy:
- a business using the Platform may initiate a conversation only with an approved Message Template;
- it may reply without a template within 24 hours of the user's last message; and
- outside that customer-service window, it may send only approved templates.
A live customer conversation does not make every message unrestricted. The message still needs the expected purpose, appropriate data and current policy fit. WhatsApp can approve, pause or reject templates and can limit service following negative feedback or policy breaches.
Treat these as separate states in the message engine:
- user initiated and service window open;
- business initiated with an approved template for the designated purpose;
- outside the window without an eligible approved template;
- customer opted out or blocked;
- number, connection or delivery failed; and
- human review required.
Fail closed on states 3 to 6. Do not silently send through a different channel unless the customer expectation and fallback rule support it.
Map repair events to controlled messages
| Repair event | Useful content | Approval or reply needed | Stop or escalation state |
| New customer enquiry | Acknowledge, ask only qualifying questions, name human route | Customer initiated; service window applies | Unsupported job, safety issue or complex diagnosis |
| Booking confirmed | Location, date, preparation and change route | Business-initiated Platform message needs the appropriate approved template | Wrong location, duplicate or no permission |
| Device received | Receipt reference, recorded accessories and next decision | No marketing content mixed in | Intake mismatch or disputed condition |
| Diagnosis ready | Evidence summary, price, scope, timing and approval action | Explicit customer decision before extra work | Ambiguous device, price or risk |
| Material delay | What changed, revised next-contact time and options | Human owner for disputed or high-impact change | Repeated delay or complaint |
| Ready for collection | Location, opening information, amount or payment route as appropriate | Release remains subject to shop controls | Failed quality check or unpaid/disputed state |
| Aftercare | Warranty or problem route | Separate review or promotional purpose where used | Open rework, complaint or opt-out |
| Promotion | Clear relevant offer and identity | Current marketing permission and approved category/template | Opt-out, complaint or frequency cap |
The customer communications guide owns cross-channel purpose and wording. The automation control loop covers event, eligibility, action, evidence and rollback design.
Keep the message useful and minimal
A repair message should answer:
- which shop is speaking;
- which repair or booking it concerns without exposing unnecessary detail;
- what changed or is known;
- what the customer needs to do;
- when the next update will happen; and
- how to reach a person.
Avoid copying the whole repair record into the thread. Use a repair reference rather than a device serial number where possible. Do not request a full payment-card number, financial account number, identity-document number or another sensitive identifier in chat; WhatsApp's policy explicitly prohibits asking people to share several of these categories.
Photos can help document visible damage, but they can also contain faces, notifications, locations, other devices or account information. Ask only when the image has a defined purpose. Restrict access, retention and onward sharing, and give another route where appropriate.
The ICO's data-protection principles require purpose limitation, data minimisation, storage limitation and appropriate security. Connect the conversation to the repair-shop CRM record without creating uncontrolled exports or staff copies.
Design human escalation before automation
WhatsApp's policy permits automation within the customer-service window but requires prompt, clear and direct escalation paths. It lists options including an in-chat human transfer, telephone, email, web support, in-store visit or support form.
Escalate when:
- device identity or fault is ambiguous;
- price, scope or timing materially changes;
- the customer disputes condition, consent or payment;
- a safety, data-loss or security risk appears;
- template variables are incomplete or contradictory;
- sentiment indicates a complaint but the facts are not known;
- the customer requests a person; or
- automation repeats or cannot progress.
Do not make the customer restate the whole case. Transfer the permitted conversation context, current repair state and unanswered decision to the accountable person.
Build templates from facts, not persuasion
Each Platform template should have:
- one declared purpose and message category;
- a named trigger and neutral eligibility rule;
- required variables with validation;
- a preview with example values;
- an approved language and version;
- a human owner;
- delivery, reply, opt-out and error handling;
- frequency and duplicate controls; and
- a retirement date or review event.
Do not place optional promotional copy inside a necessary repair update. It can change customer expectation, legal analysis and template classification. Keep service, review and marketing flows distinct.
For a neutral post-completion reputation route, use the review strategy and automated review controls. Neither page makes a WhatsApp message permissible by itself.
Test before connecting live customers
Use test contacts and synthetic repairs to verify:
- correct shop name and number;
- correct customer, location and repair mapping;
- service-window calculation;
- approved template and language selection;
- missing and unsafe variable rejection;
- inbound reply correlation;
- opt-out and block suppression;
- delivery, failure and retry states;
- fallback behaviour; and
- human handover with context.
Then run a bounded live cohort with accountable monitoring. Pause on wrong-recipient, wrong-location, duplicate, permission, sensitive-data or widespread delivery failures.
The software buyer test should include export, access and failure scenarios, not only a successful demonstration.
Measure conversation quality without open-rate folklore
Track events the system can actually observe:
Eligible message | Trigger and all permission, policy and record checks passed
Queued | Message accepted by the shop workflow for dispatch
Provider accepted | Provider returned an accepted identifier or state
Delivered | Delivery state was reported where available
Replied | Customer response correlated to the conversation
Human escalated | Named rule or customer request transferred ownership
Resolved | Repair decision or service question reached a defined outcome
Opted out or blocked | Further applicable messages suppressed
Failed | Permanent or exhausted failure recorded with reason
Do not call “sent” delivered or read. A read receipt may be unavailable. Do not treat a reply as a booking or completed repair. Reconcile outcomes through the repair-shop KPI guide.
A 30-day setup plan
Days 1 to 7: map purpose and permission
List current WhatsApp uses, who sends, which numbers are used, where conversations are recorded and how opt-outs work. Stop unowned broadcasts and shared credentials.
Days 8 to 14: choose App or Platform
Use the App where a controlled manual inbox is sufficient. Choose the Platform only when system integration, templates and routing solve a documented failure. Check current WhatsApp product, policy and pricing pages.
Days 15 to 21: configure and test
Complete the register, create the minimum templates, validate variables and run synthetic success and failure cases. Train the human escalation owners.
Days 22 to 30: pilot and review
Release one or two high-value service messages to a bounded cohort. Reconcile delivery, replies, opt-outs, complaints, escalations and repair outcomes. Expand only when the evidence and recovery path hold.
How Cellbot fits
Cellbot's WhatsApp workspace is available from the Pro plan, subject to Meta connection and template approval. It can connect approved messages, customer replies, opt-in records and repair context; exact plan features and limits are on the Cellbot pricing page.
Cellbot cannot approve a WhatsApp account or template, decide the lawful communication route or guarantee delivery. It also publishes this guide and has a commercial interest. Verify the live WhatsApp policy, ICO guidance, connection state and message evidence before relying on automation.
WhatsApp FAQs for repair shops
Is the WhatsApp Business App enough for a repair shop?
Yes, when staff can manage a standalone manual inbox and preserve customer and repair records reliably. Use the Platform when event-driven templates, routing and accountable system integration solve a real operating need.
Can a repair shop send a WhatsApp message first?
On the Business Platform, business-initiated conversations require an approved Message Template. WhatsApp also requires the customer's number and opt-in permission for subsequent messages or calls. Check the live policy and applicable law.
What is the 24-hour WhatsApp customer-service window?
The current policy allows a Platform business to reply without a Message Template within 24 hours of the user's last message. Outside it, only approved templates may be used. Other policy and legal requirements still apply.
Can WhatsApp be used for repair status updates?
Yes, where the customer expects the channel, the message uses the appropriate Platform route or App feature, the content is necessary and secure, and failures have a human recovery path.
Should customers send device passcodes through WhatsApp?
Do not request passcodes by default. Establish whether access is necessary, offer a safer handover route where practical and apply data-minimisation, access and retention controls.
Is WhatsApp marketing the same as a repair update?
No. A necessary update about an existing repair and a promotion have different purposes and may have different template, consent and PECR implications. Keep them separate in copy, records and suppression rules.
Are WhatsApp messages free?
Do not assume so. App, Platform, country, message type and provider charges can differ and change. Check current Meta and provider pricing before setting a budget.
Sources, search evidence and update note
This guide was fully rebuilt on 26 August 2026. It removes unsupported usage, open-rate, response-time, cost, setup-time and automation claims plus obsolete pricing detail and fabricated results. The replacement is a policy-first App-versus-Platform decision and message-control system.
DataForSEO returned no stored UK volume row for the submitted repair-specific WhatsApp phrases. The live desktop result for WhatsApp Business for phone repair shops contained an AI Overview and was led by a general local-service Platform guide; RO App and an AI-agent page followed, while Cellbot was absent. Exa surfaced WhatsApp's current Business Messaging Policy as the strongest primary reference and was used for semantic discovery, not rank evidence.
Primary references:
- WhatsApp: Business Messaging Policy, checked 26 August 2026
- WhatsApp: Business Platform features, checked 26 August 2026
- ICO: direct marketing using electronic mail, checked 26 August 2026
- ICO: data-protection principles, checked 26 August 2026
Continue with the customer communications playbook, automation control loop or repair customer-experience blueprint.
