WhatsApp Marketing & Broadcast Campaigns

Key Features

Segment builder that resolves audiences from res.partner, crm.lead and sale.order using saved ir.filters domains, so lists stay live instead of frozen exports

Campaign object as a first-class Odoo model with draft/scheduled/running/done states, Kanban pipeline and smart-button counters

Binding to approved WhatsApp Business message templates with variable placeholders mapped to record fields and rendered per recipient at send time

Scheduling and drip release via ir.cron plus automated actions, with per-campaign send windows and timezone handling

Configurable throttling (messages per minute/hour) to respect Meta rate limits and protect your WhatsApp quality rating

Per-message status log reconciled from WhatsApp Cloud API webhooks: queued, sent, delivered, read, replied, failed — with error reason capture

Delivery, read, reply, click and conversion counts computed on the campaign via @api.depends and surfaced on the form and dashboard

Trackable short links that attribute clicks and downstream sale.order / crm.lead conversions back to the source campaign

Opt-in/opt-out compliance: consent source and timestamp stored on the contact, automatic STOP-keyword handling, hard block on non-consented sends

Reply capture that routes inbound WhatsApp responses into Odoo (Discuss/chatter or lead follow-up) so marketing and sales share context

A/B variant support on template body and CTA link within a single campaign for measurable message testing

Suppression and dedup logic (bounced numbers, hard opt-outs, invalid E.164 formatting) applied before queueing

QWeb PDF campaign report summarizing audience size, delivery funnel and conversion for stakeholders

Role-based security via ir.model.access.csv (Marketing User vs Marketing Manager) and record rules for multi-company/multi-team isolation

XML-RPC / JSON-RPC endpoints so campaigns can be triggered or reported on from external systems

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

Turn WhatsApp into a measurable, compliant marketing channel that lives inside your Odoo database. This is a build-to-order module — ECOSIRE designs, builds, installs and supports it against your exact WhatsApp Business Platform setup — not an instant apps.odoo.com download. Typical delivery is 2 to 4 weeks depending on scope, integrations and approval cycles.

Odoo core ships WhatsApp only as a transactional/conversational channel (order confirmations, one-to-one chatter replies). It has no native concept of a segmented marketing blast, per-campaign throttling, template-campaign scheduling, or attribution back to a marketing initiative. We close that gap with a purpose-built module.

Under the hood the module introduces first-class marketing objects as proper Odoo models (models.Model): a WhatsApp campaign, a recipient/queue line, and a message-event log. Audiences are resolved from your existing data — res.partner, crm.lead and sale.order — using saved filter domains and ir.filters, so a segment is a live query, not a frozen list. Templates map to your approved WhatsApp Business message templates, with variable placeholders bound to record fields and evaluated at send time. Computed fields (@api.depends) roll up delivery, read, reply, click and conversion counts onto the campaign form and Kanban cards in real time.

Sending is governed, not brute-forced. A configurable throttle (messages per minute/hour) plus scheduling via ir.cron and Odoo's automated actions spreads volume to respect Meta's rate limits and your quality rating. Every outbound message writes a status row that is reconciled from WhatsApp Cloud API delivery webhooks (queued → sent → delivered → read → replied/failed), giving you a defensible audit trail per contact.

Attribution is built in: trackable short links tag each click and tie downstream orders or leads back to the originating campaign, so you see cost-free channel ROI inside Odoo instead of guessing. Consent is treated as a compliance surface, not an afterthought — opt-in source, timestamp and opt-out (STOP) handling are stored on the contact and enforced before any send, keeping you aligned with WhatsApp Business policy and data-protection expectations.

Security is real Odoo security: access governed by ir.model.access.csv groups (Marketing User vs Marketing Manager) and record rules for multi-company / multi-team isolation. Reporting uses QWeb for campaign summary PDFs, and the whole module is reachable over XML-RPC/JSON-RPC for headless triggering from your other systems. It targets Odoo 17, 18 and 19 on both Community and Enterprise, and is delivered as clean, upgrade-safe module code you own.

What you get

Complete, upgrade-safe Odoo module source (models, views, security, data) with __manifest__.py pinned to your Odoo 17/18/19 version and Community/Enterprise edition

WhatsApp Business Platform / Cloud API connection configured against your Meta account, phone number and approved templates (WABA credentials supplied by you)

Configured segments, throttle settings, ir.cron schedules and automated actions matched to your sending policy

ir.model.access.csv and record rules set up for your user groups, teams and multi-company structure

Admin and end-user documentation covering campaign creation, template approval workflow, compliance handling and troubleshooting

A live training session for your marketing team (recording provided) plus a QWeb campaign-report template

