Is OpenWA safe for client-facing or business-public WhatsApp numbers?

[DavidTabacman]

I'm evaluating OpenWA to power WhatsApp messaging for real client/business numbers, and the main thing I want to understand before committing is the risk posed by the whatsapp-web.js engine.
Since whatsapp-web.js automates an unofficial WhatsApp Web session rather than going through the official Cloud API, my concern is about the ban risk: How often do numbers actually get banned in production use? Does it depend on volume, message type (bulk vs. transactional), or account age?
What do you think? Extra points if you have experienced this yourself!

[rmyndharis]

Hi @DavidTabacman — thanks for opening this poll, it's a question that comes up constantly. Rather than rehash it here, I've consolidated the answer (and the safe-sending guidance that goes with it) into a dedicated section of the README: ⚠️ Before you connect a number — please read.

Short version:

• OpenWA is unofficial (uses whatsapp-web.js / @whiskeysockets/baileys, not Meta's Cloud API), so there is always a non-zero ban risk.
• The two engines trade off differently: whatsapp-web.js is lower-risk but RAM-heavy; baileys is lighter but more detectable.
• For client-facing or business-public numbers, use a dedicated number you can afford to lose, warm it up gradually, rate-limit aggressively, and keep an SMS/email/official-Cloud-API fallback for anything mission-critical.
• For regulated deployments (healthcare, finance, EU/EEA), use Meta's official Cloud API — OpenWA is not a drop-in replacement there.

Full guardrails + the cold-contact silent-drop caveat are in the README. Closing this one in favour of that canonical source — please continue the conversation there if anything's unclear. 🙂