Drag-and-build WhatsApp flows in Odoo that qualify leads, auto-create records, and hand off to live agents with full transcript. One-time license from $249.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Drag-and-build WhatsApp flows in Odoo that qualify leads, auto-create records, and hand off to live agents with full transcript.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Your team answers the same first-line WhatsApp questions all day: "What are your prices?", "Do you have this in stock?", "I need support." Every one of those messages is a lead or a ticket waiting to be captured — but only if someone is at the keyboard. The WhatsApp Chatbot & Flow Builder turns those repetitive conversations into structured, automated flows that run 24/7 inside Odoo, qualify the person on the other end, create the right record, and hand a warm, fully-documented conversation to a human the moment judgment is needed.
Visual drag-and-drop flow builder (OWL client action) to design multi-step conversations with no XML or code editing
Step, option, and branch models (whatsapp.flow / whatsapp.flow.step / whatsapp.flow.option) that map a full conversation tree to Odoo records
Keyword routing that matches inbound free-text against configurable trigger words to jump users to the right branch
Interactive button and list routing using WhatsApp's native reply-button and list-message components for tap-to-answer flows
Automatic crm.lead creation on flow completion, pre-filled with captured answers, source, and campaign tags
Automatic helpdesk.ticket creation for support flows, categorized and prioritized from the user's selections
This is a build-to-order Odoo module, not an off-the-shelf apps.odoo.com download. ECOSIRE designs, builds, installs, and supports it for your specific WhatsApp Business (Cloud API) setup and your existing CRM, Helpdesk, and routing rules. Typical delivery is 2–4 weeks depending on flow complexity and integrations. You receive the full module source, so nothing is locked to a black-box vendor.
How it works, in Odoo terms. A dedicated whatsapp.flow model stores each conversational flow; whatsapp.flow.step and whatsapp.flow.option child models hold the visual builder's steps and interactive-button choices. An OWL-based drag-and-drop canvas (rendered in a custom client action view) lets non-developers reorder steps, add keyword and button routing, and branch on user answers — no XML editing required. Inbound webhooks from the WhatsApp Business Cloud API land on a controller that matches the sender against res.partner, resumes or starts a whatsapp.flow.session, and advances the state machine. Computed fields (@api.depends) track completion progress and a live lead score; automated actions (base.automation) fire on flow completion to create a crm.lead or helpdesk.ticket, tag it, and route it. When the flow hits a handoff step or a timeout, the full transcript is posted to the record's chatter (mail.thread) and the conversation is assigned to the right sales or support agent.
Governed and multi-tenant-safe. Every model ships with ir.model.access.csv entries plus record rules so agents only see conversations for their team, and template/flow editing is gated to a dedicated "WhatsApp Manager" group. Message logs, opt-in status, and consent timestamps are stored on-record for auditability. The module respects WhatsApp's 24-hour customer-service window and template-message rules, and degrades gracefully with configurable timeout and fallback branches so a stalled conversation is never silently dropped.
Fits your stack. Runs on Odoo 17, 18, and 19, Community or Enterprise. Reporting is delivered as QWeb summaries (flows started, completion rate, leads/tickets created, average time-to-handoff) and every flow, session, and message is reachable over Odoo's XML-RPC / JSON-RPC API for BI tools or external dashboards. Because the whole thing lives inside your Odoo database, a captured lead is already in your pipeline — no CSV exports, no third-party inbox to reconcile.
Runs inbound WhatsApp campaigns and needs every enquiry qualified and pushed into the CRM pipeline automatically. Uses the builder to design qualification flows, watches lead scores, and only routes hot conversations to sales reps.
Handles first-line WhatsApp support and wants routine questions triaged before they reach an agent. Relies on button routing and auto-created helpdesk tickets, with full transcripts in chatter so agents pick up context instantly.
Owns the Odoo instance and its integrations. Needs a governed, source-available module with proper access rules and API access — not a black-box SaaS — so WhatsApp automation fits existing security, backup, and reporting standards.
Measures pipeline efficiency and wants clean data. Uses the QWeb reports and JSON-RPC feed to track completion rates, time-to-handoff, and conversion from WhatsApp flows into won deals.
Buy the license on ecosire.com and download the WhatsApp Chatbot & Flow Builder module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for WhatsApp Chatbot & Flow Builder, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| WhatsApp Business Cloud API integration | Built and wired to your number, templates, and 24h-window rules | Possible but you build the webhook and API layer from scratch | Often bundled but generic; may need extra connector apps | |
| Visual drag-and-drop flow builder | OWL canvas your team edits without code | Rarely built — usually hardcoded flows | Varies; many are form-based, not visual | |
| Auto lead/ticket creation with scoring | Automated on completion, with @api.depends lead scoring | Buildable but adds significant dev time | ||
| Agent handoff with full transcript in chatter | Assigns agent and posts complete conversation to mail.thread | Must be designed and built yourself | ||
| Timeout & fallback branch handling | Configurable inactivity windows, reminders, and catch-all branches | Depends entirely on what you implement | ||
| Team-scoped security (record rules + access CSV) | ir.model.access.csv + record rules + WhatsApp Manager group | Your responsibility to design correctly | ||
| Source code ownership (no lock-in) | Full module source handed over | You own it (you built it) | ||
| Fit to your CRM/Helpdesk routing | Configured to your teams, stages, and tags at delivery | Fully custom but at full dev cost | ||
| XML-RPC / JSON-RPC data access for BI | Flows, sessions, and messages exposed via Odoo API | Available if you model it in Odoo |
This is a build-to-order module, not an instant apps.odoo.com download. After purchase, ECOSIRE scopes your flows and integrations, then builds, installs, and tests the module on your instance. Typical delivery is 2–4 weeks depending on flow complexity, the number of departments, and any custom CRM/Helpdesk routing. You'll get a delivery timeline confirmed during the kickoff call.
Every build includes a post-launch support window covering bug fixes and compatibility with Odoo minor updates on your major version. You also get documented change-request access to add new flows or tweak logic. Because you receive the full module source, you're never locked in — and we offer extended support and retainer options if you want us to keep evolving the flows over time.
Yes. The module connects to the official WhatsApp Business Cloud API (via Meta or a Business Solution Provider). You'll need a WhatsApp Business account and an API number. If you don't have this set up yet, ECOSIRE can guide you through provisioning and template approval as part of the engagement.
The module supports Odoo 17, 18, and 19, on both Community and Enterprise. Core lead and support automation works on Community; if you use Enterprise-only apps in your routing, we integrate with those too. We confirm your exact version and installed apps during scoping so the manifest dependencies match your instance.
Yes — that's the point of the builder. Your marketing and support teams use the drag-and-drop OWL canvas to reorder steps, change keywords and buttons, and adjust branches without touching XML or Python. Editing is gated to a WhatsApp Manager security group so only authorized users can change live flows.
You define handoff steps in the flow — triggered by a keyword, a button choice, a low-confidence match, or a timeout. When one fires, the module assigns the conversation to the right sales or support user and posts the complete transcript into the record's chatter, so the agent has full context before typing a single reply.
The module stores opt-in status and consent timestamps on each contact record, logs all messages for audit, and respects WhatsApp's 24-hour customer-service window and approved-template rules. All data lives inside your own Odoo database with team-scoped record rules, so nothing leaks to a third-party inbox.
Drag-and-build WhatsApp flows in Odoo that qualify leads, auto-create records, and hand off to live agents with full transcript.