Deployment to your environment (Odoo Online-compatible packaging, Odoo.sh, or self-hosted) with smoke-tested first campaign

A defined post-launch support and warranty window with a bug-fix SLA and a documented change-request path

Who this is for

WhatsApp-first marketing manager

Runs WhatsApp as a primary promotional channel and needs segmented blasts, scheduling and read/reply analytics in one place — without exporting contacts to a third-party blaster or losing attribution.

CRM / revenue operations lead

Wants campaign sends to draw directly from live crm.lead and sale.order filters and to see conversions attributed back to each campaign inside Odoo, feeding pipeline reporting instead of a disconnected tool.

Compliance-conscious operations owner

Responsible for opt-in consent, STOP handling and audit trails; needs enforced consent checks and a per-message delivery log to stay within WhatsApp Business policy and data-protection rules.

How WhatsApp Marketing & Broadcast Campaigns Compares

Criterion	ECOSIRE	Custom Build	Competitor
Segmented marketing blasts (vs one-to-one only)	Yes — campaign object with live CRM/sales segments	Possible but you design the data model yourself	Varies; many are conversational-only
Audiences from live res.partner / crm.lead / sale.order filters	Yes, via saved ir.filters domains	Buildable with effort	Partial support
Throttling & scheduling to respect Meta rate limits	Yes — ir.cron + configurable per-min/hour throttle	You implement and tune it	Partial support
Delivery / read / reply status from Cloud API webhooks	Yes — per-message log reconciled from webhooks	You wire the webhooks yourself	Partial support
Click & conversion attribution to campaign	Yes — trackable links tie orders/leads back	Significant extra build	Not included
Opt-in/opt-out consent enforcement & audit trail	Yes — enforced pre-send with STOP handling	You must design compliance logic	Partial support
Fits your Odoo 17/18/19, Community or Enterprise	Yes — manifest pinned to your version/edition	Yes, if you maintain it	Partial support
Built, installed & supported for you with a warranty window	Yes — full delivery + post-launch SLA	Your team owns all of it	Not included

Frequently Asked Questions about WhatsApp Marketing & Broadcast Campaigns

How long until the module is delivered and live?

This is a build-to-order module, not an instant download. Typical delivery is 2 to 4 weeks from kickoff. Timing depends on scope, how many segments and templates you need, your WhatsApp Business template-approval turnaround (Meta reviews those), and whether we integrate with other systems. We confirm a firm timeline after a short scoping call and keep you updated at each milestone: build, staging demo, then production deployment.

What do I get for support and updates after launch?

Every engagement includes a defined post-launch support and warranty window with a bug-fix SLA and a documented change-request path. During that window we fix defects, adjust throttling or templates as your sending policy evolves, and keep the module compatible with your Odoo point releases. When you upgrade major Odoo versions (for example 18 to 19) or want new capabilities, we scope that as a follow-on. You own the source, so you are never locked in.

Does this need Odoo Enterprise, or does Community work?

It runs on both Community and Enterprise across Odoo 17, 18 and 19. The module adds its own marketing objects rather than depending on Enterprise-only marketing apps, so Community users get the same segmentation, scheduling and analytics. We pin the __manifest__.py to your exact version and edition during the build.

How does it connect to WhatsApp — do I need a Meta Business account?

Yes. Sending goes through the official WhatsApp Business Platform (Cloud API), so you need a Meta Business account, a verified WhatsApp Business phone number and approved message templates. You provide those credentials; we handle the integration, webhook wiring for delivery/read status, and template-variable mapping inside Odoo. Meta's own per-message and conversation pricing applies separately from our fee.

How is opt-in and opt-out compliance handled?

Consent is enforced at the data layer. We store opt-in source and timestamp on the contact, automatically process STOP-style opt-out replies, and hard-block any send to a non-consented or opted-out number before it reaches the queue. Suppression lists and E.164 validation run pre-send. This keeps you aligned with WhatsApp Business policy and gives you a per-contact audit trail.

Can it pull audiences from my existing CRM and sales data?

That is the core design. Segments are resolved from live res.partner, crm.lead and sale.order records via saved filter domains (ir.filters), so a campaign audience is always the current matching set — for example customers who bought in the last 90 days or leads in a given stage. No CSV exports, and no stale lists.

Will campaign results show up in my Odoo reporting?

Yes. Delivery, read, reply, click and conversion metrics are computed on the campaign record and shown on the form, Kanban and a QWeb PDF summary. Trackable links attribute clicks and downstream orders or leads back to the source campaign, so channel ROI is visible inside Odoo instead of a separate tool.