Odoo Helpdesk App Guide for Odoo 20: SLAs, CRM Leads and Auto-Close

This guide covers how Odoo Helpdesk really works in Odoo 20, setting by setting, and where our Odoo implementation services usually add value: SLA design, CRM routing and reporting.

It is written for support managers, operations leads and owners who already run Odoo or are choosing it. If your support team also sells, read it next to our Odoo CRM guide, because the ticket-to-opportunity flow joins the two apps.

Is Odoo Helpdesk an app or a support service?

Odoo Helpdesk is an app you use to support your own customers; Odoo support is a service you buy to keep Odoo itself running. Many searches mix the two, so the table separates them.

This article is about the app. If you need help keeping your Odoo database healthy, that is a different job, and our Odoo ERP support page covers it.

Which Odoo plan includes Helpdesk, and what does it cost?

Helpdesk comes with every paid Odoo Enterprise plan at no extra charge, but it is not available in Odoo Community. You pay per user, not per app.

On the Odoo pricing page, US prices billed yearly are US$31.10 per user a month for Standard and US$61.00 for Custom, with first-year prices of US$24.90 and US$49.00. In India they are Rs 725 and Rs 1,350. Both plans list Helpdesk among all apps.

The One App Free plan gives one app to unlimited users on Odoo Online. Helpdesk can be that one app, but watch the add-ons. Odoo's docs warn that after-sales and Help Center features install other apps, and a new app on a One App Free database starts a 15-day trial.

Helpdesk is not in the Odoo Community source code, so a Community database needs a third-party module instead. Our Odoo pricing guide explains the costs beyond licenses.

How do you set up an Odoo Helpdesk team?

A Helpdesk team is the unit everything hangs on: its pipeline, channels, SLAs and closing rules are all set per team. Most companies need two to four teams, not one per product.

Odoo's Helpdesk documentation puts the team form under Helpdesk, then Configuration, then Helpdesk Teams. A sensible first setup runs in this order:

1. Name the team and write a short description. The description shows on the public website form, so keep internal notes out of it.
2. Pick visibility. Choose private (invited internal users), company (all internal users) or public (internal users plus invited portal users).
3. Turn on automatic assignment and choose equal ticket counts or equal open tickets per agent.
4. Add team members, or leave the field empty to include every user with the right access.
5. Enable channels: email alias, live chat and website form.
6. Build the stages, and fold the stage that means "closed".
7. Switch on performance features: SLA policies and customer ratings.
8. Set self-service: automatic closing and closure by customers.

How do tickets reach Odoo Helpdesk?

Tickets arrive by email alias, live chat, website form or WhatsApp, and all of them land in the same team pipeline. You switch each channel on per team.

• Email alias: every new team gets an alias. The email subject becomes the ticket title, and the body goes into the description and chatter. On-premise databases need external mail servers for this.
• Live chat: an operator types /ticket during a chat, and the transcript becomes the ticket description.
• WhatsApp: the same /ticket command works from the WhatsApp app.
• Website form: Odoo builds a ticket form page that you can edit, add fields to and publish.

Per Odoo's guide to receiving tickets, creating a new user just to be a live chat operator can raise your subscription, because users count toward billing.

How do priorities and automatic assignment work in Odoo Helpdesk?

Priority is a 0 to 3 star field on each ticket, and it drives both the Kanban order and which SLA applies. Assignment then decides who gets the ticket.

Every new ticket starts at 0 stars. Because priority can be an SLA criterion, changing the stars can change the deadline, so agree who may raise a ticket to Urgent.

Automatic assignment skips agents on approved leave in the Time Off app. You can also dispatch by tag, such as Pricing or IT, to agents who own that topic. A ticket with no tag then stays unassigned, so add a catch-all rule or a daily check.

How do you set up an Odoo Helpdesk SLA?

An Odoo Helpdesk SLA is a policy that says which tickets it covers, which stage they must reach, and how many working hours they have to get there. SLA Policies are on by default for new teams.

Each policy in Odoo's SLA documentation applies to one team. Its criteria can include priority, tags, customers and, with Timesheets, services. Its target is a "reach stage", and you can exclude stages, such as "Waiting on customer", from the clock.

Three behaviors catch teams out:

• Priority matters even when blank. If a policy has no priority selected, it only applies to Low (0 star) tickets.
• The calendar decides the deadline. Deadlines use the policy's working hours, which default to the company working hours.
• Failure sticks. When the deadline passes, the SLA tag turns red and stays red, even after the ticket reaches the stage.

If a ticket matches several policies, Odoo shows the earliest deadline first. Keep policies few and clear.

How do you convert an Odoo Helpdesk ticket to an opportunity in CRM?

Open the ticket and click Convert to Opportunity; Odoo creates an opportunity in CRM, links the ticket in its chatter and archives the ticket. The button only appears when the CRM app is installed.

This is where support turns into revenue: a customer asking about extra seats belongs with sales, not in the support queue.

1. Open the ticket from the team pipeline or the ticket list.
2. Click Convert to Opportunity. If leads are enabled in CRM, the button reads Convert to Lead instead.
3. Choose the customer: create a new one, link an existing one, or do not link.
4. Pick the sales team and salesperson.
5. Confirm. The opportunity opens in CRM with the ticket linked in its chatter.

