Open any busy record in Odoo — a sales order, a helpdesk ticket, a project task — and the chatter tells two stories at once. One is the human story: emails exchanged, notes left by colleagues, calls logged. The other is the machine story: field changed, stage moved, amount updated, follower added. Both stories matter, but they rarely matter to the same person at the same moment, and in a long thread they blur into a single scroll of noise. Odoo 20’s communication changes are not headline features like AI agents, but they are the kind of changes you feel every day: the chatter can now be filtered, CC recipients are visible where the conversation is logged, and the tracking machinery underneath the chatter has been rebuilt. This article walks through what changed, drawn from Odoo’s official release notes.
The chatter filter: conversations or tracked changes, on demand
The headline item is simple to state: in Odoo 20 you can filter the chatter to focus on conversations or on tracked changes. Instead of one interleaved stream, you can look at the thread through one lens at a time.
That matters because the two kinds of entries serve different jobs:
- Conversations are what people said: emails sent and received, internal notes, logged calls. This is what you read when you pick up a record someone else has been working on and need the context — what did we promise the customer, and when?
- Tracked changes are what the system recorded: a stage transition, a reassigned user, a changed date or amount. This is what you read when you are auditing — who moved this, and what exactly changed?
Before the filter, answering either question meant scrolling past the other kind of entry. On a record with months of history — a long-running opportunity, a ticket that keeps coming back — the audit trail buried the conversation and the conversation buried the audit trail. Filtering does not remove anything; it just lets each audience read its own story. For support and operations teams who live in the chatter, this is the single most useful communication change in the release.
Pin the message that matters
A companion change in the same spirit: important messages can now be pinned in the chatter. Every team has the one message in a thread that everyone ends up hunting for — the customer’s confirmation, the agreed price, the delivery instruction. Pinning keeps that message findable instead of relying on someone remembering roughly when it was sent.
CC recipients: added when you send, visible when it’s logged
The second upgrade fixes a quieter blind spot. The release notes list two related items under CC email recipients:
- You can add recipients in CC when sending an email from Odoo.
- Emails logged in the chatter now show who was added in CC.
The second item is the one with the longer shadow. Email sent through Odoo has always been logged on the record, which is the whole point of the chatter as a shared memory. But if the log did not show who was copied, the record told an incomplete story: a colleague reading the thread later could not tell whether the customer’s manager, the finance contact, or the external partner had actually seen the message. Follow-ups got duplicated, or worse, someone replied-all to a thread whose audience they had guessed wrong.
Showing CC recipients on the logged email closes that gap. The chatter now answers not just “what did we send?” but “who has seen it?” — which is usually the real question before you send the next message. Combined with the ability to add CC recipients at send time from within Odoo, email from a record behaves more like email from a mail client, without giving up the shared log that makes Odoo’s approach valuable.
Under the hood: tracking messages are now generated on the fly
The deepest change in this area is one most users will never see directly. In the Technical section, the release notes describe the new mail tracking framework plainly: tracking values have been removed; the tracking message is now generated on the fly. In earlier versions, when a tracked field changed, Odoo stored the old and new values as tracking data attached to the message. In Odoo 20, that stored layer is gone and the change message is produced when it is displayed.
Two practical consequences follow:
- Features built on tracking values were reworked, not dropped. The release notes state that all features linked to tracking values — they name burndown charts and stage duration — have been updated for the new framework.
- Custom code is the thing to check. Odoo’s own fact sheet for this release warns that custom code or reports reading tracking values directly must be adapted. If your reporting pulls stored tracking values out of the database, that query has nothing to read after the upgrade. The release notes do note an escape hatch: admins who still need tracking values can install a dedicated module.
Two smaller audit-friendly items arrived alongside: mail.mail records now specify the source of their content, to ease auditing, and changes to a user’s groups are now logged in that user’s chatter as well as in the console logs. None of this changes what the chatter looks like day to day — the filter is what users see — but it changes what the system stores, and upgrade projects should treat it as a technical checkpoint rather than a cosmetic one.
Around the edges: templates, mail plugins, and Discuss
Several smaller communication improvements round out the release:
- Email template preview. The preview interface has been improved and now allows navigation between records, so you can check how a template renders across several real records without leaving the preview.
- Mail plugins. From the Gmail or Outlook plugin, you can search for a contact, task, or helpdesk ticket and log your email in that record’s chatter, and when several people are part of a conversation you can select the relevant recipients.
- Digest emails. New KPIs have been added to the periodic digest emails.
- Discuss. Channels can be organised into categories and favourited; notifications can be marked as unread; polls can be created in conversations; Discuss calls can be recorded with summaries of what was said; and a user’s Discuss status shows when they are on a call through the Phone app.
Who feels the difference
The filter and the CC line sound like viewing options, but they land differently depending on the job. A support agent opening a months-old ticket no longer scrolls through dozens of stage-change entries to find what the customer actually said. A salesperson picking up a colleague’s opportunity can read the email thread as a thread — and check the CC line to see whether the customer’s finance contact has already seen the quote before chasing it. An accountant or auditor doing the opposite job — reconstructing what changed, in what order — can strip the conversation away and read the tracked changes as a clean sequence. Three audiences were sharing one scroll; Odoo 20 finally lets each of them read the version of the chatter written for them.
What to do with this on upgrade
None of Odoo 20’s communication changes require configuration to start helping: the chatter filter, visible CC recipients, and message pinning are simply there. The preparation work is on the technical side. Before upgrading, inventory anything custom that touches tracked changes — reports, automated actions, or integrations reading tracking values — and plan to rework it against the on-the-fly framework or the dedicated module. Then tell your teams the two habits worth forming on day one: filter the chatter instead of scrolling it, and check the CC line on a logged email before assuming who has seen what. Small changes, daily returns.
Further reading
- Odoo 20 Release Notes — Odoo — the General section (chatter filter, CC email recipients, pinned messages, mail plugins) and the Technical section (in-body tracking generated on the fly).
- Activities — Odoo 20.0 documentation — how the chatter, planned activities, and record threads fit together.
