Odoo Live Chat and WhatsApp Integration Guide
Customer communication has fragmented across more channels than any support team can manage efficiently. Website visitors expect live chat. Customers in emerging markets prefer WhatsApp. Business contacts communicate via email. When each channel operates in isolation — separate tools, separate histories, separate agents — customers repeat themselves, service is inconsistent, and agents waste time context-switching between systems. Odoo 19 Enterprise unifies live chat, WhatsApp, email, and social messaging into a single inbox, giving every agent full context for every conversation regardless of which channel the customer used.
This guide covers the complete Odoo Live Chat and WhatsApp integration setup: live chat widget configuration, chatbot automation, WhatsApp Business API integration, unified inbox management, conversation routing, and engagement analytics. By the end, you'll have a production-ready omnichannel messaging operation connected to your CRM, Helpdesk, and customer records.
Key Takeaways
- Configure the live chat widget for your website with custom branding and availability rules
- Set up automated greeting messages and chatbot flows for lead qualification and FAQ deflection
- Integrate WhatsApp Business API for two-way customer messaging from within Odoo
- Route conversations to the right team or agent based on channel, topic, and customer type
- Access full customer history (CRM, sales, support tickets) from within every chat conversation
- Convert chat conversations to helpdesk tickets, CRM leads, or sales opportunities with one click
- Track response times, satisfaction ratings, and agent performance in real time
- Unify all customer messaging in one inbox that your entire team can access
Live Chat Widget Configuration
The Odoo Live Chat widget is a JavaScript snippet that embeds a chat interface on your website. The widget's appearance, behavior, and routing are fully configurable.
Creating a Live Chat channel: Navigate to Live Chat > Channels > New. Create a channel for each distinct chat function (General Support, Sales Inquiries, Technical Support). Each channel has its own agent pool, operating hours, and auto-responses. Your website can display different widgets for different pages — route visitors from the pricing page to the Sales channel and visitors from the documentation page to the Technical Support channel.
Widget customization: Configure the visual appearance of the chat widget to match your brand. Set the chat button color (use your brand primary color), the initial greeting text ("Hi! How can we help you today?"), the button position (bottom-right or bottom-left), and whether to show agent photos in the chat header. Professional widget branding signals to visitors that the chat is a real, staffed support channel rather than a generic bot.
Operating hours: Set the hours during which live agents are available under Channel > Configuration > Business Hours. When agents are online (inside business hours and at least one agent available), the widget shows as "Chat with us" with a live indicator. Outside business hours, the widget switches to "Leave a message" mode — visitors can still contact you, but their message is delivered as an email when agents are back online.
Automatic welcome message: Configure a welcome message that triggers automatically when a visitor opens the chat widget. "Welcome to ECOSIRE! I'm Alex from the sales team — how can I help you today?" This proactive greeting reduces the friction of starting a conversation and sets a friendly tone before the visitor has typed anything.
Website page targeting: Configure the chat widget to show only on specific pages (pricing, contact, checkout) or to show everywhere. Different messages and routing can apply to different page groups — visitors on the pricing page are likely evaluating a purchase decision, visitors on the support portal are likely existing customers with an issue. Tailor the channel and greeting accordingly.
Chatbot Configuration and Automation
Chatbots handle the first level of every chat conversation — qualifying visitors, answering FAQs, and routing to agents. Properly configured chatbots improve response times and reduce agent workload without sacrificing visitor experience.
Creating a chatbot script: Navigate to Live Chat > Configuration > Chatbots > New. Build the chatbot conversation as a script with a tree structure of questions and responses. The script builder is visual — add steps (questions), define what to do when a visitor selects each response option (next step, create lead, assign to agent), and branch the conversation based on their input.
Greeting and qualification flow: A typical chatbot flow for a B2B SaaS company might be:
- "Welcome! I can help you get started. Are you a new visitor or an existing customer?"
- (New visitor) → "What best describes your interest: Pricing, Product Demo, or Technical Question?"
- (Pricing) → "How many users would you need? (Fewer than 10 / 10-50 / 50+)"
- (50+) → "You qualify for our Enterprise plan. I'll connect you with an enterprise sales specialist right now." → Assign to Enterprise Sales channel
- (Fewer than 10) → Display pricing information and offer to connect
This flow pre-qualifies visitors, routes them to the right team, and answers common pricing questions without agent involvement for simple cases.
FAQ deflection: For common questions (What are your pricing plans? Do you offer a free trial? What integrations do you support?), create chatbot steps that display pre-written answers. If the answer resolves the visitor's question, they close the chat without needing an agent. If not, they can escalate to "Talk to an agent." Tracking deflection rates shows which FAQ answers are effective and which need improvement.
Lead creation from chatbot: When a visitor completes a qualification flow, configure the chatbot to automatically create a CRM lead from the conversation data. The lead includes: visitor name (if provided), email, the questions they answered, and the page they were on. This ensures no lead from the website chat is lost even if the agent doesn't respond before the visitor leaves.
Handoff to human agent: When the chatbot reaches a step requiring human judgment (complex questions, pricing negotiation, upset customers), configure a smooth handoff. The chatbot notifies the visitor that an agent will join, and assigns the chat to the appropriate channel. The agent sees the full chatbot conversation history when they join — no repeated questions.
WhatsApp Business Integration
WhatsApp has 2+ billion users worldwide, and in many markets (Middle East, South Asia, Latin America, Africa) it's the primary communication channel for both personal and business communication. Odoo 19 Enterprise's WhatsApp integration brings this channel into your unified inbox.
WhatsApp Business API setup: WhatsApp Business messaging requires a Meta Business Account and WhatsApp Business API access (through a Meta-approved Business Solution Provider). Navigate to Odoo > Settings > Technical > WhatsApp > Accounts to configure your WhatsApp Business Account. Enter your WhatsApp Business Account ID, phone number, and API token from Meta.
Message templates: WhatsApp has specific rules about when businesses can initiate conversations. Outbound messages (sent by you to a customer who hasn't messaged first) must use pre-approved message templates. Create WhatsApp templates for: order confirmation, shipment notification, appointment reminder, payment reminder, and support ticket update. Submit templates to Meta for approval — approved templates are available for outbound use within 1-3 business days.
Inbound message handling: When a customer messages your WhatsApp Business number, the message appears in Odoo's Discuss inbox automatically. The system identifies the customer by phone number and links the conversation to their Odoo contact record. Agents see the customer's history (previous orders, past support tickets, CRM notes) alongside the incoming message — providing full context from the first response.
24-hour session window: WhatsApp allows free-form replies within 24 hours of the customer's last message. Outside this window, only approved templates can be sent. Odoo tracks the 24-hour window for each conversation and warns agents when a conversation is approaching the cutoff. This encourages timely responses and helps agents know when they need to use a template.
WhatsApp for order and delivery notifications: Connect WhatsApp messaging to your Sales and Inventory modules. When a sale order is confirmed, an automatic WhatsApp message sends the order confirmation to the customer's WhatsApp number. When the delivery is dispatched, a shipping notification with tracking details is sent automatically. These automated touchpoints improve customer satisfaction without requiring agent time.
Unified Inbox and Omnichannel Management
The power of Odoo's messaging integration is the unified inbox — one place where every customer message, regardless of channel, is visible and actionable.
Discuss inbox: Navigate to Discuss to access the unified inbox. The left panel shows all active conversations by channel: Live Chat sessions, WhatsApp conversations, Email threads, and any other connected channel. Click any conversation to view the full message history and respond. The unified view eliminates the need to switch between tools — email, chat, and WhatsApp are all in one interface.
Conversation assignment: Assign conversations to specific agents from the conversation interface. Unassigned conversations appear in the team queue, visible to all team members. Configure automatic assignment rules that route conversations based on: message source (WhatsApp → WhatsApp team), customer segment (enterprise customers → enterprise support), or keyword detection (mentions of "billing" → billing team).
Internal notes: Add internal notes to any conversation — annotations visible to agents but not to customers. Use internal notes to document context ("Customer is on annual contract expiring next month — treat as high priority"), coordinate with colleagues ("@alice can you check if this is a known bug?"), or record actions taken ("Issued refund, confirmation sent to email"). Internal notes maintain team alignment without the customer seeing coordination overhead.
Customer profile sidebar: In every conversation, a sidebar shows the customer's complete profile: contact information, company, recent sales orders, active subscriptions, open support tickets, and CRM opportunity stage. Agents have full context without opening separate browser tabs or switching to other modules.
Conversation Routing and SLA
Efficient routing ensures conversations reach the right agent quickly. Slow routing increases response times and reduces satisfaction.
Channel-based routing: Configure routing rules under Live Chat > Configuration > Channels. Rules evaluate conversation properties (channel, keyword, customer tag, page URL) and route to a specific team or agent. A conversation from a customer tagged "VIP" routes to the dedicated account team; a conversation mentioning "invoice" routes to billing support.
Agent availability: Live Chat tracks agent availability in real time. When an agent closes the application or sets themselves as "Away," conversations are redistributed to available agents. Configure maximum simultaneous conversations per agent to prevent quality degradation when one agent handles too many chats at once.
Chat response time targets: Configure response time SLAs for each channel type. A live chat session might have a 2-minute first response target; a WhatsApp message a 4-hour response target. Track SLA compliance in the chat reporting dashboard. Conversations approaching their SLA deadline are highlighted in the agent queue.
Overflow management: When all agents are busy (maximum simultaneous chats reached), new visitors see an estimated wait time or are offered the option to leave an email. This queue management prevents visitors from waiting indefinitely and sets realistic expectations when immediate service isn't available.
Integration with CRM and Helpdesk
Live chat and WhatsApp conversations don't exist in isolation — they're part of customer relationships that span sales and support.
Creating CRM leads from chat: From any live chat conversation, create a CRM lead with a single click. The lead is pre-populated with the visitor's name, email (if provided), conversation summary, and the page they were browsing. The conversation is linked to the lead so the salesperson can review the full chat history before following up. This integration ensures every qualified inbound inquiry becomes a tracked opportunity.
Escalating to Helpdesk tickets: When a chat conversation reveals a support issue, convert it to a helpdesk ticket directly from the chat interface. The ticket inherits the customer information and the full conversation as its description. The customer is notified that their issue has been escalated to the support team with a ticket number. The chat conversation is linked to the ticket for cross-reference.
Proactive chat for at-risk customers: Use chat triggers to initiate proactive conversations with customers who exhibit at-risk behavior: spending more than 3 minutes on the cancellation page, visiting the competitor comparison page, or viewing their subscription options. The trigger initiates a chat with a personalized greeting from their account manager — turning potential churn signals into retention conversations.
Analytics and Performance Reporting
Chat volume trends: Navigate to Live Chat > Reporting > Chat Analysis. View conversation volume by day, week, or month — across all channels combined or filtered by Live Chat, WhatsApp, or other sources. Volume trends identify whether your messaging channels are growing or declining and correlate with marketing campaigns or product launches.
Response time analysis: Track average first response time, average resolution time, and SLA compliance rate by channel and agent. Compare response times across channels — if WhatsApp response times are significantly longer than live chat, that channel may need additional staffing.
Satisfaction ratings: After each resolved live chat conversation, automatically send a satisfaction rating request (1-5 stars or emoji rating). Track CSAT by channel, agent, and time period. Use low-rated conversations for quality review and coaching.
Agent performance: The agent performance report shows conversation volume, average handling time, CSAT rating, and SLA compliance per agent. Use this data for performance coaching — pairing each metric with sample conversation review for context-rich feedback.
Frequently Asked Questions
Can Odoo Live Chat work with mobile apps in addition to the website?
Yes. Odoo provides a Live Chat SDK for iOS and Android apps. Embed the SDK in your mobile app to provide in-app chat support — conversations are handled by the same agent pool and appear in the same Odoo Discuss inbox as web-based chats. This unifies support across web and mobile without requiring a separate support tool for each platform.
How does Odoo handle privacy and data retention for WhatsApp conversations?
WhatsApp conversations stored in Odoo are subject to your data retention policies. Configure retention rules under Settings > Technical > Data Retention. Customer phone numbers and conversation content can be anonymized after a configurable period. For GDPR compliance, customers can request deletion of their conversation data via a data deletion request processed through Odoo's privacy controls.
Can we integrate Odoo Live Chat with Facebook Messenger in addition to WhatsApp?
Odoo 19 includes Social Marketing integration that can route Facebook Page messages to the Discuss inbox. Configure the Facebook integration under Settings > Social Media > Facebook. Incoming messages from your Facebook Page appear alongside WhatsApp and live chat conversations. Responses are sent back to Facebook from within Odoo, with the full conversation context available.
How many simultaneous chat conversations can one agent handle effectively?
Research on live chat agent performance suggests 2-3 simultaneous conversations is the effective maximum for quality service. Above 3, first response times increase noticeably and quality suffers. Configure the maximum simultaneous conversations setting per agent to 3 (configurable individually for different agent experience levels). This protects quality while maintaining reasonable throughput.
Can the chatbot handle conversations in multiple languages?
Yes. Create separate chatbot scripts for each language you want to support. Use Odoo's language detection to route visitors to the appropriate language script based on their browser language setting or their response to an initial "Please select your language" question. Agent routing can also be language-based — route French-speaking visitors to French-speaking agents automatically.
How does WhatsApp integration work for outbound sales prospecting?
WhatsApp's business messaging rules only allow outbound messages to customers who have previously messaged your number (within the 24-hour window) or to numbers where you use pre-approved templates. For prospecting (messaging people who haven't reached out), WhatsApp is not the appropriate channel — it's designed for customer service and relationship management with existing contacts. For outbound prospecting, use email or LinkedIn.
Can we use Odoo Live Chat to support customers in different time zones with agents in different locations?
Yes. Configure multiple agent pools for different time zones. Use the operating hours configuration to route conversations to the active time zone's agent pool. When North American agents are offline, conversations automatically route to the European team. When European agents are offline, Asia-Pacific coverage takes over. This "follow-the-sun" model provides 24/7 chat coverage without requiring any single team to work unusual hours.
How do we train new agents on chat and WhatsApp handling without giving them access to sensitive customer data?
Use Odoo's role-based access control to create a limited-access role for trainee agents. Trainees can access the Discuss inbox and respond to conversations but cannot view financial records, full order history, or sensitive customer account data. Once certified, their role is upgraded to full agent access. Pair trainees with senior agents using the "barge-in" observation feature where the trainer can see all of the trainee's conversations in real time.
Next Steps
Odoo Live Chat and WhatsApp integration transforms customer communication from a scattered, multi-tool challenge into a unified operation with complete context, efficient routing, and measurable performance. When every channel feeds into one inbox and every conversation is connected to the customer's full history, your team can deliver consistent, personalized service at scale.
ECOSIRE implements Odoo Live Chat and WhatsApp integration for customer-facing businesses across industries. Our implementation includes widget configuration, chatbot scripting, WhatsApp Business API setup, team routing design, and agent training.
Visit our Odoo services page to explore live chat and messaging implementation options, or browse our marketplace modules for messaging extensions including advanced chatbot builders, WhatsApp campaign management, and multi-channel analytics dashboards for Odoo 19 Enterprise.
Written by
ECOSIRE TeamTechnical Writing
The ECOSIRE technical writing team covers Odoo ERP, Shopify eCommerce, AI agents, Power BI analytics, GoHighLevel automation, and enterprise software best practices. Our guides help businesses make informed technology decisions.
ECOSIRE
Transform Your Business with Odoo ERP
Expert Odoo implementation, customization, and support to streamline your operations.
Related Articles
Odoo vs NetSuite Mid-Market Comparison: Complete Buyer's Guide 2026
Odoo vs NetSuite for mid-market in 2026: feature-by-feature scoring, 5-year TCO for 50 users, implementation timelines, industry fit, and two-way migration guidance.
Tally to Odoo Migration 2026: Step-by-Step Guide for Indian SMBs
Tally to Odoo migration playbook for Indian SMBs in 2026: data model mapping, 12-step plan, GST handling, COA translation, parallel run, UAT, and cutover.
AI-Powered Customer Segmentation: From RFM to Predictive Clustering
Learn how AI transforms customer segmentation from static RFM analysis to dynamic predictive clustering. Implementation guide with Python, Odoo, and real ROI data.