In WhatsApp-first markets across MENA, South Asia, and LATAM, your customers read a WhatsApp message in seconds and ignore email for days. ERPNext ships email and SMS notification channels out of the box, but it has no native, supported connection to the WhatsApp Cloud API — no template management, no session-window handling, no two-way inbox, and no way to attach a rendered invoice PDF to an outbound message. Teams end up copying order numbers into a personal WhatsApp on someone's phone, which loses the audit trail, breaks when that person is out, and never scales past a handful of conversations.

The WhatsApp Cloud Business Suite is a proper Frappe app (its own module, DocTypes, hooks.py, and fixtures) that ECOSIRE builds and installs on your ERPNext v15 or v16 bench. At its core is a WhatsApp Settings single DocType holding your Meta WhatsApp Business Account credentials (phone number ID, permanent access token stored encrypted, and app secret for webhook signature verification). A WhatsApp Message DocType logs every inbound and outbound message with delivery status, linking each thread back to the related Customer, Lead, or Contact so conversations live inside ERPNext rather than on a phone. Outbound sends go through whitelisted server-side methods that call the Cloud API /messages endpoint; a webhook receiver (a whitelisted, allow_guest method that validates Meta's X-Hub-Signature-256 HMAC) ingests inbound messages and status callbacks, updating message records via frappe.db.set_value and publishing realtime events to the Desk inbox.

We wire notifications to real business events using doc_events in hooks.py — for example on_submit of Sales Invoice triggers an approved template message with a link to (or PDF of) the invoice, and on_update_after_submit of Delivery Note sends a dispatch update. Template messages are managed through a WhatsApp Template DocType that mirrors your Meta-approved templates and their variable placeholders, so non-developers can map ERPNext fields to {{1}}, {{2}} parameters without touching code. Because the 24-hour customer-service window rules which message types are allowed, the app tracks the last inbound timestamp per contact and automatically chooses between a free-form session message and an approved template — respecting Meta's policy instead of getting your number flagged. A scheduler event reconciles pending delivery statuses and retries transient failures.

Because this is build-to-order, nothing ships as a blind download. We start with a short scoping call to confirm your exact document events, template catalog, role permissions, and ERPNext version, then build against your requirements and deliver on a staging/UAT bench first. Typical delivery is one working week from confirmed scope, depending on how many templates and triggers you need. You get the full source in a Git repository, a documented install, user training, and a post-go-live support window — you own the code and can extend it yourself or keep it under our maintenance.