Answer the four questions customers actually ask on WhatsApp.

No call has ever been made to Meta from this module - there is no app, phone number id or token on our development account. Verified over real HTTP against Meta documented payload shapes: the verification handshake, signature validation, wamid idempotency, status transitions, the store-then-acknowledge split and every send refusal. The outbound body matches the documented structure, but nobody has watched Meta accept it. We would rather say so here than have you discover it after paying.

Core is sending: an outbound channel with a message log, templates and retry. It has no webhook and cannot receive anything. This is receiving and answering: a webhook, conversations, the 24-hour window, rules, lookups, handover and opt-out. Neither depends on the other and they keep separate records, so owning both is safe.

No, and none is required. It is a rule engine and says so - which is honest and also works better, because a numbered menu gets answered and a system that appears to understand gets sentences it cannot handle.

A phone-number match is not authentication, and a statement shows a customer entire position with you. The request raises a task; a person confirms identity and sends it.

A sentence is not an order. 20 of the blue ones becomes a draft with no lines and a task for sales, because pricing it automatically means guessing product, quantity and price on the customer behalf.

No, deliberately. The reply payload shape could not be confirmed from Meta published documentation, and this module does not parse structures from memory. The numbered text menu works on every client, needs no template approval, and accepts 2, status or the words.

Whichever you have enabled - it is Odoo own portal link, so it works with our Paymob module or anything else, and keeps working if you switch.

The module itself, for one Odoo instance, with no user limit and no expiry; every 18.0 release of the module, including security fixes; the module documentation, in the module and on this site; and defect fixes and help with configuration, at no extra cost and with no support plan required. It is a one-off licence for one Odoo instance, with no user limit and no expiry. It does not include installation on your instance, and configuration against your data; changes to the module for your own requirements; migration of the module or your data to another Odoo series; and work on your Odoo, your server, your network, or on other vendors’ modules.

No, and it is not hidden in the price either. Installation and configuration is a separate, optional service at $399 one-off. It covers remote installation on your instance; credential and endpoint configuration for the external service; and compatibility verification against your Odoo version and edition. If you or your partner install Odoo modules already, buy the licence on its own and skip it — most buyers of a module this size do.

Odoo 18, on Community and Enterprise. We do not claim a series until there is a branch for it, its tests pass on that series, and somebody has run it there — so the list on this page is what is actually supported rather than what is planned.

Twelve months of module updates, including security fixes; configuration support by email; priority handling: your ticket is looked at before unpaid enquiries; and help reproducing and reporting a defect, and a fix or a workaround. It runs for twelve months at $240 and is bounded by stated limits rather than by the word "reasonable": Up to 10 support requests in the twelve months; up to 4 hours of remote assistance in total; one Odoo minor-version upgrade of the module, within the same series; response within 2 business days, Sunday to Thursday, Cairo time; and covers the module. It does not cover your Odoo, your server, your network, or work on other modules.. The plan runs for 12 months from the day it starts and then stops. It renews only if you ask us to renew it — nothing renews automatically and no card is stored. It does not cover your Odoo, your server, your network, your backups, or other vendors’ modules; custom development or changes to how the module behaves; migration to another Odoo series — 18.0 to 19.0 is a project, not a ticket; on-site attendance, and work outside the hours below; and anything an external vendor charges for.

No, and this is the line worth being clear about. Defect fixes, at no charge, for the life of the 18.0 series; help when the module does not behave as its description says it does; answers to configuration questions about the module itself; and security fixes, released to everyone whether or not they hold a support plan — all of that comes with the licence, for every buyer, at no extra cost and whether or not a plan is ever bought. A paid plan adds updates, priority over unpaid enquiries and an allowance of assistance hours on top. It never takes anything away.

No, in any of the three options. A change to how a module behaves, a migration between Odoo series, and connecting a system we do not publish a connector for are each their own piece of work, quoted on their own. They are listed as exclusions on the cards rather than left to be discovered: they are the three things buyers most often assume are covered.

Use the buttons in the Pricing & Services section above. Both have a price, so the button takes you to a short form, shows you the total and what it covers before you commit, and creates a numbered order we reply to. No card details are taken on this site, and nothing is added to anything unless you choose it.