什么是 WhatsApp Marketing & Broadcast Campaigns for ERPNext？
A build-to-order Frappe app that lets your marketing team segment ERPNext audiences, schedule template-based WhatsApp broadcasts, and track delivery, read and reply analytics per campaign. ECOSIRE scopes, builds, installs and supports it for you. Built to order by ECOSIRE for ERPNext v15, v16 — indicative price from $999.00 USD; request a quote for a scoped proposal.
产品详细信息以英文显示。翻译即将推出。
示意预览A build-to-order Frappe app that lets your marketing team segment ERPNext audiences,
schedule template-based WhatsApp broadcasts, and track delivery, read and reply analytics per campaign.
ECOSIRE scopes, builds, installs and supports it for you.
核心功能
Dedicated Frappe app and module installed via `bench get-app` / `bench install-app`, with custom DocTypes (`WA Campaign`, `WA Template`, `WA Audience Segment`, `WA Recipient`, `WA Message Log`, `WA Consent`) rather than overloaded custom fields
Audience segments defined as saved Frappe report filters or whitelisted queries over `Lead`, `Contact`, `Customer` and custom lists, resolved live at send time so recipient lists are never stale exports
WhatsApp Business template catalogue modelling the Meta approval lifecycle (draft → submitted → approved → rejected) with header/body/button variable validation before a campaign can use a template
Scheduled and recurring broadcasts driven by Frappe `scheduler_events` (`cron`/`daily`/`hourly`), enqueued to the background worker via `frappe.enqueue` with per-number throttling to respect WhatsApp tier limits
Whitelisted webhook endpoint (`@frappe.whitelist(allow_guest=True)`) with signature verification that ingests sent/delivered/read/failed status callbacks and updates each `WA Message Log` row
Inbound reply capture linked back to the originating recipient and CRM record, so replies surface next to the `Lead`/`Contact` in ERPNext
Per-campaign analytics: sent, delivered, read, failed and reply counts with rates, plus per-recipient drill-down, rendered on the campaign form via a Client Script dashboard
Opt-out and consent management via a `WA Consent` DocType, with `hooks.py` doc events that suppress withdrawn contacts from every future segment automatically
Role profiles and permission rules (e.g. Campaign Manager vs Campaign Approver) so drafting, approving and sending are separated for governance
Pluggable provider layer supporting Meta WhatsApp Cloud API, Twilio, 360dialog or another BSP, with credentials kept in a single-DocType Settings record (encrypted `password` fieldtype)
Merge-field personalization pulling template variables from ERPNext fields (customer name, order number, city) with a safe fallback for missing values
Rate-limit, retry-with-backoff and failure-quarantine logic on the send queue so a provider 429 or number block doesn't stall the whole campaign
Server Scripts and hooks kept upgrade-safe (no core patches), compatible with ERPNext / Frappe v15 and v16
Exportable campaign reports via the Frappe Report Builder and REST API (`/api/resource/WA Campaign`) for downstream BI or audit
按需定制，全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 ERPNext 上构建、配置并安装。
- 3
上线 + 支持
约 2–4 周内上线，并提供上线后的支持期。
技术规格
- ERPNext 兼容性
- —
- 许可证
- GPL-3.0
- Python 要求
- Python 3.10+
- 数据库
- MariaDB 10.6+
关于此产品
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 2-4 weeks from confirmed scope.
你得到什么
- Installable source code for your commissioned version of the Frappe app, pinned to your ERPNext v15 or v16 line
- Installation and configuration on your bench, including provider credentials, webhook wiring and scheduler verification
- Technical documentation: DocType schema, hooks and scheduler events, webhook contract and provider setup notes
- End-user guide plus a live training session for your marketing and approver roles
- UAT on a staging site with a documented rollback plan before any production change
- A defined post-go-live support window for bug fixes and adjustments after handover
- Full git repository handover so your team owns and can extend the code
- Consent and template-catalogue setup mapped to your actual segments and WhatsApp Business account
这是给谁的
Marketing / Growth Manager
Owns promotional WhatsApp outreach in an emerging-market business and needs to segment ERPNext leads and customers, schedule broadcasts, and prove which campaigns drove replies and conversions — without exporting data into a disconnected blasting tool.
CRM / Sales Operations Lead
Wants every WhatsApp send and reply logged against the originating Lead or Customer record so the sales team follows up in context, and needs consent status enforced automatically across all campaigns.
ERPNext Administrator / IT Manager
Responsible for keeping the site upgrade-safe on Frappe v15/v16, wants a proper app rather than brittle custom scripts, and needs role-based permissions separating who can draft from who can approve and send.
Compliance / Data Protection Owner
Needs an auditable opt-in and opt-out trail inside ERPNext, template governance aligned to WhatsApp Business policy, and confidence that withdrawn consent instantly removes a contact from future broadcasts.
WhatsApp Marketing & Broadcast Campaigns for ERPNext 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | ERPNext 原生 |
|---|---|---|---|---|
| Audience segmentation | Live segments from ERPNext filters/queries over Lead/Contact/Customer, resolved at send time | Whatever your developer hand-codes; often stale exports | Basic tag or list upload, weak ERPNext data binding | No marketing segmentation — transactional messaging only |
| Scheduled & recurring broadcasts | Frappe scheduler_events + background queue with throttling and retry | Depends on build; cron often bolted on ad hoc | Usually present but fixed to the vendor's model | Not available for bulk marketing |
| Template lifecycle & approval | DocType modelling Meta draft/submitted/approved/rejected with variable validation | Rarely modelled; managed manually in Meta console | Sometimes; varies widely by app | None |
| Delivery / read / reply analytics | Per-campaign and per-recipient metrics via signed webhook, shown on the form | Only if explicitly built and maintained | Vendor dashboard, often outside ERPNext | No campaign analytics |
| Consent & opt-out enforcement | WA Consent DocType + hooks.py events suppressing opt-outs from all segments | Must be designed and enforced by hand | Basic unsubscribe, inconsistent ERPNext sync | No structured consent trail |
| ERPNext integration & data ownership | Native DocTypes, REST API, permissions; all data in your site | Native if built well, but you own the maintenance burden | Often stores data in the vendor's cloud | N/A — no marketing layer |
| Upgrade safety (v15/v16) | Standard Frappe app, no core patches, tested on v15/v16 | Risk of core edits that break on upgrade | Depends on vendor's maintenance cadence | Part of core, but no feature to speak of |
| Support & handover | Install, training, post-go-live window, full git repo handover | Tied to the individual developer's availability | Vendor SLA, no source access | Community/forum only |
关于WhatsApp Marketing & Broadcast Campaigns的常见问题
Is this an app I can download and install instantly?
No. This is a build-to-order product. ECOSIRE builds it against your specific ERPNext site, segments, template catalogue and WhatsApp provider, then installs and configures it for you. It is not a pre-existing Frappe Cloud Marketplace download.
How long does delivery take?
Typical delivery is 2-4 weeks from confirmed scope. The timeline starts once we've completed the scoping call and agreed your segments, provider (Meta Cloud API / Twilio / 360dialog / other BSP), template catalogue and consent rules. Larger or multi-integration scopes may extend this, and we'll say so in the proposal.
Which ERPNext and Frappe versions are supported?
We build for Frappe / ERPNext v15 and v16. The app installs as a standard Frappe app via `bench get-app` and `bench install-app`, uses DocTypes, hooks and scheduler events rather than core patches, so it stays upgrade-safe on your bench.
Which WhatsApp provider does it use — do I need the official Business API?
Yes, template marketing requires an approved WhatsApp Business account. We build a pluggable provider layer, so you can use the Meta WhatsApp Cloud API directly or a BSP such as Twilio or 360dialog. You bring the account and credentials; we wire the sending, webhooks and template lifecycle to it. We do not build unofficial or unapproved sending methods.
How are opt-outs and consent handled?
A dedicated `WA Consent` DocType records opt-in and opt-out with timestamps, and `hooks.py` doc events suppress any withdrawn contact from every future audience segment automatically. Segments resolve consent live at send time, so a contact who opts out is never included in a later broadcast.
What about support and updates after go-live?
Every engagement includes a defined post-go-live support window for bug fixes and adjustments. Because you receive the full git repository and source, your team can also extend the app independently. Ongoing enhancements, new segments or version upgrades can be arranged as a separate support retainer or change request.
Will campaign data and replies stay inside ERPNext?
Yes. All templates, segments, message logs, delivery statuses and inbound replies live in your ERPNext site as DocTypes, scoped to your organization and governed by Frappe's permission model. Nothing is stored in an external marketing tool, and everything is queryable via the Frappe REST API and Report Builder.
相关模块
按单定制
按单定制
按单定制
申请报价
WhatsApp Marketing & Broadcast Campaigns
A build-to-order Frappe app that lets your marketing team segment ERPNext audiences, schedule template-based WhatsApp broadcasts, and track delivery, read and reply analytics per campaign. ECOSIRE scopes, builds, installs and supports it for you.
- Dedicated Frappe app and module installed via `bench get-app` / `bench install-app`, with custom DocTypes (`WA Campaign`, `WA Template`, `WA Audience Segment`, `WA Recipient`, `WA Message Log`, `WA Consent`) rather than overloaded custom fields
- Audience segments defined as saved Frappe report filters or whitelisted queries over `Lead`, `Contact`, `Customer` and custom lists, resolved live at send time so recipient lists are never stale exports
- WhatsApp Business template catalogue modelling the Meta approval lifecycle (draft → submitted → approved → rejected) with header/body/button variable validation before a campaign can use a template
- Scheduled and recurring broadcasts driven by Frappe `scheduler_events` (`cron`/`daily`/`hourly`), enqueued to the background worker via `frappe.enqueue` with per-number throttling to respect WhatsApp tier limits