The shared inbox trap
Let me describe the system I see at almost every small business before they fix it. There's a shared email inbox -- support@, info@, help@, whatever. Three or four people have access. When an email comes in, someone is supposed to handle it. Supposed to.
What actually happens: Person A reads it and thinks Person B will grab it. Person B is swamped and assumes Person A handled it. Person C was on vacation. The email sinks. Two weeks later the customer follows up, angrier, and someone scrambles. Or worse -- the customer doesn't follow up. They just leave, quietly, and you never know why revenue dipped.
This isn't a people problem. Your team isn't careless. The problem is architectural: email was designed for communication, not for work tracking. An email has no owner, no status, no deadline, no history of who's touched it. It's a message in a pile. Asking a shared inbox to function as a ticketing system is like asking a group chat to function as a project plan -- the tool shapes the behavior, and the tool is wrong for the job.
Odoo Helpdesk fixes this without adding complexity, but only if you set it up right. Here's the setup that actually sticks, based on every implementation I've done.

1. Let the inbox become the ticket queue (automatically)
In Odoo: Helpdesk -- Configuration -- Teams -- set your email alias.
The single move that changes everything: point your support@ address directly at Odoo Helpdesk. Every incoming email automatically becomes a ticket -- customer info attached, subject as the title, full thread history preserved, attachments included. No more "can you forward that to support." No more "I thought you had that one." No more archaeological digs through CC chains to figure out what was promised.
The psychological shift matters more than the technical one, and I want to be clear about this because it's the real reason implementations succeed or fail. An email is something you read and feel vaguely guilty about. A ticket is something you own -- it has a number, a stage, an assignee, a timestamp. The moment a message becomes a ticket, it stops being ignorable. It sits in a queue, visible, aging, demanding action.
I've watched teams go from "we think we're keeping up" to "we know exactly what's open, who's working on what, and what's overdue" in the first week. Same people. Same workload. Same customers. The only thing that changed was visibility -- and visibility changed behavior without a single lecture about accountability.

2. Stages that match reality (not the manual)
Odoo ships with default ticket stages: New, In Progress, Solved, Cancelled. Most teams keep them exactly as-is and then wonder why the system feels useless after a month.
Here's why: those stages describe Odoo's generic idea of support, not how YOUR team actually works. If your process doesn't fit the stages, people stop updating them, and then the board is fiction, and then nobody trusts the system, and then you're back to the shared inbox with extra steps.
Your stages should mirror your actual workflow. For a typical small business, I recommend: New -- Triaged -- Waiting on Customer -- In Progress -- Resolved. Let me explain the ones that matter.
"Triaged" is the step everyone skips and everyone needs. It's the 30-second decision: is this urgent? Who should handle it? Is this actually a support ticket or a sales question in disguise? Without a triage stage, everything lands in "New" and sits there, because "New" doesn't tell anyone what to do next. Triage assigns ownership and priority. It's the difference between a pile and a queue.
"Waiting on Customer" is the stage that saves your metrics from lying to you. Every support team has tickets that are blocked -- you asked the customer for their order number three days ago, they haven't replied. Without a dedicated stage, those tickets sit in "In Progress," making your team look slower than they are and burying the tickets that actually need action. "Waiting on Customer" separates "we're working on it" from "we're waiting on them," which is honest and useful.
Rule of thumb I give every team: if a ticket sits in any stage for more than a week and nobody can explain why, your stages are wrong. Don't blame the team. Fix the stages. The board should tell a true story at a glance -- if it doesn't, the stages are lying, and people will stop looking.
3. SLAs: the follow-up discipline, in writing
In Odoo: Helpdesk -- Configuration -- SLAs.
An SLA (Service Level Agreement) is just a promise with a timer attached: "we respond to new tickets within 4 business hours," "we resolve standard issues within 2 business days," "urgent tickets get a response within 1 hour." Odoo tracks these automatically against every ticket and flags the ones approaching breach -- yellow warning, then red.
Small businesses almost always resist this step. "We're not a call center." "Our customers know us personally." "We don't need formal SLAs." I hear it every time, and I understand the instinct -- it feels corporate, impersonal, bureaucratic.
But here's the reframe that usually lands: the SLA isn't for the customer. It's for you. It's the system tapping your shoulder before a ticket goes stale, the automated version of the conscientious team member who remembers to follow up. The number one reason customers leave quietly -- not angrily, quietly, which is worse because you never learn -- isn't a bad product or a high price. It's feeling ignored. Feeling like their problem went into a void.
An SLA is how you make "we'll get back to you" a system instead of a hope. It's the difference between intending to follow up and actually following up, enforced by software that doesn't get busy, doesn't forget, and doesn't have a bad day.
Start generous -- I'd rather see an 8-hour response SLA you meet consistently than a 1-hour SLA you breach weekly. Breached SLAs train the team to ignore the warnings. Met SLAs build trust in the system. You can tighten them quarter by quarter once the team trusts the process. An SLA you meet beats an ambitious one you breach, every time.
The bottom line
Email is for communication. Tickets are for work. The moment you stop asking one tool to do the other's job, support gets calmer, customers get answers, and your team stops dreading the shared inbox.
Thirty minutes of setup. Three things most people skip. One monthly report. That's the whole system -- and it's the difference between "did anyone reply to that guy?" and knowing exactly where everything stands.
Frequently asked questions
Why do tickets get lost in small companies?
They live in personal inboxes and somebody's memory — no owner, no status, no history. They quietly never get answered.
What does Odoo Helpdesk change?
Every request becomes a ticket with an owner, a stage, and a deadline, tied to the customer record. The whole queue is visible at a glance.
Does a tiny team need a helpdesk system?
More than a big one does. With two people and no slack, one absence loses tickets.
What should I set up first?
One team, one pipeline with honest stages, and automatic assignment so nothing lands unowned. Add SLAs and automations after a month of real tickets.





