Short answer: Most Odoo Helpdesk problems are not bugs. They come from a handful of settings that look harmless: a stage that was collapsed instead of folded, an auto-close rule pointed at the wrong stages, priority stars that quietly switch SLAs on or off, and customers created twice. Each of these is documented, and each can be fixed from the team form, so the cheapest cure is knowing where they hide. This is a checklist of those places, not a list of rules.
Applies to
- Odoo version: Odoo 19. I read the same Helpdesk pages in the 20.0 documentation; the settings below are described identically there.
- Edition: Enterprise only, because Helpdesk is an Enterprise app. Everything is taken from the documentation.
- Apps: Helpdesk, with notes on CRM, Data Cleaning, Time Off and the Contacts records customers are linked to.
Why does a solved ticket still look open?
Because folding a column and closing a ticket are different things. In a team’s pipeline, the gear icon on a stage offers Fold and Edit. Fold only tucks the column away for tidiness. A ticket is treated as closed when its stage has Folded in Kanban ticked in the stage settings, which you reach through Edit.
This matters beyond looks. Ratings, reports and the “closed” filter all depend on the same idea. If the stage is wrong, the numbers are wrong too, and you will not notice until someone asks why Tickets Analysis shows nothing closed.
Is Automatic Closing safe to switch on?
Only if you aim it. Under Self-Service, Automatic Closing moves tickets to a chosen stage after After days of inactivity, which starts at 7. Two details cause trouble.
First, the count ignores the working calendar, so a Friday ticket and a long weekend burn days the customer never saw. Second, if you leave In Stages empty, the rule is not limited to the stage where silence is expected. The docs use the example of a Customer Feedback stage: a ticket waiting on the customer can close itself, but a ticket sitting in New or In Progress means your team is behind, and closing it would hide that.
What do priority stars have to do with SLAs?
More than most teams realise. Priority is an SLA criterion. The policy applies only once the ticket’s stars match, and a policy with no priority selected applies only to Low tickets. Change the stars later and the SLA deadline can change with it.
A related surprise: once an SLA tag has turned red, it stays red even if the ticket later reaches the Reach Stage. The documentation is explicit about it, and it is worth telling agents, because many expect the tag to clear.
Who gets the ticket when nobody is assigned?
If Automatic Assignment is set to Dispatch tickets based on tags, a ticket with no tag stays unassigned. The options based on workload do not have this gap. Also, assignment skips people with time off scheduled in the Time Off app, so on a small team, make sure leave is recorded properly or tickets will pile on whoever remains.
Why are customers duplicated, and tickets too?
Two separate problems with the same root: nobody decided what counts as the same customer.
When a ticket is converted to an opportunity (needs the CRM app), the pop-up asks you to Create a new customer, Link to an existing customer or Do not link to a customer. The first one is the quick one and the one that adds duplicates to Contacts. I would link whenever the person already exists. Remember that the ticket is archived after conversion, with a link left in the opportunity’s chatter.
For duplicate tickets, Helpdesk ‣ Tickets ‣ All Tickets, then Actions ‣ Merge, lists the selected tickets with a similarity rating. The action only appears if Data Cleaning is installed.
When this advice fits and when it doesn’t
It fits any team running Helpdesk with more than one person and some stage logic. It does not fit if you are still deciding whether to use Helpdesk at all; the overview of Odoo Helpdesk is the better start. And if you have no SLAs, ignore the priority section.
A worked example
A stationery wholesaler runs stages New, In Progress, Waiting for Customer and Solved. Its manager ticks Automatic Closing, moves tickets to Solved after the default days of inactivity and, wanting to be careful, leaves In Stages blank.
A buyer reports damaged boxes on Thursday. The agent is busy, the ticket sits in New and, after a long weekend, closes itself with no reply. The fix is two clicks: limit In Stages to Waiting for Customer. The team now sees stuck New tickets as a staffing issue rather than losing them.
Common mistakes
- Fixing settings in the middle of a busy day. Changing visibility away from public removes portal users as followers from tickets, so do it when you can check the result.
- Putting internal notes in the team description. It is published on the website form.
- Enabling extra features to see what happens. After-sales and Help Center options can install other modules, which has licence consequences on a One-App-Free database.
- Treating the Ratings request as a reminder. The rating email belongs on a folded stage only.
Related
- How to set up Odoo Helpdesk walks through where each of these settings lives.
- Common Odoo CRM sales mistakes covers the data-quality side of the same habit: duplicates and stale records.
There is a longer screen by screen walkthrough of this on sajjalbajaj.in.
Official references
How this article was checked: I read the Odoo 19 Helpdesk, SLA, ratings and closing pages, compared them with the 20.0 versions, and checked each setting name against the text. I did not run a live Helpdesk database.
If you want a second pair of eyes on a support set-up, take a look at my work page.