In WhatsApp-first markets across MENA, South Asia and LATAM, your leads and customers reply on WhatsApp — but ERPNext core has no WhatsApp channel. Teams end up bouncing between a phone and the desk, copy-pasting order numbers and delivery updates by hand, losing the thread of who said what, and having no record of a conversation attached to the Lead, Contact or Customer it belongs to. Generic broadcast tools sit outside ERPNext entirely, so a quotation status or an invoice reminder never fires from the document that changed. This is exactly where native ERPNext runs out of road.

ECOSIRE builds a proper Frappe app that talks to the Meta WhatsApp Cloud API directly — no third-party messaging middleman marking up every conversation. The app ships its own module and DocTypes: a WhatsApp Settings single DocType holding your Cloud API phone-number ID, WABA ID and encrypted access token; a WhatsApp Message DocType that logs every inbound and outbound message with delivery/read status; and WhatsApp Template records that sync to and from Meta so approval status and variable placeholders stay in step. A whitelisted webhook endpoint receives inbound messages and status callbacks from Meta, verifies the payload signature, and threads each message onto the linked party record, so the full conversation history is visible right on the Lead, Contact or Customer form via a client script timeline.

Automation is wired through hooks.py doc events and server scripts: on_submit of a Sales Invoice can send an approved payment-reminder template, a Delivery Note submission can push a dispatch notification, and a stage change on a Lead can trigger a follow-up — each mapped to a Meta-approved template with variable substitution pulled from the source document's fields. Outbound sending, template sync and campaign dispatch run as background jobs and scheduler events so the request stays responsive and Meta's rate limits are respected. Bulk broadcast campaigns target a recipient list or a report/filter, queue per-recipient sends, and record delivery outcomes back on each WhatsApp Message. Access is governed by Frappe role profiles and permission rules, and every method that touches the Cloud API is a whitelisted, permission-checked endpoint — nothing bypasses ERPNext's own security model.

Because this is build-to-order, there is no instant download. We start with a short scoping call to confirm which DocTypes trigger which templates, your campaign and role requirements, and your Frappe/ERPNext version (v15 or v16). We then build against that scope, provision your WhatsApp Cloud API and message templates with Meta, and validate everything on a staging bench before touching production. Typical delivery is one working week from confirmed scope, depending on how many notification flows and templates you need. You receive the installable source for your version, a git repository handover, documentation, a training session, and a post-go-live support window — you own the code and can extend it yourself afterward.