WhatsApp Chatbot & Flow Builder

Name: WhatsApp Chatbot & Flow Builder
Brand: ECOSIRE
SKU: whatsapp-chatbot-flow-builder

核心功能

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

Live lead scoring via computed @api.depends fields that weight answers and rank hot conversations

Agent handoff step that assigns the conversation to a sales/support user and posts the complete transcript to chatter (mail.thread)

Timeout handling with configurable inactivity windows that trigger a reminder, a fallback branch, or graceful closure

Fallback and 'catch-all' branches so unrecognized replies get a helpful response instead of dead air

res.partner matching and auto-creation so every WhatsApp contact resolves to a real Odoo customer record

24-hour service-window awareness and approved-template handling to stay compliant with WhatsApp Business policy

Automated actions (base.automation) that tag, route, and notify on defined flow events

Full message and session logging with opt-in/consent timestamps stored on-record for audit

QWeb analytics report: flows started, completion rate, records created, and average time-to-handoff

Team-scoped record rules and ir.model.access.csv so agents only see their own conversations

XML-RPC / JSON-RPC exposure of flows, sessions, and messages for external BI and dashboards

Multi-flow / multi-department support so sales, support, and bookings each run their own logic on one number

按需定制，全程代劳

无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。

您下单

以一次性构建价格开始。我们在启动时与您共同确定范围。

我们构建与安装

ECOSIRE 在您的 Odoo 上构建、配置并安装。

上线 + 支持

约 2–4 周内上线，并提供上线后的支持期。

关于此产品

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.

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.

你得到什么

Complete, documented Odoo module source (models, OWL views, controllers, security, QWeb reports) with a proper __manifest__.py declaring version, dependencies, and data files

Working installation on your Odoo 17, 18, or 19 instance (Community or Enterprise), wired to your WhatsApp Business Cloud API credentials

Configured starter flows built to your scripts — typically a lead-qualification flow and a support-triage flow — ready to go live

CRM and Helpdesk integration configured to your teams, stages, tags, and routing rules

ir.model.access.csv access rights plus record rules and a WhatsApp Manager security group, tuned to your org structure

Admin and agent documentation: how to edit flows, read transcripts, manage handoffs, and interpret the analytics report

A live training session (recorded) for your marketing/support team on building and maintaining flows

A post-launch support window with bug fixes and Odoo minor-version compatibility, plus a change-request path for new flows

这是给谁的

Lead-Generation Manager

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.

Customer Support Lead

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.

Odoo / IT Administrator

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.

Sales Operations / RevOps Analyst

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.

WhatsApp Chatbot & Flow Builder 如何比较

标准	伊科西尔	定制建造	竞争对手
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	部分支持

关于WhatsApp Chatbot & Flow Builder的常见问题

How long does delivery take, and is this an instant download?

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.

What support and updates are included after go-live?

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.

Do I need WhatsApp Business API access first?

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.

Which Odoo versions and editions are supported?

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.

Can non-technical staff edit the flows after handover?

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.

How does a conversation get handed to a human agent?

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.

Is customer data and consent handled compliantly?

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.