Skip to content

WhatsApp AI Commerce Agent

An AI sales agent on WhatsApp whose write tools are opt-in.

The short answer

WhatsApp AI Commerce Agent puts a conversational sales agent on your WhatsApp number, answering product questions, quoting and chasing abandoned carts, with the limits on what it may create written in code rather than asked for in a prompt. An agent with nothing configured gets read-only tools only. It is for a shop willing to sell on WhatsApp but not willing to let a stranger's text create records unbounded.

Request this module

Last updated

What it is for

You are letting a stranger's text drive your database. That is what an AI sales agent on a public channel is: a customer types a sentence, a model decides what to do with it, and what it decides may be to create a record in your system. Prompt injection is not a theoretical risk on that path, it is the normal traffic. Most integrations answer this by hoping the prompt holds. A system prompt is a suggestion to a model, not a permission. What actually bounds the damage is which tools the model can reach and what limits sit on them.

Platform
Odoo
Category
Connectors
Works with
Odoo 18 · Odoo 19
Technical name
whatsapp_ai_commerce
Status
Direct from webbox
Pricing
Paid

What is inside it

  1. 01

    Tool safety

    Seven tools ship in the registry. Five read and two write, and an agent with none explicitly enabled falls back to the five read-only ones, so creating a quotation or sending a payment link has to be granted.

  2. 02

    Agents

    An agent is a record: a provider, a system prompt, a tool list and a history depth. Hosted or local, and changing the model or the temperature is a form rather than a deployment.

  3. 03

    Cart recovery

    Three reminders at an hour, a day and three days, then it stops. The rule carries a discount ceiling and a code, so an agent that can negotiate cannot negotiate past the cap.

  4. 04

    The board

    The numbers that bound the agent, each enforced before a tool runs: how many tools write, what an unconfigured agent gets, the line and quantity caps, the hourly quotation limit, and where the reminders stop.

What it looks like in practice

  1. An agent is created and its tool list is left empty

    Nobody has chosen which of the registry's tools this agent may reach, and the Enabled Tools field on the record is blank.

    It falls back to the five read-only tools: search products, product detail, check stock, recommend and order status. The two that touch real records have to be added by hand, per agent.

    Read-only tools
    5, on by default
    Write tools
    2, opt-in

    Figures from the module's own demo data, on a fresh install. Install with demo data and open the storefront agent, then read its empty Enabled Tools list.

    Tool safetyAgents

  2. A shopper talks the agent into ordering ten thousand of something

    The conversation has persuaded the model to quote a quantity nobody would approve, and the quotation tool is one this agent was given.

    The quotation is capped at 20 lines and 100 per line, checked before the tool runs, and quotations per hour are limited as well. The model never sees the arithmetic that stops it.

    Quotation lines
    20
    Line quantity
    100
    Quotations per hour
    12

    A default you can change.

    Tool safetyThe board

  3. A cart is abandoned and gets three messages, then nothing

    A shopper leaves items behind. Left to itself, a recovery rule would keep chasing them for as long as somebody kept raising the number.

    The rule fires at 60, 1440 and 4320 minutes and stops at three reminders. Its discount ceiling and code travel with it, so the agent cannot offer more than 10% however persuasive the conversation gets.

    Step delays
    60, 1440 and 4320 minutes
    Maximum reminders
    3
    Discount cap
    10%

    A default you can change.

    Cart recovery

What it deliberately does not do

No model is included
You bring a provider and a key, or you run Ollama yourself. This module ships no inference, no credits and no hosted endpoint, and its price does not include any.
Requires WhatsApp Connector
The transport, accounts, conversations, messages and templates all live in that module, which is free and must be installed alongside this one.
Not a chatbot builder
There is no flow designer and no decision tree. An agent is a prompt, a tool list and limits.
No payment processing
The payment-link tool sends a link. Taking the money remains between your provider and the customer.

Questions

Can I install this on Odoo Online?
No. Odoo Online cannot install modules that contain Python, so this runs on Odoo.sh or a self-hosted instance. Check the versions listed above for the series and edition it is verified against.
Does the price include the AI?
No. No model is included and no credits are either. You bring an OpenAI-compatible or Anthropic provider with your own key, or you run Ollama yourself, and nothing works until that provider record exists. The module ships no inference and no hosted endpoint.
Can it run without the WhatsApp Connector module?
No. The transport, the accounts, the conversations, the messages and the templates all live there. That module is free and Odoo pulls it in as a dependency, so the two are installed together and there is nothing extra to buy for it.
Can I design the conversation flow?
Not as a flow. There is no designer and no decision tree here; an agent is a provider, a system prompt, a tool list and a history depth, all on one record. If you need branching scripts rather than a model answering, this is the wrong shape.

Have something to build?

Tell us the problem. We'll come back with a plan, a price, and who'd actually build it.

  • Free scoping call
  • Reply within 1 business day
  • No lock-in