Every few months a client asks me the same question: "Can we just send this over WhatsApp?"

Every few months I make the same mistake: "Sure, the Cloud API isn't that bad."

It is that bad. Not the API itself — the everything around it. After the third project where I rebuilt the same plumbing, I switched to a platform called EnoSend and got my weekends back. This is a quick post on what kept biting me, and what I do now.

The stuff nobody warns you about

Building directly on the WhatsApp Cloud API, here's what eats your time:

• Business verification and number provisioning. Days of back-and-forth with Meta before you send a single message.
• Template approvals. Marketing and utility templates have to be pre-approved. They get rejected. You guess why.
• The 24-hour window. You can only freely message a user within 24 hours of their last message. Outside that, templates only. Your code has to know which side of the window it's on.
• Bulk sending without getting flagged. Send too fast, you get rate-limited. Send too slow, your campaign takes a day. Quality rating tanks if recipients block you.
• Multiple numbers, multiple clients. The moment you have two businesses on one stack, you're building a multi-tenant routing layer you didn't budget for.
• Reselling to your own users. If you're charging end customers for messages, now you need wallets, top-ups, per-message pricing, and reconciliation.
• Instance health. Numbers disconnect. QR codes expire. You need a job that notices and reconnects before your client does.

Each one is a week of work. Together, they're a product.

What I use now

EnoSend is a WhatsApp SaaS that handles all of the above so I can focus on the part that's actually mine — the business logic. The parts that mattered most to me:

1. Bulk campaigns with scheduling, throttling, and delivery tracking. I don't write rate-limit logic anymore.
2. Multi-instance management. I can run several WhatsApp numbers for several clients from one dashboard, and the routing is solved.
3. Built-in wallet and billing. If I'm reselling to end clients, the per-message accounting is already there. I'm not building a billing system on the side.
4. Auto-reconnect for stuck instances. QR and connecting states get cleaned up in the background. I stopped getting "the number is offline" messages on Sunday nights.
5. A marketing and ticketing layer on top, for when the client wants more than just sending.

A rough sketch of what shipping a WhatsApp feature looks like now versus before:

Before:

Week 1-2: plumbing (auth, webhooks, templates, rate limits, retries)
Week 3:   more plumbing (multi-tenant routing, instance health)
Week 4:   start the actual product

After:

Day 1: start the actual product

You can wire up a send in a few lines:

enosend.send(to=number, template="order_confirmation", vars={...})

That's the part I wanted to write. Everything underneath it is somebody else's problem now.

When EnoSend is the right call

Use it if you're:

• Building a tool that sends WhatsApp messages on behalf of clients (agencies, SaaS, marketplaces)
• Running bulk campaigns and tired of fighting rate limits and quality ratings
• Managing multiple WhatsApp numbers across multiple businesses
• Reselling WhatsApp messaging and need billing + wallets out of the box
• Just tired of explaining template rejections to your team

Probably overkill if you only need to send one transactional message a day from one number — the raw Cloud API will do.

The takeaway

The Cloud API gives you a protocol. A product needs everything around the protocol — quality management, billing, multi-tenant routing, campaign throttling, instance health. That second list is the iceberg.

If the part you actually want to build is the product, not the messaging layer underneath it, hand the messaging layer to something else. I use EnoSend. It made me faster and it made my clients happier, which is the only metric that matters.

Build the part that's yours.