AI Live Chat (BytesRaw)
AI agents answer website Live Chat visitors, with human hand-off
Visitors answered around the clock,
handed off when it matters.
AI Live Chat lets an AI agent answer the visitors on your website’s Live Chat — around the clock, in the visitor’s language, and with a clean hand-off to a real person the moment one is needed.
You assign an agent on a Live Chat channel rule, exactly where you would assign a scripted chatbot today. Sessions opened by that rule are operated by the agent, and because a bot can always answer, the chat button appears even when no human operator is online.
Everything about the visitor surface is built for zero trust. Only tools you explicitly flag Allowed for Visitors are ever offered to the model, those tools still execute as the anonymous visitor, and the endpoint that drives the agent is rate-limited per conversation and per IP address.
Answers Around the Clock
Website visitors get an immediate, on-topic answer at any hour, in the language of the page they came from, instead of a form or an “all operators are busy” message.
A Real Hand-Off, Not a Dead End
When the visitor asks for a person — or the agent genuinely cannot help — the bundled hand-off tool transfers the conversation through Odoo’s own Live Chat forwarding. The human joins, the bot leaves, and AI replies stop immediately.
Zero Trust on a Public Surface
Visitors are anonymous, so the agent’s tools are narrowed to a vetted allowlist and run with no implicit rights. The shipped agent’s prompt forbids revealing internal data or configuration and treats visitor input as a question, never as an instruction.
Public-facing AI,
built like it means it.
Eleven capabilities covering coverage, safety and cost — because a chat widget on the open internet is all three problems at once.
Assign an Agent on a Channel Rule
An AI Agent field appears on Live Chat channel rules, next to the chatbot script. Set it and every session matching that rule — by URL, country or visitor condition — is operated by that agent. The AI agent takes precedence when a scripted chatbot is also configured.
The Chat Button Shows With Nobody Online
Odoo shows the Live Chat button when a bot can answer. An AI agent counts as one, so your website keeps a working chat channel outside office hours instead of hiding the button.
Visitor-Safe Tool Allowlist
Server-action tools gain an Allowed for Visitors flag. On a live chat, the agent is offered only the flagged tools — the rest are not merely blocked, they are never exposed to the model. Flagged tools still execute as the visitor, so access rights apply on top of the allowlist.
Human Hand-Off Tool
The hand-off tool transfers the current conversation to an available operator using core Live Chat forwarding. The agent is detached from the channel so it stops replying, and when nobody is available the tool says so, letting the agent apologise and carry on helping instead of going silent.
Lead Capture
A visitor’s name, email and question are recorded as a CRM lead — validated, capped in length, one lead per conversation (repeat calls update the existing one), and acknowledged to the visitor without reading anything back to them.
Identity-Matched Order Status
The order-status tool requires both the order reference and the email used on the order, and returns only the status — never amounts, addresses or any other personal data. A failed match returns one generic message, so the tool cannot be used to probe which order references exist.
A Live Chat Agent, Ready to Assign
A purpose-built agent ships with the module: plain-text output (chat bubbles render no markup), short replies, a balanced tone, and a system prompt written for anonymous visitors. It is hidden from the internal messaging menu and the AI Workspace, because a public-facing agent is the wrong partner for a staff chat.
Language-Aware Replies
The visitor’s website language is passed to the agent, which replies in it unless the visitor writes in another language.
Rate Limiting on a Paid Model
The response endpoint is bounded twice — per conversation and per IP address — because bounding only the conversation invites opening a fresh session per request. A visitor that exceeds the window simply gets no reply, the same silent path as a closed session.
Knowledge and Guardrails
Because it is a normal BytesRaw agent, the live chat agent can carry skills: instruction packs plus indexed documents (product sheets, FAQs, policies) so it answers from your material. Its instructions tell it never to invent prices, stock or delivery dates.
Works in the Website Widget
The agent drives conversations in the website chat bubble and on the live chat support page. Replies are generated in their own request after the visitor’s message commits, so the chat stays responsive.
One field on a channel rule.
Assign the agent where you would assign a chatbot script — everything else is knowledge and guardrails.
Check the prerequisites
Odoo’s Live Chat app installed, plus a tested provider under AI → Configuration → AI Providers.
Wire the shipped agent
At AI → Agents → Live Chat, add at least one line on the Connections tab.
Give it knowledge
Create a skill under AI → Skills with your product information, FAQ and policies, and attach it to the agent.
Assign it to a rule
At Live Chat → Channels, open the Channel Rules tab and set the AI Agent on the relevant rule.
Check the tool allowlist
The three shipped tools are already flagged. To add your own, tick Allowed for Visitors in AI → Tools.
Tune the rate limits
The endpoint’s limit and window are adjustable through the rate-limit system parameters.
See it in action
Assigning the agent, and what the visitor sees.
Four workflows, end to end
Get the agent live, teach it your products, set up hand-off, then extend it carefully.
Put an AI Agent on Your Website Chat
Go from no coverage to answered visitors in a few minutes.
Teach It About Your Products
Stop the agent from guessing and make it answer from your own material.
Set Up the Hand-Off to Your Team
Make sure a visitor who wants a person actually gets one.
Add a Tool of Your Own
Extend what visitors can do — carefully.
Full transparency
The current limitations, stated plainly.
Cross-origin embeds are not wired up
The agent operates the website widget and the live chat support page, which are same-origin embeds. The cross-origin CORS loader — Live Chat embedded on a third-party domain — is not wired up in this version.
Two shipped tools depend on other apps
Lead capture needs CRM and order status needs Sales. Without them the tool returns a clear message telling the agent to apologise and offer a hand-off, so nothing breaks — the capability is simply unavailable.
The visitor flag is a security decision
Any tool you flag Allowed for Visitors is offered to a model driven by anonymous input. The allowlist controls exposure and the visitor’s own rights control execution, but a tool that internally elevates its own privileges is your responsibility to review.
Rate limiting is not a spend cap
It bounds how fast one visitor can make you call a paid model, but not the total. Set a Daily Token Budget on the provider connection for that.
Questions, answered
Quick answers to the questions buyers ask most.
Does this replace Odoo’s scripted chatbot?
It can. When both a chatbot script and an AI agent are set on the same rule, the AI agent takes precedence. You can also keep scripts on some rules and AI on others.
Can a visitor make the agent reveal internal data?
The agent is offered only the tools flagged Allowed for Visitors, and those run with the visitor’s own anonymous access rights. On top of that, the shipped agent’s prompt forbids discussing internal data, other customers or its own configuration, and treats visitor messages as questions rather than instructions.
What happens when nobody from my team is online?
The chat button still appears, because a bot can answer. If the visitor asks for a human and none is available, the hand-off tool reports it and the agent apologises and keeps helping — optionally capturing a lead so your team follows up.
Does the agent see who the visitor is?
Only what the visitor tells it. The order-status tool deliberately requires both an order reference and the matching email before revealing even a status, and never returns amounts or addresses.
Will it answer in the visitor’s language?
Yes. The website language of the session is given to the agent, and it replies in that language unless the visitor writes in another one.
How do I stop a runaway conversation from costing me money?
The response endpoint is rate-limited per conversation and per IP out of the box. For a hard ceiling, set a Daily Token Budget on the provider connection.
Can I use my own agent instead of the shipped one?
Yes — any agent can be assigned on a channel rule. Give it plain-text output and short replies, and remember that only its visitor-flagged tools will be offered.
Release history
A clean record of every release.
Bytesraw
🛠️ Need help?
Got a question, found a bug, or need a custom enhancement? Our support team responds within 24 hours on business days.
help@bytesraw.com →💼 Custom development
Need this module tailored to your workflow, or a brand-new Odoo solution? Let’s talk about your project.
info@bytesraw.com →| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Live Chat (im_livechat)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 7172 |
| Technical Name |
ai_livechat_bytesraw |
| License | OPL-1 |
| Website | https://www.bytesraw.com |
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