Odoo Helpdesk manages the whole customer support cycle: from ticket creation to resolution, from SLA compliance to measuring satisfaction, up to after-sales actions. It integrates with Sales (billing the time spent on tickets), Inventory (product returns and repairs) and Timesheets (tracking support effort). This article describes what the module covers, how it is configured, which mistakes recur most often and how to decide between standard, configuration, integration and custom development. It refers to Odoo 20 Enterprise.
When an implementation is healthy
A support implementation works when five conditions hold:
- every support request enters Odoo as a ticket, with no parallel email inboxes or tracking spreadsheets;
- SLAs enforce response and resolution time commitments automatically;
- the customer rating is collected after every ticket is closed;
- tickets are resolved without leaving Odoo for email chains, WhatsApp or other tools;
- the team's workload and SLA compliance are visible in real-time reports.
The module covers six areas: teams (structure and routing), tickets (lifecycle, stages, priorities), SLA policies (response and resolution targets), the Help Center (self-service knowledge base and community forum), customer ratings and after-sales (returns, repairs, credit notes from tickets).
Module basics for people working in support
| View | Use in support |
|---|---|
| Kanban | Tickets by stage: the agent's daily working view |
| List | All open tickets with priority, team, assignee, SLA deadline |
| Form | A single ticket: full history, timesheets, SLA status, linked sales order |
| Pivot | Ticket volume by team, tag, period |
| Graph | SLA compliance trends, average resolution time, ratings |
The chatter of each ticket is the audit trail of the support interaction: the internal note for communication between agents, not visible to the customer; the message, a direct email to the customer from the ticket, with the whole thread logged; the activity, for a follow-up call, waiting for information from the customer or an escalation reminder. An example: a ticket is escalated after three days with no reply from the customer. The agent notes "Follow-up email sent. If no reply by Friday, close as unresponsive", schedules an "Email" activity for Friday and, if the ticket has the VIP customer tag, mentions the team lead.
Five principles
1. Team structure drives routing, not manual assignment. Every ticket is assigned to a helpdesk team, not directly to a single agent. The team defines: visibility (all internal users, invited internal users, customers from the portal), assignment (manual, random, balanced on workload), channels (email alias, website form, live chat, API), the SLA policies that apply to its tickets, timesheets (to track billable support time), after-sales (returns, repairs, credit notes from tickets) and customer ratings at closing. If every ticket is created and assigned by hand by a manager reading a shared inbox, automatic assignment and routing are not in use.
2. Stages represent the state of the work, not people. They say how far resolution has got, not whose ticket it is. The recommended stages: New (received, not yet triaged), In Progress (the agent is working on it), Waiting (awaiting a reply from the customer or information from third parties: if the stage is folded, it stops the SLA clock), Resolved (solution delivered, awaiting confirmation) and Closed (resolution confirmed; it is a folded stage and triggers the rating request). Tickets in folded stages count as closed for SLAs and ratings. Stages are shared across teams by default, or specific to one team.
3. SLAs are commitments, not aspirations. An SLA policy sets the maximum time between ticket creation and a target stage. Its fields: the team it applies to, the priority (only tickets with that priority, from zero to three stars), tags (only tickets with those tags), the target stage to reach within the deadline and the deadline in hours from creation, counted on the team's working-hours calendar. The SLA status on the ticket is In Progress (green, deadline not yet reached), Failed (red, the target stage was not reached in time) or Reached (grey, SLA met). Deadlines count working hours only, not calendar time: a four-hour SLA on a ticket created on Friday at 16:00 does not expire on Friday at 20:00. Without SLA policies there is no automatic enforcement of response commitments: compliance is measured by hand or not at all.
4. Customer ratings close the feedback loop. They are requested automatically when the ticket moves to a folded (closed) stage that has the rating email template. The values are Satisfied, Okay and Dissatisfied, and in the report they become a score from one to five (one dissatisfied, three okay, five satisfied). The email goes out by itself to the ticket's customer contact and the reply, with any comment, appears in the chatter and in the ratings report. The report shows the percentage per category over the period and lets you compare satisfaction across teams. Without ratings there is no systematic measure of support quality, only ticket volume and resolution times.
5. After-sales actions start from the ticket. Returns, repairs and credit notes started in answer to a support request must be linked to the originating ticket, for traceability. From the ticket, if enabled on the team, you can start: the return (creates a reverse transfer in Inventory, goods sent back by the customer), the repair (creates a repair order), the credit note (creates in Accounting a credit note linked to the ticket), the coupon (generates a discount voucher for the customer) and the field intervention (Plan Intervention creates a shift in Planning; the ticket shows a Scheduled button). The chain is ticket, after-sales action, inventory or accounting document. If returns and repairs are processed in Inventory or Accounting with no link to a ticket, support does not see the outcome of the cases it handles.
Configuration: channels, priorities, Help Center
Intake channels. The email alias (for example support@company.com) creates a ticket in the assigned team for every message, with a reply address set automatically, so the customer's replies continue the thread. The website form creates a ticket with the form fields as tags. Live chat can be turned into a ticket with one click. The customer portal lets customers create and follow their own tickets. A ticket can also be created directly in the app. Every channel has to route to the right team: a company with one alias for all requests but three teams (Technical, Billing, General) cannot route automatically, and needs one alias per team.
Priorities. Set on the ticket with stars: zero stars (default) is low, with the standard SLA; one star medium; two high; three urgent, with the tightest SLA and perhaps an immediate notification. SLA policies can target specific priority levels, and balanced automatic assignment takes priority into account.
Help Center. It has three components: the knowledge base (articles written by support, searchable from portal and website), the community forum (customers ask questions, other customers and agents answer) and eLearning (structured courses linked to help topics). Ticket deflection works like this: before submitting a ticket from the website form, Odoo suggests the relevant knowledge base articles, cutting ticket volume for common problems.
The flows
Standard ticket lifecycle. The ticket is born (email, form, portal or by hand) and is assigned automatically to an agent (balanced or random) or by hand. The agent investigates, notes and writes to the customer. If waiting for the customer, the agent moves the ticket to Waiting and the SLA clock stops. When the customer replies it goes back to in progress. Once the solution is delivered it moves to Resolved. On the customer's confirmation, or after N days, the ticket goes to Closed (folded stage) and the rating request goes out. The customer rates and the score appears in the chatter and the report.
When the SLA is about to expire. With less than an hour left, the ticket card in the Kanban turns orange and the agent and team lead are notified. Once the deadline has passed it turns red, the SLA status is Failed and the ticket appears in the SLA status analysis report. The team lead looks into the case: a staffing problem, a complex case, a routing error? The corrective action is documented in the ticket's chatter.
After-sales return. The customer reports a defective product with a ticket. The agent checks the details and from the ticket form uses Return. In Inventory the reverse transfer from Customer to Stock is created. The customer sends the product back, the warehouse validates the receipt, then a repair order is created (if needed) or the credit note is issued. The ticket is closed, the customer is notified and the rating is requested.
What changes with Odoo 20
Odoo 20 Enterprise is the baseline. Before classifying a need as development (Studio or custom), it is worth testing it against this feature.
- Field interventions from the ticket, planned in the Planning app. With Field Service enabled in the team's after-sales settings, Plan Intervention creates a shift, and a Scheduled button on the ticket shows the date and time of the intervention. Customers with portal access follow the intervention like the ticket. In Odoo 19 the same action created a task in a field service project.
For development requests the guidance is this: triage of a shared inbox, custom support portals, SLA statistics done by hand, sheets for dispatching technicians and after-sales sheets are first tested against the standard features of Odoo 20 Helpdesk, Planning (field service), Knowledge, Forum, Live Chat, Inventory and Sales.
The rationalisations you hear
| In the company they say | What it really is |
|---|---|
| "We handle support by email, it is simpler than a ticket system" | Email has no SLA tracking, no view of workload, no customer rating and no reports. Every manager who "checks the inbox" is doing by hand a triage that Odoo automates. |
| "We do not use SLAs because our response times vary" | Variability is exactly why they exist: they flag when it goes beyond the acceptable threshold. With no SLA there is no warning when a customer waits five days. |
| "Ratings are no use, unhappy customers do not answer" | Even a 20 per cent response rate is statistically significant. The distribution (percentage satisfied and dissatisfied) is worth more than the absolute number. |
| "We process returns in Inventory without linking them to a ticket" | A return without a ticket has no context: defect, wrong product, change of mind? With the link the loop between support and logistics becomes traceable. |
| "The knowledge base takes too long" | Five articles on the five most frequent questions cut ticket volume by 15 to 20 per cent, with about two hours of work once. |
| "Our team likes to assign tickets itself" | Manual assignment is a bottleneck at any scale. Balanced automatic assignment spreads the load objectively and takes the manager out of daily triage. |
Warning signs
- Support requests handled by email or WhatsApp: no tickets, no tracking.
- No SLA policy configured: commitments on response times are informal and unmonitored.
- All tickets in one stage, whatever the resolution state: stages are not used as a workflow tool.
- Tickets closed without customer confirmation: quality of resolution unknown.
- Customer ratings not enabled: no systematic measure of satisfaction.
- A single team for all kinds of support (technical, billing, general): no routing, mixed workload.
- After-sales actions (returns, repairs) not linked to tickets: no end-to-end view of the case.
- No knowledge base published: every common question generates a ticket.
- SLA breaches not reviewed: compliance failures are invisible to management.
- Timesheets not enabled on teams: billable support time is not tracked and cannot be invoiced.
How to verify a configuration
After configuring or assessing Helpdesk, verification goes through these checks:
- there is at least one team for each support area (technical, billing, general);
- there is an email alias per team and incoming emails create tickets automatically;
- the stages reflect the real resolution flow and folded stages trigger rating requests;
- SLA policies are defined for each team and priority level, with the working-hours calendar set correctly;
- automatic assignment (balanced or random) is configured and manual assignment is kept for exceptions;
- customer ratings are enabled on all customer-facing teams, with the email template on the closing stage;
- after-sales features (returns, repairs) are enabled on teams that deal with product problems;
- the Help Center has at least five articles published on the most frequent questions;
- ticket deflection is active: the website form suggests knowledge base articles before sending;
- the SLA status analysis report is reviewed every week and recurring cases investigated;
- the ticket analysis report is used to monitor how workload is spread across teams;
- timesheets are enabled if support hours are billed to customers.
Standard, configuration, integration or custom development
To compare the current process with what Odoo covers without customisation, the starting point is knowing what is standard: ticket intake from several channels (email alias, web form, live chat, phone entered by hand); ticket stages with automatic SLA timers and escalation rules; ticket assignment by team with round-robin or manual allocation; canned responses (macros) for frequent ticket types; the knowledge base linked to tickets and accessible from the portal; customer satisfaction ratings (CSAT) per ticket; integration with Sales and Invoicing for after-sales and warranty; timesheet logging on tickets (billable support).
Six questions help classify each gap before asking for development:
- How do customer requests arrive today? Email, phone, WhatsApp, web form, portal? Are they all tracked in one place? Mixed channels with no central tracking are a standard gap. The WhatsApp channel is an integration (WhatsApp Business API).
- Are SLAs defined and measured? What is the first-response and resolution target? Is there a penalty for breach? Undefined SLAs are solved with process change and configuration. If SLAs are contractual with penalties, you need configuration and Studio for reporting.
- How are tickets categorised and prioritised? Who decides, on what criteria, how fast? Informal categorisation is solved with Odoo ticket types and priority levels.
- Is there a knowledge base? Where does it live, who maintains it, do agents really use it? Knowledge scattered in emails or personal notes is standard. An external archive the company has invested in is an integration.
- How is satisfaction measured? A survey after closing, NPS, a periodic review or not at all? If not measured, it is solved with Odoo's CSAT. An external NPS tool is an integration.
- Is support billable? How are hours tracked, how are they invoiced? If not tracked, it is solved with Helpdesk timesheets and the billing policy.
The typical classification of the commonest cases is this:
| Common gap | Typical path | Signals that push towards custom |
|---|---|---|
| Tickets by email only, no tracking | Standard | An existing service desk with ITIL flows the company will not simplify |
| No SLA definition | Process change and configuration | Contractual SLAs with automatic penalty calculation |
| No knowledge base | Standard | A very large external archive with complex taxonomy and API dependencies |
| CSAT not measured | Standard | External NPS platform integrated into CRM reports |
| Support not billable | Configuration | Complex time-and-materials billing with several rate cards |
This article is an OIAR skill
What you have just read is the content of a skill from the OIAR catalogue, written for people. Knowledge like this, but richer and deeper, written for the agents, drives the interviews, the analysis and the report inside the platform. Skills are used in OIAR: to try this one on a project of yours you need an account.
odoo-helpdeskGuide to designing and assessing the Odoo 20 Enterprise Helpdesk module: teams and routing, ticket stages, SLAs, customer ratings, Help Center, after-sales (returns, repairs, credit notes, field interventions). It includes warning signs, the rationalisations heard in companies and the questions that decide between standard, configuration, integration and custom development. Use it when setting up or checking customer support in Odoo, with or without interviews with support managers and agents.