Odoo Helpdesk handles the fundamentals well — stages, SLA policies, a customer portal, a merge tool for duplicates. What it doesn’t do out of the box is the two things support teams actually ask us for: get tickets in cleanly from WhatsApp and email without a manual triage step, and stop a human from having to open every “where’s my order” ticket that a knowledge base article already answers.
Helpdesk is a genuinely capable stock app. The gap is almost never the module — it’s whether the stages, routing, and escalation rules match how your team actually triages, not a generic default someone left unchanged.
Kanban stages — New, In Progress, Solved, Cancelled — paired with SLA policies scoped by team, priority, or tag. Deadlines colour-code on the ticket itself, so an agent sees the clock without opening a report.
Multiple Helpdesk teams, each with its own assignment method — manual, random, or balanced load — and routing rules keyed on tag, priority, or the channel a ticket came in on.
Portal users see ticket status and history, reply and attach files without emailing back and forth, and rate the resolution on close — all without a separate login system to maintain.
Helpdesk tickets link to Knowledge or Forum articles, with suggested articles surfaced to the agent (and optionally the customer) at the moment a ticket is created — before anyone starts typing a reply from scratch.
The native merge tool combines threads from the same customer into one record, keeps the full message history, and notifies both requesters — so a ticket opened twice doesn’t get worked twice.
SLA breach triggers a stage change, a reassignment, or a notification to a team lead — configured per policy, not left as a single generic “overdue” flag nobody checks until the customer calls.
Helpdesk ships with clean email and portal intake. Live chat handoff works too. Anything else — WhatsApp, phone logs, a webhook from another system — needs a bridge built on top.
The recurring request: a customer messages on WhatsApp, and it needs to become a real Helpdesk ticket — not a separate conversation your support team has to remember to check.
Illustrative pattern — not a specific client, but the shape we see repeatedly once ticket volume outgrows what one or two agents can read individually.
To be direct about it: Odoo doesn’t currently ship an AI agent that reads a Helpdesk ticket, checks it against your knowledge base, and replies on its own. That capability — the part that actually reduces tier-1 volume — is something we build as a scoped, bespoke project on top of Helpdesk and Knowledge, not a native feature we’re configuring. We’d rather tell you that up front than let a sales deck imply otherwise.
We’ll look at your ticket stages, SLA policies, and intake channels, and tell you honestly what’s a configuration fix and what would need a custom build like a WhatsApp bridge or an AI autoreply agent. Within 5 business days you’ll have a written audit with a fixed-scope quote. No deck.