Docs › Services/Helpdesk › Helpdesk All in One with WhatsApp and SMS

Helpdesk All in One with WhatsApp and SMS
A WhatsApp or SMS message to the team's number opens a ticket or lands on the open one, and the agent's reply goes back the same way. Installed by itself alongside Helpdesk and the Marketing Automation messaging add-on.
bambooforge_helpdesk_messagingKey facts
- Not for
- Carry pictures, voice notes or files. A message without text arrives as (empty message); the files of a reply are not sent.; Send outside WhatsApp's 24-hour window. WhatsApp takes a free-text reply only within 24 hours of the customer's last message; after that the provider refuses it, and the ticket says so in a note.; Reopen a closed ticket. A message after the close opens a new ticket.; Limit who writes in. Any number that writes opens a ticket.; Prove who sent a message. The gateway's address carries a secret; the provider's own signature is not checked.
- Manual last updated
- 2026-11-11
With Helpdesk and the Marketing Automation SMS & WhatsApp add-on on Odoo 20, a helpdesk team can take one of the add-on's gateways (Twilio or Meta) as its number. A message to that number opens a ticket or lands on the open one, and the agent's reply goes back to the number. It installs by itself when both apps are there.
This page is the complete manual: what comes in, how a number finds a customer, what goes out, and what happens when it does not.
Overview
For whom. A desk whose customers write by WhatsApp or SMS rather than by mail. It needs Helpdesk and the Marketing Automation SMS & WhatsApp add-on, on Odoo 20.
What it does
A number per team. On the team, WhatsApp / SMS Number takes one of the add-on's gateways.
In. A message to that number lands on the open WhatsApp or SMS ticket of the same number on the team, as the customer's message, and takes a waiting ticket back to the desk. Otherwise it opens a ticket: the first line is the subject, the number is on the ticket.
Out. Every reply the customer would read on such a ticket is sent to the number as plain text, and logged on the ticket's Messages sent tab with the provider's answer.
STOP. A message that is only stop, stopall, unsubscribe, cancel, end or quit opens no ticket: the add-on puts the number on Odoo's phone blacklist.
What it does not do
Carry pictures, voice notes or files. A message without text arrives as (empty message); the files of a reply are not sent.
Send outside WhatsApp's 24-hour window. WhatsApp takes a free-text reply only within 24 hours of the customer's last message; after that the provider refuses it, and the ticket says so in a note.
Reopen a closed ticket. A message after the close opens a new ticket.
Limit who writes in. Any number that writes opens a ticket.
Prove who sent a message. The gateway's address carries a secret; the provider's own signature is not checked.
What it needs
Helpdesk & Ticket Management for Community and the Marketing Automation SMS & WhatsApp add-on on Odoo 20.
A gateway under Automation > Gateways: Twilio (SMS or WhatsApp) or Meta's WhatsApp Cloud API, or Sandbox to try it without sending anything.
An address the provider can reach: the gateway's Inbound / webhook address is built from Odoo's web.base.url.
Concepts
Gateway. A Twilio or Meta account set up in the messaging add-on: one number, SMS or WhatsApp.
Channel. Where a ticket came from; WhatsApp and SMS tickets are answered by the number.
Messages sent. The log of every reply sent to the number from a ticket, with the provider's answer.
Install and first run
Install Helpdesk and the messaging add-on: this module installs by itself.
Expected: a team's form has WhatsApp / SMS Number; a ticket has a Messages sent tab when it is a WhatsApp or SMS ticket.
Under Automation > Gateways, set up the gateway, and paste its Inbound / webhook address into the provider's console (Twilio: the number's "A message comes in" webhook; Meta: the app's webhook).
Expected: the provider accepts the address; Meta checks it with the gateway's verify token.
On the helpdesk team, choose the gateway under WhatsApp / SMS Number.
Expected: a message to the number opens a ticket in the team, Channel WhatsApp or SMS.
Uninstalling
Uninstalling takes the number off the teams and the Messages sent tab off the tickets. The tickets and their conversations stay; the lines of the add-on's message log lose their ticket.
Flows
What comes in and what goes out.
A message comes in
The customer writes to the team's number.
If the number has an open WhatsApp or SMS ticket on the team, the message is added to it, under the contact's name when the number belongs to a contact, and a ticket waiting on the customer goes back to the desk.
Otherwise a ticket opens: subject from the first line (80 characters), description from the text, Channel from the gateway, the number in Contact Phone, and the contact the number belongs to, when exactly one contact has it. Without one, the number is the contact name.
The team's targets start, as for a mail.
Answer it
Answer in the chatter with Send message, a canned reply, or a suggested one. A note stays internal and is not sent.
The reply goes to the ticket's number as plain text, through the team's gateway.
Messages sent shows each reply with its state: Sent, then Delivered and Read as the provider reports them, or Failed with the error.
How it works
How a message reaches Odoo
The provider calls the gateway's Inbound / webhook address, /bf_messaging/inbound/<id>/<secret>; status reports come to its Status callback address. The secret in the address is all that is checked: the address must stay private.
A Twilio message comes as form fields (From, Body; whatsapp: is taken off the number); a Meta message as JSON, the number given a +.
A STOP word goes to the phone blacklist first. Any other text is handed to the team whose WhatsApp / SMS Number is that gateway; with two teams on one gateway, the first in the list.
How a number finds a customer
The number is compared with the contacts' Phone on its last nine digits, spaces, dots and dashes aside. A contact's number written with its country code (+ or 00) must have every digit the same.
One contact found: the ticket is theirs. None, or two contacts with the number: nobody, and the number stands as the contact's name.
An open ticket of the same number is found by the number exactly as the provider sends it.
When a reply fails
A reply the provider refuses is logged as Failed with the provider's error, and a note on the ticket says Could not send by WhatsApp: ... (or SMS). The reply stays in the chatter. The first-reply target runs again.
WhatsApp refuses a free-text reply more than 24 hours after the customer's last message.
A number on the phone blacklist is not sent to: the reply is logged as Failed, the number answered STOP.
Who reads and writes what
Agents read the Messages sent lines of the tickets they may read; the rest of the add-on's message log stays with Marketing Automation's users.
The gateways are set up by Marketing Automation's users. Whoever can read a gateway can read its addresses, secret included.
Inbound messages are written by Odoo itself, from the provider's call.
How we make sure it works
Before every release, 17 automated checks run against this app on Odoo 16, 17, 18, 19 and 20. Among them:
A note and the customers own words are not sent.
A twilio post opens a ticket and stop does not.
A log of no ticket stays with marketing.
Refused reply no answer.
Stop number not sent.
The complete list is in the source you receive.
For managers
Helpdesk > Reporting > Tickets groups the tickets by Channel: WhatsApp and SMS are two of them.
This add-on has no analysis or report of its own. No document prints from it.
Troubleshooting and FAQ
Could not send by WhatsApp: ... The text after the colon is the provider's error: a reply outside the 24-hour window, a wrong token, a number the gateway may not write to.
Nothing arrives. The provider's console holds the gateway's Inbound / webhook address, and that address is reachable from the internet.
A message arrives in the wrong team. Two teams share the gateway; give each team its own.
Questions people ask
What does a customer get when they write in? No automatic answer; the agent's first reply.
Can an agent start a conversation? No. A ticket starts from the customer's message.
Does it work with SMS only? Yes: a Twilio gateway set to SMS.
Support
Write to support@bambooforge.dev with your Odoo series and what the screen said.
Changelog
20.0.1.0.2
Every field has a help text.
This manual.
Reference
Generated from the module's own code (version 20.0.1.0.2, series 20.0) on 2026-11-12; every menu, field, setting, scheduled action, group, rule, report and endpoint below is read from the files, not written by hand.
Models
bf.helpdesk.team (extends bambooforge_helpdesk's bf.helpdesk.team)
Field |
Technical name |
Type |
Help |
Flags |
|---|---|---|---|---|
WhatsApp / SMS Number |
messaging_provider_id |
Many2one to bf.messaging.provider |
Messages received on this provider's number open tickets on this team, and replies go back through it. Give a provider to one team only: with two, the first team in the list gets the messages. |
bf.helpdesk.ticket (extends bambooforge_helpdesk's bf.helpdesk.ticket)
Field |
Technical name |
Type |
Help |
Flags |
|---|---|---|---|---|
Messages sent |
messaging_log_ids |
One2many to bf.messaging.log |
Every reply sent to the customer's number from this ticket, with the provider's answer: sent, delivered, read or failed, and the error. |
bf.messaging.log (extends bambooforge_ma_messaging's bf.messaging.log)
Field |
Technical name |
Type |
Help |
Flags |
|---|---|---|---|---|
Helpdesk Ticket |
helpdesk_ticket_id |
Many2one to bf.helpdesk.ticket |
The helpdesk ticket this message was sent from. Agents read the lines of the tickets they may read. |
Security
Access rules
Model |
Group |
Read |
Write |
Create |
Delete |
|---|---|---|---|---|---|
bf.messaging.log |
bambooforge_helpdesk.group_bf_helpdesk_user |
yes |
no |
no |
no |
bf.messaging.log |
bambooforge_helpdesk.group_bf_helpdesk_manager |
yes |
no |
no |
no |
Record rules
Rule |
Model |
Groups |
Domain |
Operations |
|---|---|---|---|---|
Messaging log: an agent reads what their tickets sent |
bf.messaging.log |
bambooforge_helpdesk.group_bf_helpdesk_user |
['|', '|', ('helpdesk_ticket_id.team_id.visibility', '=', 'all'), ('helpdesk_ticket_id.team_id.member_ids', 'in', [user.id]), ('helpdesk_ticket_id.user_id', '=', user.id)] |
read |
Messaging log: a manager reads what any ticket sent |
bf.messaging.log |
bambooforge_helpdesk.group_bf_helpdesk_manager |
[('helpdesk_ticket_id', '!=', False)] |
read |