ERPNext already holds your Leads, Customers and Contacts, but it has no native way to run structured WhatsApp marketing off that data. The built-in notification and WhatsApp settings are transactional and one-to-one — fine for an order confirmation, useless for a segmented promotional broadcast to ten thousand opted-in numbers. Marketing teams end up exporting CSVs into a disconnected third-party blaster, losing the link between who received a campaign and the Lead/Customer record it came from, with no consent trail and no way to feed replies back into ERPNext. When a regulator or the WhatsApp Business Platform asks about opt-in evidence, the answer lives in a spreadsheet nobody trusts.

We build a proper Frappe app (its own module, installed via bench get-app and bench install-app) that turns ERPNext into your WhatsApp marketing control room. The core is a set of purpose-built DocTypes — WA Campaign, WA Template, WA Audience Segment, WA Recipient (child), WA Message Log and WA Consent — wired to the WhatsApp Business Cloud API (or your BSP/on-premise provider). An Audience Segment is defined as a saved Frappe report filter or a whitelisted query against Lead, Contact, Customer or a custom list, so a segment like "UAE retail leads, opted-in, no purchase in 90 days" is resolved live at send time rather than frozen into a stale export. Templates are modelled to mirror the Meta template lifecycle — draft, submitted, approved, rejected — with the header/body/button variables validated before a campaign can reference them.

Sending is driven by Frappe's own scheduler. A WA Campaign set to a future time (or a recurring cadence) is picked up by a scheduler_events hook that enqueues messages onto a background queue with rate-limiting and per-number throttling to stay inside your WhatsApp tier limits. Delivery, sent, read and failed statuses arrive back through a whitelisted webhook endpoint (@frappe.whitelist(allow_guest=True) with signature verification) that updates each WA Message Log row; inbound replies are captured against the originating recipient so your team sees the conversation next to the CRM record. hooks.py doc events keep everything consistent — a consent withdrawal instantly suppresses a contact from every future segment, and a Client Script gives marketers a live delivery/read/reply dashboard on the campaign form without leaving ERPNext. Everything respects Frappe's permission model: role profiles like "Campaign Manager" and "Campaign Approver" gate who can send versus who can only draft, and all data stays inside your organizationId-scoped site.

Because this is build-to-order, nothing is a black-box download. After a short scoping call we confirm your exact segments, template catalogue, WhatsApp provider (Meta Cloud API, Twilio, 360dialog, or another BSP) and consent rules, then build against your ERPNext v15 or v16 site. We deliver on staging first for UAT, hand over the full git repository and source, install and configure it on your production bench, train your team, and stay on a post-go-live support window. Typical delivery is one working week from confirmed scope.