I Stopped Hand-Rolling WhatsApp Integrations. Here's What I Use Instead.

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