WhatsApp Automation for Small Business in Cyprus and Greece: Rules, Costs and Use Cases (2026)
Dabster Labs · Last updated 27 August 2026
Through the official WhatsApp Business Platform a small business can automate replies inside the 24 hour customer service window, send appointment confirmations and reminders as utility templates, run opt in marketing and hand any conversation to a person. Meta has charged per message since 1 July 2025. Unofficial tools that scrape the app get numbers banned.
The rules that decide everything
WhatsApp is not email. Meta decides when you may write, what you may send and what it costs. Four rules cover almost every decision.
The 24 hour customer service window. When a customer writes to you first, a window opens for 24 hours. Inside it you can reply freely, without a template, and those replies are free. Utility templates sent inside the window are free too.
The 72 hour free entry point. When a customer reaches you through a click to WhatsApp ad or a page button, all messages within the next 72 hours are free.
Templates outside the window. Once the window closes, you can only send templates that Meta has approved in advance. A reminder sent two days before an appointment is almost always a template.
Four categories. Every template belongs to one category, and the category sets both the price and the consent you need.
| Category | What it is | Example | Cost and consent |
|---|---|---|---|
| Service | Free form reply inside the 24 hour window | Answering “are you open on Saturday?” | Free inside the window |
| Utility | Message about something the customer asked for | Appointment reminder, order status | Free inside the window, charged outside it |
| Marketing | Offers, news, promotions | “September offer on physiotherapy packages” | Charged, needs the customer’s opt in |
| Authentication | One time codes | Login or verification code | Charged |
Opt in and GDPR. Marketing messages need the customer’s opt in, recorded with a date and a source. Under GDPR your business is the controller of the contact data: you tell people who processes their data and why, you keep only what you need and you answer access requests. We propose 30 days of retention for any transcript.
What it costs
There are two separate bills: what Meta charges per message, and what the automation costs to build and run.
The platform fee. Meta charges per message, and the rate depends on the country code of the recipient’s number and on the template category. We do not quote figures because Meta changes them; check the current rate card. The free cases matter more than the rates: a business that mostly answers inbound questions and sends utility reminders inside the window pays very little, while one that sends marketing templates to its whole list pays for every one.
Our build. We start with a process audit from EUR 500, credited to the build if you go ahead. A fixed price build starts from EUR 2,500 and covers the platform setup, the templates in Greek and English, the n8n flows and the connection to your calendar or CRM. Management from EUR 699 per month covers monitoring, template changes and a monthly review of real conversations. Same figures as our pricing page, no WhatsApp surcharge.
Use cases that work for Cyprus and Greek SMEs
Each flow has a human checkpoint, the moment a person takes over, because a bot that never hands over loses customers.
- Appointment reminders for clinics and therapy centres. A booking in the calendar triggers a utility template the day before. Checkpoint: change requests go to the reception as an open thread, the bot never moves an appointment on its own. See AI automation for clinics.
- Booking requests for hotels and accommodation. A guest writes from the button on your site, which opens the 72 hour free window. The bot asks for dates and guests and sends the options. Checkpoint: a person confirms the price and sends the payment link.
- Document collection for accountants and insurance offices. On the agreed date each client receives a template asking for the month’s invoices or the renewal documents, and the CRM marks what has arrived. Checkpoint: the accountant or broker reviews the files, the bot only chases what is missing. See AI automation for accountants.
- Lead reply within minutes. A form or an ad click gets a first WhatsApp reply within a minute, with two or three qualifying questions. Checkpoint: as soon as the lead answers, a person takes the conversation, and the bot never quotes a price nobody approved.
- Order status for organisations. A status change in your system, an application received or a certificate ready, triggers a utility template. Checkpoint: any reply that sounds like a complaint goes to a person.
- After visit review requests. A short message after the visit asks how it went, sent only to customers who agreed to receive it. Checkpoint: a negative reply reaches the owner the same day, never a template.
WhatsApp plus the phone
The customer who writes on WhatsApp at noon calls the office at five. Our AI receptionist answers the phone in Greek and English, books into the calendar and notifies the team. WhatsApp answering can be added to the AI receptionist as part of the build, on the same knowledge base and the same CRM log.
Both channels use the same knowledge base, so the answer about opening hours or prices is identical whether the customer calls or writes. Both log into the same CRM record, so a call and a WhatsApp thread from the same number sit in one place. At DROSOS Clinic in Kos the AI receptionist answered all 41 calls in its first three weeks, more than half outside opening hours.
What to avoid
- Unofficial APIs. Tools that run a modified WhatsApp app or scrape the web client get numbers banned, and they process personal data through a route you cannot document, which breaks your duties as controller.
- Bulk marketing without opt in. Exporting your contacts and sending everyone an offer is the most common request we turn down. A list of numbers from past invoices is not consent.
- Collecting data you already have. If the patient’s name and number are in the calendar, the bot must not ask for them again.
- No exit path to a person. Every flow needs a word or a button that reaches a human, and a fallback when the bot does not understand.
- Hiding that it is a bot. Since 2 August 2026 Article 50 of the EU AI Act requires that people are told they are talking to an AI unless it is obvious. Say it in the first message.
How we build it
- Audit. We read a week of your real WhatsApp conversations, count them by type and agree which ones run on their own and where the handover sits.
- Official platform setup. Meta Business account, the number registered on the WhatsApp Business Platform, and the templates written in Greek and English and submitted for approval before anything else is built.
- n8n flows on EU servers. One n8n instance per client, so your data never mixes with anyone else’s, connected to your calendar, booking system and CRM.
- Logs in the CRM. Every message, consent and handover is written to the contact record with a timestamp. Transcripts are deleted after 30 days by default.
- Test, go live, review. We test on real conversations before launch, then the monthly management covers monitoring, template changes and a review of what customers actually asked. The same flows run on a website chatbot, see AI chatbots in Cyprus.
Frequently asked questions
Do I need a WhatsApp Business account?
Yes. Automation runs on the official WhatsApp Business Platform, which needs a Meta Business account and a number registered on the platform. The free WhatsApp Business app on a phone has greetings and quick replies, but it does not connect to your calendar or CRM.
Can I use my existing number?
Usually, but check before you commit. A number can be moved to the Business Platform, and Meta’s rules on whether the same number can stay active in the app at the same time have changed more than once. Follow the migration steps in Meta Business Help at the time you move, and do not run the same number in the app and on the platform without checking the current rule. We check the current rule for your number during the audit.
Is WhatsApp automation GDPR compliant?
It can be, and the responsibility is yours as the controller. You need a lawful basis for each type of message, opt in for marketing, a clear notice about who processes the data and why, and a retention period. Our builds record consent, keep transcripts for 30 days by default and run on EU servers.
Can it send messages to everyone in my contacts?
No. Marketing messages need the customer’s opt in, and outside the 24 hour window you can only send approved templates. Sending an offer to numbers that never agreed to hear from you breaks Meta’s rules and GDPR at the same time.
How fast can it be set up?
The build is fixed price and scoped in the audit. The two things outside our control are Meta’s template approval and access to your calendar or CRM, so we give you a date after the audit, not before.
Does it work in Greek?
Yes. Templates are submitted in Greek and English, the bot answers in the language the customer writes in, and the handover goes to a Greek speaking person on your team.
Send us the WhatsApp conversations you handled last week, and in one call we will tell you which of them can run on their own and what the platform fee would be at your volume. Contact us here.
How we do this for clients: WhatsApp automation for your business: what we set up and run
