WhatsApp Business Automation for Service
Appointment reminders, job status and customer questions run through the channel your customers already have open. What you are allowed to send there depends on the 24-hour window – free wording inside it, approved templates only afterwards. We build the flow so that it knows that rule.
The channel is open, the time window is not
Customers write on WhatsApp because the app is already open. The message then lands on a work phone lying in the workshop, gets answered when somebody has a moment, and leaves no trace in any system. A service phone is a device, not a channel: no ownership, no status, no record of who promised what.
The real difficulty sits elsewhere. WhatsApp is not email: Meta distinguishes two states. For 24 hours after the customer's last message you may write freely – text, photos, follow-up questions. After that only a message gets through that was submitted and approved as a template beforehand, in the right category, and for anything promotional only with consent. Every automated message therefore sits on a deadline that your process does not set – the customer's behaviour does.
So the work is not connecting WhatsApp. The work is deciding, for every message in your process, which state it will be in when it is sent, and building templates for the cases that fall outside the window and still have to survive review. On top of that, incoming replies have to arrive somewhere: in the CRM or the help desk, not in an app on one device.
Which messages are worth automating
We start with the flow that is triggered most often and has the clearest template. Further flows later share the same connection and the same consent logic.
Appointment reminders and confirmations
The most common starting point: appointment confirmed, reminder the day before, cancellation by reply. Both are templates, because they go out without the customer prompting them.
Job and delivery status
Order accepted, goods on the way, spare part arrived – triggered by the shop, ERP or stock system instead of by hand.
Questions inside the open window
Once the customer replies, free wording applies for 24 hours. That is exactly where the automation answers standard questions from your systems.
Capturing a request instead of going back and forth
Photo of the fault, job number, preferred date – asked for in a structured way and filed as a record in the CRM, with the images on the right entry.
Handover to a person
Complaints, pricing questions and anything emotional go to the service team with the full thread – inside the open window, so no template is needed.
Following up after the job
One message after completion, a review request for example: technically a template, sensible only with consent and a frequency cap.
A thread with the 24-hour window
Two days from a service job. Green means it goes out as it stands. Once the window has expired, only what is approved as a template gets through.
-
Customerwindow opened
Good morning, when is the engineer coming to look at the boiler?
-
Automatedfree wording
Good morning, Ms Albers. Job 4482 is booked for Wednesday between 8 and 10. Does that still suit you?
-
Customerto the service team
Yes. What does it cost if the pump has to be replaced?
-
Service teamfree wording
The engineer will check the pump on site and quote you the price before replacing anything.
- Window expired · Tue 09:21
-
Planned · free textnot deliverable
Your spare part has arrived, we could come tomorrow.
-
Templatedelivered
Hello {{1}}, the spare part for job {{2}} has arrived. Reply 1 for Wednesday or 2 for Thursday.
spare_part_arrived · utility category · approved -
Customerwindow open again
2
-
Template · promotionalblocked
Our spring offer on boiler servicing: book your slot now.
spring_service_offer · marketing category · no consent on record
Tuesday 14:05 is the line that matters: the same information does not arrive as free text and does arrive as an approved template. Notice that only in production and you have lost a message without knowing why.
The window hangs on the last customer contact, not on your schedule: every incoming message restarts the 24 hours. That is why we decide up front, for each planned message, whether it needs a template.
From verification to day-to-day operation
-
Sort out and verify the sender
Business verification with Meta, display name and number – through a provider such as 360dialog or Twilio, or directly on Meta's Cloud API. Without this step no automated message leaves the building.
-
Sort the messages
Every planned message is classified: free reply inside the open window, utility template or marketing template. That determines what needs approval and what needs consent.
-
Submit templates, build triggers
Templates go to Meta for review with their placeholders. In parallel the triggers are built in n8n: a calendar appointment, a job status, a shipping event or a field in the CRM.
-
Handle what comes back
Replies open the window, are attached to the right record and trigger standard answers. Anything ambiguous goes to a named person together with the full thread.
-
Make the running system safe
Delivery status, rejected templates and the quality rating of your number land on one overview. An objection takes effect immediately and is recorded.
What changes day to day
Today
- A work phone sits in the workshop and nobody owns it
- Messages are answered in the evening, or not at all
- Whatever was agreed on WhatsApp is in no system at all
- Planned messages fail to arrive for no visible reason
- Promotional messages without consent put the number at risk
With an automated channel
- Every incoming message becomes a record with an owner
- Standard questions are answered at once, the rest is assigned
- The thread sits on the customer record for everyone to read
- If a message falls outside the window, the template takes over
- Consent is documented and an objection takes effect instantly
What the channel does not allow – and what we will not build
WhatsApp belongs to Meta, not to you. We clarify these four points before quoting, because they decide whether the project is worth doing at all:
- Meta makes the rules. Templates are reviewed and can be rejected, usually because a utility template reads as promotional. If categories, prices or quality rules change, your effort changes without us having done anything differently. We build the flow so that the wording and category of a template stay exchangeable – the dependency itself does not go away.
- If your customers do not write on WhatsApp, this channel solves nothing. With mainly business recipients, in heavily regulated sectors, or where people phone anyway, email and SMS are the more honest answer and considerably cheaper, because every template message costs money. If we see it that way, we say so in the intro call and build something else instead.
- We do not let a freely improvising AI talk to your customers. What the automation answers comes from your systems and your wording; everything else goes to a person. That is more restrained than a chatbot with an opinion on every question – in exchange, nothing appears on WhatsApp in your name that you cannot stand behind.
- An open WhatsApp channel creates expectations. People who write there expect a reply within minutes, including on a Saturday. Opening hours and waiting times can be communicated cleanly, but nothing replaces the person who works through the open threads on Monday morning. Without defined ownership and response times the channel becomes a second inbox to neglect – that is an organisational question, not a technical one.
Fits your systems
Scope and price
The entry price covers one message flow with your templates, the triggers and the record in your CRM. Meta bills the message fees directly to you.
- Connection to the official WhatsApp Business API via your provider
- Support with business verification, display name and number migration
- One message flow with up to five templates, submitted and signed off
- Triggers from your calendar, shop, ERP or CRM
- Incoming messages as a record in your CRM or help desk
- Consent, objection and logging, plus the data processing agreement
- Documentation, handover session and 30 days of support
What increases the price
- Several flows with their own templates and triggers
- Two-way dialogue with answers from your knowledge base
- Connection to an industry system without a ready interface
- Templates in several languages for several countries
- Handover to a help desk with shifts and response times
Several flows with two-way dialogue and a connection to a stock system typically land in the range of our Workflow Advanced package from €2,490. We quote the binding fixed price after the intro call.
All prices excl. VAT · Meta message fees by usage · operation optionally via a support package
What you get
-
Production message flow
From trigger through approved template to the record in your CRM, signed off with test messages
-
Approved templates with categories
Wording, placeholders and classification as utility or marketing – documented and changeable later
-
Consent and objection logic
Where consent is captured, where it is stored and what happens the moment somebody objects
-
Handover and an operating view
Who answers inside the open window, what to do about a rejected template and how to read the quality rating
Frequently asked questions about WhatsApp Business
These solutions fit alongside
Automated Appointment Reminders
The same trigger over email and SMS – for every customer who is not on WhatsApp.
AI Chatbot for Customer Support
The same answering logic on your website, where no template has to be approved.
E-Commerce Automation
Where the order and shipping statuses come from that go out as templates.
AI Phone Assistant
The channel next door: taking and recording calls outside opening hours.
Are your customers already writing without getting an answer?
In the free intro call we go through your messages and sort out which ones fall inside the open window and which ones need a template. Afterwards you know how many templates you actually need – and whether WhatsApp is the right channel for your customers at all.
Book a free intro callWhere WhatsApp Business automation creates value in everyday work
Customer requests on WhatsApp are captured with consent, answered in a structured way and handed to CRM or service with full context when needed.
Three concrete operating scenarios to compare with your own process.Answer status questions
Order, appointment or ticket status is loaded from the source system and explained clearly.
Capture complete requests
Photos, reference number and reason are assigned to the right record.
Bring people in deliberately
Uncertain or emotional cases go to service with conversation history and detected urgency.
A strong fit when …
Requests arrive through several channels, need reliable prioritisation and should remain traceable with status, deadline and ownership.
- You handle recurring whatsapp requests using repeatable rules.
- The intake, target system and accountable business role can be named clearly.
- Exceptions are allowed to remain visible and move to people deliberately.
Deliberate automation boundary
Marketing without consent, sensitive individual cases and free-form AI answers without a source are excluded.
Explore the technical approach and platformsEstimate time savings with your own volume
The calculator uses 6 minutes today and 2 minutes after automation as fixed example assumptions. It does not replace process analysis.
Illustrative estimate based on the visible assumptions — not a guarantee.