Chatter Mail Manager

Name: Chatter Mail Manager
Brand: ECOSIRE
SKU: chatter-mail-manager

Key Features

Unified inbox-style list/kanban surface aggregating all `mail.message` chatter across configured models into one filterable queue

Per-user read/unread state via computed fields on `mail.notification`/seen data, so each user's unread count is private and does not mutate the shared record

Filter and search by author, source model, record, date range, message type (comment/note/email/notification), and subtype

Quick actions: mark read/unread, open source record, reply into the original `mail.thread`, archive from the working view

Reply-in-context posts back through `message_post`, preserving followers, subtypes, and email routing on the original record

Assign follow-up `mail.activity` records directly from a message row with due date and responsible user

Security enforced through `ir.model.access.csv` plus record rules — users only see chatter on records they are already permitted to read

Saved filter presets (optionally shared per team) stored as reusable search domains

Optional `ir.actions.server` / automated actions to route selected message types into a shared triage queue

Bulk quick-action buttons for multi-select mark-read / archive operations on large message batches

OWL-based frontend components for responsive list rendering and inline action feedback

Full XML-RPC / JSON-RPC exposure so external tools can read message state and trigger actions programmatically

Optional QWeb-rendered daily digest of unread chatter per user or per team

Built and tested against Odoo 17.0, 18.0, and 19.0, aligned to Community or Enterprise chatter behavior as applicable

Built to order, done for you

No DIY setup — a working app, built, installed and supported by ECOSIRE.

You order

Start with a one-time build price. We scope it with you at kickoff.

We build & install

ECOSIRE builds, configures and installs it on your Odoo.

Go live + support

You go live in about 2–4 weeks, with a post-launch support window.

About this Product

In standard Odoo, every note, log, and outbound email lives inside the chatter (mail.message) attached to an individual record — a sales order, a partner, a helpdesk ticket. That is fine until a team needs to work mail as a queue: find every message that mentions a customer, see what still needs a reply, or triage the day's inbound notes without opening fifty records one by one. Native Odoo gives you the Discuss inbox and per-record chatter, but it has no unified, filterable, read/unread-aware operations view over all chatter mail. Teams end up living in email clients that Odoo doesn't know about, and context gets lost. That is the gap Chatter Mail Manager closes.

