openWA: free WhatsApp bots without Meta costs? What you need to know before you start

Anyone who wants to automate WhatsApp for business runs into openWA sooner or later. The promise is simple: a free, open source program that you put on your own server, with which you build bots, send messages automatically and connect WhatsApp to your own systems. No templates that you have to get approved first, no cost per message, no Meta looking over your shoulder. To a developer that feels like freedom, to a business owner like a saving.

We get questions about it too. A customer recently asked in a support ticket whether he could use openWA alongside CommuniQate, to get around the costs of Meta. A logical question if you only see the surface. This article is the answer we gave him, written out: how openWA works, what it gets you and why we advise our customers against it.

openWA, also written as open-wa, is not a service of WhatsApp and not an official connection from Meta. It is a program that automates WhatsApp Web. You scan a QR code, exactly the way you open WhatsApp Web on your laptop, and from that moment on openWA drives that session: it reads the messages that come in and types the replies your software supplies. Under the bonnet it does that with an invisible browser running WhatsApp Web, or with a rebuilt version of the protocol the WhatsApp app uses to talk to Meta's servers. On top of that it puts its own connection and webhooks (automatic signals to your software the moment a message arrives), so that to your developer it feels like a real, free WhatsApp API.

The project does not keep that quiet either: its own website states that it has no ties whatsoever with Meta or WhatsApp, and that automated use through third party software carries risk. That is the heart of everything that follows. From Meta's point of view, openWA is not a business tool but a user who behaves differently from a human being.

On paper openWA can do much of what the official API can: send and receive messages, photos and documents, manage groups, reply automatically, send bulk messages and pass everything through to your own system. It runs on your own number, without registering with Meta, and you can start tonight.

That is exactly where the appeal lies. The official WhatsApp Cloud API asks for a business account, a verified company (Meta checks whether your business really exists), templates that Meta approves in advance and a fee for every message that you as a business start. openWA asks for none of that. What the guides do not tell you is why Meta built those steps in, and what happens when you skip them.

WhatsApp's terms of service set out what you may not do: rebuild or modify the service, gain access to it through workarounds or automated means, and build software or connections that do the same as WhatsApp itself without permission. An unofficial WhatsApp API such as openWA, which drives WhatsApp Web or imitates the protocol, falls squarely under that. It makes no difference whether you use it for something legitimate, such as sending appointment reminders. The violation lies in the method, not in the content. Careful use, as the guides advise (using the number normally for a few weeks first, no cold messages), changes nothing about that either: it may reduce the chance that you stand out, not the violation.

Meta enforces this actively. The servers recognise an unofficial program by the way it signs in and behaves: the pace, the patterns, the technical characteristics of the connection. The penalty is not a warning or a fine, but switching off the account. Sometimes temporary, with a timer counting down until you are allowed back, often permanent straight away. You can appeal, but with a permanent ban that rarely helps, and then the number is definitively unusable on WhatsApp: you can no longer reach your conversations, not even to export them. How to recognise a ban and what you can still do then is in our article about a blocked WhatsApp Business account; here it is enough to know that the chance is high and the damage lasting.

Put the saving next to the risk for a moment. What you pay Meta for are the messages that you as a business start: a reminder, a quote, a campaign. If a customer messages you, or replies to your message, everything you send back within 24 hours is free. For a business with hundreds of conversations a month it comes down to a few tens of euros, not thousands.

On the other side is the number that is on your website, your company van and your business cards, with all the running conversations in it: the customer waiting for approval, tomorrow's appointment, the complaint that is half dealt with. On the day of the ban all of that stops at once, without warning. Some of our customers ended up with us in exactly that way: first an unofficial connection or a heavily used Business App, then a ban, and after that the official route anyway, but with a new number and weeks of lost ground. Work that through and the free solution is the most expensive one.

Even without a ban there are two reasons not to put openWA into your business.

• Privacy. With openWA all customer conversations run through a program that you host yourself and that nobody supervises. On the official API it is laid down how Meta and your platform handle customer data. With openWA there is nobody you have that agreement with: for the GDPR you are solely responsible for that processing, including the security of a session that is permanently logged in to your business WhatsApp. Whoever gets into that server can message as your company.
• Reliability. openWA works as long as WhatsApp Web behaves the way the program expects. Every update from Meta can break the connection, and that happens without notice. There is no supplier to call, no guarantee and no status page; there is a community that repairs things in its own time. Fine for a hobby project, not for the channel your customers reach you on.

Everything people look for in openWA (bots, automatic replies, connections with their own system) exists officially as well. There are three ways to use WhatsApp for business that Meta offers itself:

1. 1The WhatsApp Business App. Free, for small teams where customer contact mainly comes in. No bots or connections, but a business profile, quick replies and labels. You can read where the limits lie in our article about the possibilities and limits of the Business App.
2. 2The WhatsApp Cloud API through a partner such as CommuniQate. Meta's official connection, with a team inbox, automatic flows, forms and connections to your calendar, till or CRM around it. You pay Meta per message that you start yourself and a subscription for the platform; in return your number is safe, everything you do with it is allowed and there is someone on the phone when something does not work.
3. 3The WhatsApp Cloud API directly from Meta. The same connection, free at Meta itself, but without a platform: your developer builds the inbox, the flows and the template management themselves. An option for companies with their own development team.

The difference with openWA is not what you can do, but what ground you stand on. On the API you start a conversation with an approved template and Meta keeps track of your quality rating (a score for how customers respond to your messages); in return your number does not disappear from one day to the next.

Our advice is short: do not do it. Not out of self-interest, but because we too often get the call from a company whose number was switched off that morning. The customer from the support ticket said it himself after our explanation: he had not known that.

If you already use openWA, the order is this: export your conversations while you still can (per chat, from the WhatsApp app itself), switch off the automation and move your number to the official API before Meta makes the choice for you. How that move goes step by step is in our article about moving from the Business App to the Cloud API. And the bots and connections you had thought up with openWA? You simply build those again on the API, but this time on a foundation that holds.