Unified Team Inbox for Odoo

The Unified Team Inbox is a made-to-order Odoo application we design and build for your specific mailboxes and workflow. Technically it is a set of custom models (models.Model with proper _inherit of mail.thread where it earns its keep) declared in a versioned __manifest__.py that depends on base, mail, fetchmail and contacts. Multiple IMAP/fetchmail incoming servers route into a single collaborative inbox, each mailbox bound to its own outgoing ir.mail_server so a reply to a support@ thread leaves as support@ with the right signature. Conversations are threaded automatically by parsing Message-ID, References and In-Reply-To headers so an entire back-and-forth reads as one thread rather than a scatter of disconnected emails. Every conversation carries an ownership state — assign, reassign, claim, or leave in an unassigned queue — surfaced through OWL/XML views as Kanban and list layouts per team, with a per-agent workload dashboard driven by stored compute fields and @api.depends. Real-time collision detection uses Odoo's bus to show who is currently viewing or replying, so two people never send conflicting answers.

On top of that spine we build the day-to-day tooling support and sales teams actually live in: public replies versus internal mail.message notes on the same thread with @mention collaboration; canned replies/snippets with dynamic placeholders (contact, company, related order) rendered at reply time; conversation statuses (open, pending, snoozed, closed) with snooze-with-reminder and follow-up scheduling via ir.cron and Odoo's automated actions; tags/labels and saved filtered views; SLA first-response and resolution timers with breach reporting exposed through QWeb/list reporting; and per-mailbox and per-agent signatures applied automatically on send. Every thread auto-links to res.partner, so an agent sees prior conversations and existing CRM or helpdesk context inline. Assignment automation rules — round-robin, or by tag or sender domain — distribute incoming mail without a human triaging the queue. Access is locked down with ir.model.access.csv plus record rules so agents see the right mailboxes and teams, and everything is reachable over the standard XML-RPC/JSON-RPC API for integration with your other systems. We target Odoo 17.0, 18.0 and 19.0 and build cleanly against Community, layering in Enterprise-only hooks only where your edition supports them.

Because this is build-to-order, nothing is downloaded and switched on today. After a short scoping call we confirm your mailboxes, teams, routing rules and edition, then design, build and test the module against a staging copy of your database. Typical delivery is 2–4 weeks from confirmed scope. You receive installable source code for your Odoo version, a documented git repository, install and configuration, UAT sign-off on staging with a rollback plan, and a post-go-live support window. Pricing starts from $549 (indicative, single-company base scope); the number of connected mailboxes, multi-company routing, deeper CRM/helpdesk integration, SLA and reporting depth, and any data migration of historical mail increase the quoted scope. You get a fixed quote after the scoping call — never a surprise invoice.