WhatsApp CPaaS platform
Business messaging infrastructure on the WhatsApp Business API — panel, gateway and automation surface for programmatic customer messaging.
WhatsApp is the default business channel in Malaysia — receipts, order updates, OTPs and support all live there. I work on the platform layer that lets businesses send through it programmatically: the WasapBom panel and the WhatsApp Business API integration underneath it.
The work
- The messaging gateway. Template management, session handling, and delivery status tracking against the WhatsApp Business API — the messy reality of message states (sent, delivered, read, failed-for-seventeen-reasons) normalised into something an application can act on.
- Webhooks both directions. Inbound messages and status callbacks fan out to customer systems with retries and signing; the platform treats webhook delivery with the same seriousness as message delivery, because to the integrating developer they are the same thing.
- The automation surface. Official n8n community nodes so non-developers can wire WhatsApp into workflows — order confirmation flows, form-to-message pipelines — without touching the API directly. The same philosophy as the payment SDKs: meet integrators where they already are.
What the domain teaches
Messaging platforms are rate-limit-and-state machines. Everything interesting happens at the edges: a template pending approval, a session window expiring mid-conversation, a webhook consumer that’s been down for an hour. Building for those edges — visible queues, honest status, replayable deliveries — is the difference between a demo and a platform.