| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
AI (ai_app)
• Contacts (contacts) • Discuss (mail) • WhatsApp Messaging (whatsapp) |
| Lines of code | 9791 |
| Technical Name |
sati_chat |
| License | OPL-1 |
| Website | https://sati.com.py |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
AI (ai_app)
• Contacts (contacts) • Discuss (mail) • WhatsApp Messaging (whatsapp) |
| Lines of code | 9791 |
| Technical Name |
sati_chat |
| License | OPL-1 |
| Website | https://sati.com.py |
SATI Chat
The omnichannel chat suite that lives inside Odoo 19 Discuss. WhatsApp, Messenger, Instagram and Live Chat conversations stream into the same Conversations module your operators already use every day, with AI agents grounded in your own Knowledge articles handling volume under operator supervision.
An omnichannel chat suite, native to Odoo 19 Discuss.
SATI Chat brings WhatsApp, Messenger, Instagram and Live Chat into the same Conversations module your operators already use every day. Customer threads land as native Odoo channels. AI agents grounded in your own Knowledge articles handle the volume your team can't cover, escalate when they should, and work under operator supervision. The audit trail, permissions and reporting are the same ones you use for the rest of your business — because they are the same ones Odoo ships. You pay Meta and your AI provider directly under your own contracts. We don't sit in the middle.
Where SATI Chat lives in your Odoo. SATI Chat extends the native Conversations module: new entries appear inside Conversations → Conversations, Conversations → Reports and Conversations → Configuration, following the same Operations / Reports / Configuration pattern used by CRM, Sales, Account and other Odoo Enterprise modules. No new top-level menu in your navigation bar. Operators who already know Discuss can start handling customer conversations without learning a new interface.
Every conversation, every channel, every operator — in one Odoo-native kanban.
No new app to learn. SATI Chat appears as a new view inside Odoo's Conversations module: a kanban of every WhatsApp, Messenger, Instagram and Live Chat thread your team is handling, grouped by stage, with the AI agent already working under operator supervision. Same look, same shortcuts, same permissions as the Discuss your team already uses every day.
A native Odoo kanban view inside the Conversations module. Same shortcuts, same permissions, same reporting toolbox as the rest of Odoo.
The AI doesn't just reply. It carries the conversation to checkout.
A real multi-turn exchange between a customer and the Nimbus Assistant. The AI recognises intent, handles the color variant question honestly, surfaces the limited-drop price difference, sends the direct checkout link with promo code already applied, and closes the conversation warmly. Every claim is grounded in the Knowledge article assigned to this channel — the [1] citations after each AI message prove the answers come from your operator-curated content, not from the AI making up prices.
![SATI Chat conversation between Zoe Anderson and the Nimbus Assistant AI agent inside the Conversations module. Four-turn exchange: shipping inquiry to NJ, color variant question, sage green selection with direct checkout link, order confirmation. Every AI response carries citation markers [1] linking to the knowledge article that grounds the answer](http://apps.odoocdn.com/apps/assets/19.0/sati_chat/screenshots/01b_ai_conversation.png?dd24e50)
Real conversation against the Nimbus Retail Solutions demo. The citations [1] after each AI message link back to the Knowledge article that grounds the answer — verifiable, not invented.
What you actually get
Two close-ups of the moving parts: the multi-channel kanban already shown above (zoomed in on a single channel card so you can read the data) and the per-channel AI agent assignment with reply mode. The full walkthroughs of the operator workflow follow in their own sections below.
Every customer conversation across WhatsApp, Messenger, Instagram and Live Chat lives in the same Conversations module, with provider icons, stage columns, assigned operators, priority stars and connector tags visible at a glance. Operators stay in the workspace they already know.
Every channel uses a configured AI agent: choice of AI provider, response style, reply mode (copilot or autonomous), operating rules and the Knowledge articles that ground its answers. Owned, edited and audited by your team, not by us.
Your knowledge base is the AI's knowledge base.
The AI reads from the same Knowledge module your team already uses for internal documentation. Onboarding playbooks, support runbooks, commercial scripts, FAQs — the articles your team already writes become AI sources with one click. The same access rules that control who can read an article also control what the AI can use to ground its replies. No external service to set up, nothing to upload elsewhere.
The agent's Sources tab lists every Knowledge article connected to the AI. An Active toggle controls whether the AI can use it. The Indexed badge confirms the article is ready for the agent; Reprocess refreshes it when the article content changes.
The same article opened in Odoo Knowledge. Edited by humans, versioned by Odoo, ready for the agent. Update the article, click Reprocess, and the agent's next reply uses the new content. No re-deploy, no re-training.
Your knowledge stays in your Odoo. Same permissions, same audit trail, same backup policy as the rest of your business data. Add an article, the agent reads it. Archive an article, the agent stops citing it. No external cloud, no per-document fee, no separate knowledge base to maintain. Your operations team owns what the AI knows.
Autonomous when it's routine. Copilot when the operator decides.
The same AI agent operates in two modes depending on what each channel needs. Routine inbound (product questions, hours, shipping, stock) gets answered directly by the AI. Sensitive cases (complaints, refunds, ambiguous requests, VIP customers) are handled by the human operator — the AI briefs them internally with customer context, policies and tactical recommendations, and the operator writes the actual reply.
A customer reports a damaged package. The AI reads the conversation and posts an internal briefing for the operator: customer history, applicable policies cited from the Knowledge article, the resolution paths the policy allows, and a tactical recommendation based on customer value. The operator reads the briefing, makes the call, and writes the response to the customer in their own words.
Copilot is the AI working as an assistant to the operator, not as a ghostwriter for the customer reply. The customer never sees the briefing — internal notes stay internal. The operator stays in full control of tone, decision and wording.
A customer asks if you're open Sunday. The AI reads the business hours from your Knowledge article and answers directly through the provider: WhatsApp, Messenger, Instagram or Live Chat. The reply is logged in the channel, audited server-side, and visible to the operator who can take over with one click at any moment.
Autonomous mode handles the volume that doesn't need human attention: product questions, hours, shipping estimates, stock checks, FAQs. Out-of-hours? Define an AI schedule on the channel and the agent only replies inside the window you configured.
The two modes are not levels of trust in the AI. They are two different jobs. Autonomous mode is the AI doing customer service. Copilot mode is the AI assisting the human who is doing customer service. Switching between modes is a single setting on the channel — same agent, same knowledge sources, same audit trail.
Inbound, internal collaboration, public reply, real WhatsApp delivery
The same conversation followed through every layer: the customer message landing in the operator workspace, the operator consulting a colleague internally, the public reply leaving Odoo, and the customer's phone receiving the message. No staged screenshots, no mockups: one channel, four moments, zero leakage.
A message arrives from Instagram, WhatsApp, Messenger or Live Chat. The channel opens in the operator workspace, links the customer if recognised, and notifies the assigned team. Same Discuss your team already knows.
The operator switches to Internal note and
mentions a colleague with @ to confirm a
detail. The teammate gets a Discuss notification.
None of this reaches the customer.
The operator flips to Message, writes the public reply in their own words, and sends. The message leaves Odoo through the messaging provider. Delivery tracked end to end: sent, delivered, read.
The customer's WhatsApp shows the message from your company number, formatted as a regular WhatsApp text. The customer never knows there is an AI layer on your side.
One channel. Four moments. Zero leakage. The internal team sees views 1, 2 and 3. The customer sees view 4 only. The audit log preserves all four forever. Each audience stays on its right side of the line.
Operators stay in the workflow they already know. The composer is the same composer. The mention is the same mention. The internal note is the same internal note. SATI Chat adds the Invocar IA button and the AI agent your team configured. Everything else is the Discuss workspace your team uses every day.
One workspace. Every channel your customers actually use.
Each provider is a separate add-on. Install only the ones you need. Mix and match: keep one WhatsApp gateway for staff groups, run the official WhatsApp Business API on another number for compliance-sensitive customers, add Messenger and Instagram on top. One operator workspace for all of them.
WhatsApp via ApiChat.io
Fastest path to a working WhatsApp number. Group chats supported. Production-ready. Your team contracts the provider plan directly — no SATI middleman.
WhatsApp Business API (official)
Bridge with the native Odoo Enterprise WhatsApp module. Non-bannable, template-aware, ready for regulated industries. You own the Meta Business Manager account.
Facebook Messenger
Connected to your Facebook Page through Meta's official channel, with secure message handling and a Test Connection action to confirm everything is live. Production-ready, requires Meta App Review for live traffic.
Instagram Direct Messages
Same integration path as Messenger, scoped to Instagram Business accounts linked to a Facebook Page. SATI runs both in production against its own corporate handles.
Website Live Chat
Brings website visitors into the same workspace as your other channels. Same AI agent, same routing, same audit trail.
Add your own provider
The architecture is open: connect Telegram, SMS, Slack or any other channel into the same operator workspace with a focused implementation from your team or ours.
A note on Meta provider setup (Facebook Messenger and Instagram DM)
The Meta providers require onboarding on your side: a Meta Business Manager account with admin access to the Page or Instagram Business account, a Meta App created with the right messaging permissions, and Meta's App Review process for production traffic.
Expect 2 to 4 hours hands-on for a technically capable operator, plus Meta's App Review wait time when needed (typically 1 to 7 business days). SATI offers paid onboarding for customers who prefer assisted setup. Contact info@sati.com.py.
Customer-facing AI that does not invent.
Letting an AI talk to your customers carries real risks: it can invent prices, fabricate ticket numbers, slip from one client's voice into another, or keep replying when a human should have taken over. SATI Chat ships four protections that run on every reply — so what your customer receives is what your team approved.
No invented references
If the AI is about to send a ticket number, order ID or any internal reference, the system verifies that reference actually exists in your Odoo. If it doesn't, the reply is held back, a safe message is sent instead, and the original is logged for your team to review. Built after a real incident where an AI fabricated a reference number to a customer.
Different voice for different audiences
The same agent uses one voice when talking to your end customer and a different one when an internal team member invokes it from Discuss. With the customer it behaves as your brand representative. With your engineers it behaves as a technical assistant. One configuration, automatic switch.
Personas don't leak between customers
If you run support for multiple end-customers (multi-tenant operators, managed service providers), each customer gets their own AI agent with their own knowledge. When one agent is about to reply, the conversation history from other agents is filtered out. Each customer's AI persona stays inside their own world.
Human takeover, scheduled windows
Configure when the AI is allowed to reply: office hours per channel, per timezone, per weekday. The AI pauses automatically when the customer asks for a human, sounds angry, or mentions contractual terms (Spanish and English detection). One click Take Chat freezes the agent. Release hands it back.
If Odoo already does it, we use it.
SATI Chat is designed to extend Odoo 19 Enterprise, not to duplicate it. Marketing campaigns, message templates, conversational AI, translation and the operator workspace itself already exist as native Odoo modules. Below is what you keep using as-is when you install SATI Chat — every one of these is a module you've already paid for in Odoo 19 Enterprise.
Marketing campaigns
Use Odoo 19 Enterprise's native marketing automation and WhatsApp modules. Templates, scheduling, audience targeting, metrics. SATI Chat plugs into the same conversations, no separate mass-messaging module.
Message templates
The native WhatsApp module manages templates with Meta-approved variables, dynamic fields and PDF attachments. SATI Chat reuses that surface as-is — templates live under Conversations → Configuration, alongside Odoo's own Discuss settings. Operators never leave the Conversations module to send a template.
Keyword chatbots and IVR menus
The AI agent replaces 2020-era press-1-for-sales menu trees. It reads natural language, looks up information, opens tickets, creates leads. No menu tree to maintain.
Translator and audio transcription
The AI behind the agent already translates and transcribes natively. Modern providers (Gemini, Claude, GPT) handle this inline. No separate translation module needed.
Discuss workspace
We do not replace Discuss with a proprietary UI and we do not add a top-level menu. SATI Chat appears as new entries inside the native Conversations module, following the canonical Odoo pattern (Operations / Reports / Configuration). Every Discuss improvement Odoo ships in future versions lands in your SATI Chat for free.
Provider relationship
No SATI backend in the middle of your WhatsApp traffic. You contract Meta directly. You contract your WhatsApp gateway directly. You contract your AI provider directly. We do not act as a reseller and we do not charge a monthly cut.
Chat that becomes a lead, a ticket, a quote.
The conversation is just the start. Each bridge module auto- installs when the corresponding Odoo app is present and gives the AI agent the right tool to turn a chat into a structured record in the right place.
Helpdesk bridge
The AI can read existing tickets and open new ones from a conversation, with automatic deduplication so the same issue doesn't generate two tickets. Each helpdesk team can be scoped to its own knowledge sources. From an existing ticket, a wizard Pedir sugerencia IA proposes a response without entering the chat.
CRM bridge
Create CRM leads directly from a conversation, with contact, channel and message context already linked. The AI agent can open leads conditionally when a customer signals buying intent.
Sales bridge
Drag and drop products onto a chat to build a quotation draft right inside the conversation. The same draft is reused for follow-up messages so the conversation doesn't produce duplicates. The AI agent can convert customer intent into structured quote lines.
Every message sent. Every delivery confirmed. Every reply audited.
Know what your team sent, what reached the customer, and what the AI replied — for every channel, every operator, every day. Reports run inside Odoo with the same charts and filters your finance and sales teams already use. No second tool to learn, no dashboard subscription, no data leaving your Odoo.
Messages sent per operator per day, last 7 days. The same chart toolbox you use for sales, finance and inventory reports.
Operator productivity
Measure messages sent per operator, response time per channel, peak hours, response volume per shift. Know who is carrying the load and who needs support.
Delivery confirmation
Every outbound message keeps its delivery status from the messaging provider: sent, delivered, read, or failed. Failed messages keep the reason so your team can recover the conversation without losing the customer.
AI quality audit
Every AI reply is logged with the customer message that triggered it and the Knowledge article it cited. Review quality, spot patterns, refine the operating rules.
Use cases by area
Six configurations production-tested by SATI before this listing went live.
B2C customer support
Inbound WhatsApp on a single number, AI in copilot mode during office hours, autonomous out of hours, ticket creation on every reported issue, grounded in your Knowledge articles.
B2B sales pipeline
Messenger and Instagram inbound from ads, AI qualifies and opens a lead in CRM, the human sales rep takes over, the quote is built directly inside the chat with drag-drop products.
Multi-tenant MSP support
Managed service provider runs support for many end-customers. One AI agent per customer with its own knowledge. Routing rules assign the right agent on first inbound. Each customer's AI persona stays inside its own world.
Internal team copilot
Internal staff WhatsApp groups (admin, sales, ops) bridged into Discuss. The AI agent helps the team with policy questions, ticket lookups and record inspection. Customer traffic stays isolated.
Compliance-sensitive industries
Official WhatsApp Business API only (no unofficial gateways). Full audit trail. AI in copilot mode on every channel so every customer-facing reply goes through the operator. Built-in protections prevent the AI from inventing references.
Omnichannel retail
WhatsApp, Messenger, Instagram and website Live Chat into one sidebar. Same agent across channels. Catalog drag-drop on the chat. Sale order created from the conversation, paid through the Odoo portal link.
Install what you need. Pay once. Run on your own credentials.
The suite is modular. Start with the core plus one provider. The bridges to CRM, Sales and Helpdesk are sold separately on apps.odoo.com and install alongside their destination Odoo app when you add them to the scope.
| Module | Purpose | Install |
|---|---|---|
| sati_chat | Core: connectors (ApiChat.io + official WhatsApp Business API), channels, AI agent integration, audit trail | Manual |
| sati_chat_facebook | Facebook Messenger provider | Sold separately |
| sati_chat_instagram | Instagram Direct Messages provider | Sold separately |
| sati_chat_livechat | Website Live Chat bridge | Sold separately |
| sati_chat_routing | Rule-based auto-assignment of AI agents to channels | Sold separately |
| sati_chat_crm | Create CRM leads from a chat | Sold separately |
| sati_chat_helpdesk | Create tickets, per-team knowledge scoping, reply protections | Sold separately |
| sati_chat_sale | Build quotations and add products from a chat | Sold separately |
Technical specs
| Odoo version | 19.0 Enterprise |
| Core module version | v19.0.2.0.2 |
| License | OPL-1 with full source |
| Hard dependencies | mail, phone_validation, contacts, ai, ai_app |
| Supported AI providers | Any model exposed by the native Odoo ai module: Gemini 2.5 Pro / Flash, GPT-5, GPT-4, Claude Sonnet |
| Inbound message security | Cryptographic signature validation on every inbound webhook, per-connector enforcement policy |
| Languages shipped | English, Spanish (es_ES / es_PY), French, German, Italian, Dutch, Russian, Chinese |
| Vendor | Rapidsoft S.A. (SATI), Gold Odoo Partner |
| Support | info@sati.com.py |
Frequently asked questions
Why this if Odoo 19 already has a native WhatsApp module and a native AI module?
You do not need anything else for one-off campaigns or simple AI Q&A. SATI Chat is the bridge that connects those native modules into a single operator workspace, adds support for multiple WhatsApp providers, Facebook Messenger, Instagram and Live Chat, and ships the safeguards that customer-facing AI in production needs (verified references, audience-specific voice, scheduled hours, human takeover) but the base AI module does not include yet.
Do I have to pay SATI a monthly plan to use this?
No. SATI Chat is a one-time purchase per module. You pay your WhatsApp gateway (ApiChat, Meta) and your AI provider (Gemini, Claude, GPT) directly under your own contracts. We do not route your traffic through any SATI backend and we do not take a cut per message.
Can I run multiple WhatsApp providers at the same time?
Yes. You can connect as many providers as you need. SATI itself runs ApiChat for staff WhatsApp groups and the official WhatsApp Business API for compliance-sensitive customer numbers on the same Odoo instance. Each connector is independent.
What happens to existing channels if I upgrade the module?
Existing channels and customer message history are untouched. The upgrade only refreshes the code, the AI operating rules, and the reporting views. Your customer conversation history stays exactly as it was.
Which AI provider should I pick for the AI agent?
For customer-facing replies, we recommend the analytical tier of each provider: Gemini 2.5 Pro, GPT-5, Claude Sonnet 4.5 or 4.6. The lighter "flash / mini / nano" variants are fine for triage and quick lookups but tend to skip operating rules under load. Set the agent's response style to analytical on customer-facing channels.
Where does SATI Chat fit if I'm already evaluating other WhatsApp options?
SATI Chat occupies a specific niche: it extends Odoo 19's native AI agent rather than wrapping an external chatbot service, it reuses Odoo's native modules for marketing, templates and the Discuss workspace instead of duplicating them, and it routes traffic directly between your Odoo and the messaging providers (no SATI infrastructure in the middle). This works well for organisations that already invested in Odoo 19 Enterprise and want to keep their AI, knowledge and audit trail in the same place. Organisations looking for a fully-managed service with broker-routed traffic and monthly per-message billing typically find a better fit elsewhere.
How complex is the Facebook / Instagram onboarding?
The module installs in seconds. The onboarding complexity is on the Meta side and not something we can automate: a Meta Business Manager account, a Meta App with the right messaging permissions, and Meta's App Review process for production traffic. Expect 2 to 4 hours hands-on plus App Review wait time. SATI offers paid onboarding for customers who prefer assisted setup.
Is the source code available?
Yes. The module ships full source under the OPL-1 licence. You can read it, audit it, extend it subject to the licence. No obfuscated code, no hidden network calls, no telemetry leaves your Odoo instance. The only external calls go to the messaging providers and the AI provider you configured.
Does it run on Odoo Online (SaaS)?
Odoo Online does not support third-party modules. SATI Chat is compatible with Odoo.sh and on-premise Odoo 19 Enterprise.
Is professional support and onboarding available?
Yes. SATI offers implementation, AI agent prompt engineering, Meta Business Manager onboarding, internal training and custom connector development. Contact info@sati.com.py.
Try it on a live database
Use the Live Preview button on this page, or open demochat.satur.com.py and sign in with demo / demo. Open Discuss to see the omnichannel inbox and the AI agent in action.
What data is processed, and where
To deliver and answer a conversation the module processes the channel name, the contact name and phone or handle, and the message content. Messages are exchanged with the third-party messaging provider you connect (for example apichat.io for WhatsApp, or the official WhatsApp Business API) and, when AI auto-respond is enabled, with the AI provider you configure (Google Gemini, OpenAI or Anthropic).
You use your own provider credentials; SATI does not receive or store your conversations. For data-handling questions, contact info@sati.com.py.
Rapidsoft S.A. (SATI)
Your partner in Technology and Innovation. Gold Odoo Partner. Implementation, training, AI agent tuning and custom development on Odoo 19 Enterprise. We run SATI Chat against our own customer support and sales floor every day before it ships to you.
SATI CHAT
Multi-provider WhatsApp/Telegram/Instagram chat integrated with Discuss and AI agents
Overview
This module is part of the SATI Chat suite by Rapidsoft S.A. It integrates with Odoo Enterprise to provide AI-augmented multi-channel messaging for operations, sales and support teams.
Features
- Multi-provider chat connectors (WhatsApp, Messenger, Instagram, Telegram, SMS).
- AI agent auto-respond pipeline integrated with the native ai module.
- Per-channel and per-connector AI schedule, reply mode (internal note vs public reply), takeover detection.
- Internal notes via Discuss composer with explicit Invocar IA action.
- Regex-based routing rules for agent and helpdesk team assignment at channel creation.
- Outbound delivery tracking with provider-side status (queued, sent, delivered, read, failed).
Dependencies
- phone_validation
- contacts
- ai
- ai_app
Configuration
After installation, open Chat > Configuration to manage connectors, AI agents and routing rules. Each connector exposes the credentials, webhook URL and AI schedule applicable to its provider.
License
OPL-1. See the LICENSE file at the module root.
Support
Issues, feature requests and commercial enquiries: https://www.sati.com.py
Version
The current version is declared in __manifest__.py. This document is kept in sync with each release of the module.
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module