Because the ticket is archived, do not convert a ticket that still has an open problem; solve it first or log the sales interest as a CRM activity. Our Odoo CRM release notes for Odoo 20 show what the sales side gains this version.

How does Odoo Helpdesk auto-close tickets?

Automatic Closing moves tickets that have been inactive for a set number of days into a closed stage, 7 days by default. You find it in the team's Self-Service section.

Odoo's guide to closing tickets explains that a ticket counts as closed once it sits in a stage marked "Folded in Kanban". The gear menu's Fold option only hides the column for you; it does not close anything.

Set the In Stages field so only waiting stages auto-close. A good pattern is to auto-close from "Customer Feedback" after 7 days, and never from "New" or "In Progress", where silence means your team is stuck, not that the customer is happy.

The inactivity counter ignores the working calendar, so 7 days means 7 calendar days, weekends and holidays included. With Closure by Customers on, customers also get a Close Ticket button in the portal.

What can customers do in the Odoo Helpdesk portal?

Customers can view, reply to and close their tickets, rate your support, and search your Help Center, often without a portal login. The emailed "View the ticket" link works even without portal access.

Portal users see their tickets under My Account, then Tickets. The Help Center adds Knowledge articles, Forums and eLearning for self-service, but needs public team visibility and the website form.

Ratings go out when a ticket reaches a folded stage that carries the "Helpdesk: Ticket Rating Request" email template. Customers choose Satisfied, Okay or Dissatisfied and can add a comment, which lands in the ticket chatter.

What does Odoo Helpdesk reporting show?

Odoo Helpdesk ships three reports: Tickets Analysis, SLA Status Analysis and Customer Ratings. Each one opens as a pivot or graph you can regroup by team, agent, priority or tag.

Odoo's Helpdesk reporting guide notes that Hours Open uses calendar hours, while most other measures use working hours. Compare like with like in your dashboards.

What is new for Helpdesk users in Odoo 20?

The Helpdesk screens in Odoo 20 work much as they did in Odoo 19; the biggest change is that on-site jobs from a ticket now become Planning shifts. Odoo's 20.0 pages on SLAs, closing and reporting match the 19.0 pages.

Odoo merged the Field Service app into Planning. In the 20.0 after-sales documentation, the ticket button is now Plan Intervention, which creates a shift, and a Scheduled smart button shows its date and time.

Odoo Online got this merge in version 19.2; Odoo.sh and on-premise databases get it when they upgrade to Odoo 20. Our post on Odoo 20 field service in Planning covers what dispatchers must relearn.

The other after-sales buttons are still on the ticket: Refund (credit notes on posted invoices), Coupon, Return (reverse transfers) and Repair. Odoo 20 AI features run on Odoo AI IAP credits at EUR 1 per credit, so budget for them if agents use AI replies.

How do different industries use Odoo Helpdesk?

Every industry uses the same app, but the SLA, the channel mix and the after-sales buttons change. The table shows patterns we see most often.

Services firms can also bill support time: the track and bill time guide shows prepaid hours on a sales order going down as agents log timesheets. Not sure which apps you need next to Helpdesk? Try our Odoo app selector.

How iVentureTeam helps you set up Odoo Helpdesk

We set up Odoo Helpdesk around your real support process, so SLAs, routing and reports match how your team works. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists over 13+ years.

• Process mapping: teams, stages, priorities and closing rules agreed with your support leads first.
• SLA design: a short set of policies with working calendars, excluded stages and alerts.
• CRM handoff: clear rules for when a ticket becomes a lead or opportunity, and who owns it.
• Integrations: our Odoo integration services connect Zoho Desk, email tools or AI triage to Odoo.
• Training and reports: agent training plus dashboards for response time, SLA failures and ratings.

For an early budget and timeline, run the Odoo project estimate tool before we talk.

Odoo Helpdesk case study: LabMart

A healthcare SaaS company used Odoo Helpdesk for internal escalations, with an AI agent triaging tickets that arrive in Zoho Desk. LabMart operates in the USA and India.

Inbound tickets had grown four times year over year, and first-response SLAs had slipped from 2 hours to 18 hours. Two generic AI helpdesk tools had failed on the company's clinical terminology.

We wired an AI agent into Zoho Desk for tickets and Odoo Helpdesk for internal escalations, with Odoo CRM updated on every customer-impacting ticket. Anything below a 78% confidence score goes to a human, and specimen-safety tickets bypass automation entirely.

The agent went live in 7 weeks. It handles 1,800 tickets a week, auto-classifies 92% of them, and cut first response from 18 hours to 4.5 minutes. Read the LabMart AI ticket triage case study, or see our AI customer support automation service.

The bottom line on Odoo Helpdesk

Odoo Helpdesk is a full ticketing system that is already in your Enterprise subscription, and it pays off most when tickets connect to CRM, sales orders and stock. The settings are simple; the design choices are not.

Start with two or three teams, a few SLAs on working hours, auto-close only from waiting stages, and a clear rule for converting tickets. Review the SLA report weekly.

Ready to set up Odoo Helpdesk for your team?

Get a support workflow that your agents and your sales team will both use. Plan your Odoo Helpdesk rollout with us, call +91-90235-15208, or email business@iventureteam.com.