We build a dedicated inbox-style workspace on top of the existing mail.message and mail.thread backbone. A new list/kanban surface (models.Model extending or aggregating mail.message, exposed through XML and OWL views) lets users read, search, and filter every chatter message by author, model, record, date, message type (comment/note/notification), and subject. A per-user read/unread state is tracked with a computed field (@api.depends on the user's mail.notification and message_seen state, or a dedicated relation where finer control is needed), so each team member sees their own unread count without mutating the underlying record for everyone. Quick actions — mark read/unread, open the source record, reply into the original thread, assign a follow-up activity (mail.activity), or archive from the working view — run as ORM methods with ir.model.access.csv and record rules enforcing that users only see messages on records they are already allowed to read. Filtering respects Odoo's security model end to end; we never widen visibility.

Because it is built on Odoo's own mail primitives, the module stays compatible with existing followers, message subtypes, and email routing, and everything remains reachable over the XML-RPC/JSON-RPC API for downstream automation or reporting. Optional extras we frequently scope: saved filter presets per team, automated actions that route certain message types into a shared queue, a QWeb-rendered daily digest, and bulk quick-action buttons. The base module targets Odoo Community; where a client runs Enterprise we align the UI with Enterprise chatter behavior and any Discuss add-ons in play.

This is a build-to-order engagement, not an instant download. After a short scoping call we confirm the exact models to cover, your read/unread semantics, security boundaries, and any integrations, then build against your target version (17.0, 18.0, or 19.0). Typical delivery is 2 to 4 weeks from confirmed scope, including UAT on a staging copy of your database before go-live. Pricing starts from $399 (indicative, single-company base scope); broader model coverage, multi-company record-rule complexity, custom automated-action routing, and extra integrations increase the quoted scope. You receive a fixed quote after the scoping call — never a surprise invoice.

What you get

Installable Odoo module source code (your version: 17.0, 18.0, or 19.0), packaged with a clean `__manifest__.py`

Installation and configuration on your staging environment, then production go-live

Technical documentation: models, fields, security rules, and extension points

End-user guide plus a live training session for your team

UAT on a staging copy of your database with a documented rollback plan

Post-go-live support window for defect fixes and configuration adjustments

Git repository handover with full commit history and tagged release

Configuration of covered models, read/unread semantics, and saved filter presets agreed during scoping

Who this is for

Shared-inbox operations teams

Support, order-processing, or back-office teams that treat inbound notes and emails as a work queue and need one place to see what is unread and unanswered across many records.

Odoo administrators and functional consultants

Admins who want chatter triage without ripping users out into an external email client, and need read/unread and quick actions that respect existing record rules and followers.

Team leads and managers

Managers who need visibility into message backlog, response coverage, and follow-up assignment across their team without opening records one at a time.

Operations / integration owners

Technical owners who want message state and actions reachable over XML-RPC/JSON-RPC to feed dashboards, SLAs, or downstream automation.

How Chatter Mail Manager Compares

Criterion	ECOSIRE	Custom Build	Competitor
Unified cross-record inbox view	Purpose-built inbox-style queue over all chatter	Possible but you design it from scratch	Generic message list, limited filtering
Per-user read/unread state	Private computed state, no record mutation	Depends on your build effort	Often global or read-only flags
Fit to your models and workflow	Scoped to your exact models and rules	Fully yours to specify and maintain	Fixed feature set, take it as-is
Security and record rules	Enforced via ir.model.access.csv + record rules	Your responsibility to get right	Varies; may not respect your rules
Delivery model	Built, installed, and supported by us	You hire and manage developers	Self-install download
Timeline	2-4 weeks from confirmed scope	Weeks to months, effort-dependent	Immediate install, no fit work
Support and handover	Support window + git repo handover	Only what you build internally	Vendor tickets, limited scope
Version coverage	Targeted build for 17.0/18.0/19.0	Whatever you build and test	May lag on newer versions

Frequently Asked Questions about Chatter Mail Manager

Is this an existing app I can download and install today?

No. Chatter Mail Manager is build-to-order. ECOSIRE scopes it to your models and security requirements, then builds, installs, and supports it for your database. There is no instant download.

How long does delivery take?

Typical delivery is 2 to 4 weeks from confirmed scope. The timeline depends on how many models you want covered, your read/unread semantics, multi-company complexity, and any integrations. We confirm dates in the fixed quote after the scoping call.

How does pricing and scoping work?

Pricing starts from $399 as an indicative single-company base-scope figure. After a short scoping call we confirm exact requirements and send a fixed quote. Broader model coverage, multi-company record rules, custom automation, and integrations increase the quoted scope.

What about support and updates after go-live?

Every engagement includes a post-go-live support window for defect fixes and configuration adjustments. You receive the full git repository, so your team can maintain it, and we offer ongoing support or version-upgrade work as a separate agreement.

Which Odoo versions and editions are supported?

We build against Odoo 17.0, 18.0, or 19.0 on Community or Enterprise. The base module runs on Community mail primitives; on Enterprise we align with Enterprise chatter and Discuss behavior where relevant. We target one primary version per engagement.

Will it respect our existing access rights?

Yes. Visibility is enforced through `ir.model.access.csv` and record rules. Users only see chatter on records they are already permitted to read — the unified view never widens access beyond your existing security model.

Does it change our records or followers?

No. Read/unread state is tracked per user without mutating the shared record, and replies post back through the standard `mail.thread` so followers, subtypes, and email routing stay intact.