Odoo Service Desk Setup Guide: Teams, Tickets, SLAs

Odoo Helpdesk is an Enterprise-only app for managing customer support tickets. It integrates with your sales, inventory, and CRM workflows. If you're on Community Edition, you'll need an open-source alternative like the OCA Helpdesk module. This guide walks you through setting up Odoo Helpdesk: creating teams, configuring channels, managing ticket stages, and enabling self-service portals.

What Is Odoo Helpdesk? (Enterprise-Only)

Odoo Helpdesk is a built-in application for managing customer support tickets. But there's a catch: it's only available on Enterprise Edition. Community Edition does not include it.

Helpdesk gives you a unified inbox for customer issues. Tickets arrive from email aliases, website forms, live chat integrations, and API calls. You manage them in a kanban board, assign them to team members, track response times with SLAs, and close them with a survey.

The real value comes from integration. A ticket can trigger inventory returns (RMA), generate repair work orders, create refunds as credit notes, spawn CRM opportunities for upsell, or link to a specific project. If you're already using Odoo's sales, inventory, or CRM modules, Helpdesk becomes the spine that connects customer support to the rest of your operations.

Key features:

• Multi-channel ticket capture (email, web form, live chat, API)
• Kanban board with customizable stages
• Automatic ticket assignment by workload or tags
• SLA tracking with configurable response and resolution times
• Customer self-service portal
• Email templates and automation rules
• Integration with Returns, Repairs, Refunds, CRM, and Projects

If you're using Odoo Community Edition or evaluating whether Helpdesk makes sense for your team, read on to understand the deployment options and what alternatives exist.

Before You Start: Self-Hosted vs Cloud Deployment

Odoo Helpdesk deployment options depend on your infrastructure preferences and cost sensitivity.

Odoo Online is the easiest entry point. You pay per user per month, get automatic updates, and no infrastructure headaches. Downside: per-user pricing scales quickly once your team grows beyond 10 people.

Odoo.sh is Odoo's managed hosting platform. It sits between Odoo Online and self-hosted: you pay a monthly fee for the database, but you control add-ons and customizations. Good for teams who want managed infrastructure without the SaaS per-seat model.

Self-hosted Odoo gives you the most control and often the lowest total cost. You manage the server, apply updates, configure backups. If you choose self-hosted, you'll need a hosting provider. Opsily offers managed self-hosted Odoo hosting designed for teams your size. You get unlimited users, which means Helpdesk scales without additional license costs. For a 10-15 person support team, self-hosted Odoo typically costs less per user than Odoo Online because there are no per-seat fees.

The trade-off: self-hosted requires you to own deployment and backup responsibility. Many teams find the operational control and cost savings are worth it. Visit our Odoo hosting guide to compare all three deployment models in detail.

Step 1: Create Your Helpdesk Team

Creating your first Helpdesk team is straightforward.

1. Open the Helpdesk app from your Odoo main menu.

2. Go to Configuration > Helpdesk Teams.

3. Click New.

4. Fill in the basic info:

   • Team Name: e.g. "Customer Support", "Technical Support", "Billing Support"
   • Description: A short note on team scope
   • Company: The legal entity this team serves
   • Team Lead: Assign a manager (optional)

5. Set Visibility:

   • Private: Only invited internal users see tickets
   • Company: All internal users in the company can see tickets
   • Public: Internal users + invited portal customers can see tickets

6. Configure Assignment:

   • Manual: You assign tickets by hand
   • Balanced: Odoo distributes tickets equally across team members
   • Balanced on Open: Assigns to the person with the fewest open tickets
   • By Tags: Routes tickets based on custom tags (e.g., billing tickets to the billing team)

7. Add Team Members: Select users who will handle tickets.

8. Save.

That's it. Your team is created. Now tickets can be routed here once you configure channels (email, web form, live chat). If you skip assignment rules and choose Manual, every ticket lands in the Helpdesk inbox and waits for someone to pick it up. Most teams start with Manual and graduate to Balanced or By Tags as volume grows.

Step 2: Set Up Multi-Channel Ticket Capture

Tickets come from four sources: email, web forms, live chat, and direct API calls. Most teams start with email.

Email Aliases (Fastest):

1. Go to Helpdesk Team > Channels.
2. Click New Channel or select Email.
3. Enter an email alias for this team, e.g., support@yourcompany.com, billing@yourcompany.com.
4. Odoo automatically creates tickets from emails to this address.
5. Set a default team (if multiple teams are in scope).

You must configure your email provider (Gmail, Microsoft 365, a mail server) to forward emails to Odoo. The documentation has provider-specific steps.

Website Forms:

1. Go to Helpdesk Team > Channels > Website Form.
2. Odoo auto-generates a contact form.
3. Add it to your website under /helpdesk/form or embed via iframe.
4. Customers fill in the form, hit submit, and a ticket is created.

The form captures name, email, subject, description, and custom fields you add (e.g., product, issue type). Responses are linked to the customer's contact record in Odoo.

Live Chat:

1. Install the Live Chat module (if not already enabled).
2. Link Live Chat to Helpdesk under Helpdesk Team > Channels > Live Chat.
3. When a chat ends or is escalated, Odoo converts it to a Helpdesk ticket.

For a small support team, start with email. Email is reliable, customers are familiar with it, and setup takes 15 minutes. Web forms and live chat add overhead and should be added once your team is running smoothly with email.

Step 3: Configure Automatic Ticket Assignment

Automatic assignment prevents the bottleneck where all tickets land with one person. Three methods exist.

Equal Count: Every new ticket goes to the team member with the fewest total tickets assigned. Simple but crude. If Person A gets 5 tickets and Person B gets 2, the next ticket goes to B regardless of B's workload. This works if all tickets take roughly the same time.

Equal Open: Every new ticket goes to the person with the fewest open (unresolved) tickets. This is smarter. If Person A is working on 8 tickets and Person B is working on 3, the next ticket goes to B. This method assumes roughly equal resolution times and works well for teams with similar ticket complexity.

By Tags: You create tags for issue types: "billing", "technical", "refund", "bug". You assign team members to tags. Every incoming ticket is auto-tagged based on content (email subject, form category, or live chat intent). Tickets are routed to the person (or team) assigned to that tag. This is most flexible but requires discipline: your tagging taxonomy must match your team structure.

Implementation:

1. Go to Helpdesk Team > Assignment Rules.
2. Select your method.
3. If using By Tags, create tags and assign team members.
4. Save.

Why assignment matters: It enforces SLAs. If tickets are piling up with one person, Odoo can't enforce response time promises. Balanced assignment also reduces burnout and makes overtime usage transparent. Start with Balanced on Open. It handles 90% of cases. Migrate to By Tags if you have specialized teams (e.g., billing never touches technical).

Step 4: Manage the Ticket Pipeline

The Helpdesk kanban is where you manage work. Each column is a stage (status). Default stages are New, In Progress, Pending, and Done. You can customize them.

Kanban Workflow:

1. Open Helpdesk Team > Dashboard (or Kanban view).
2. Tickets appear as cards in columns (stages).
3. Drag a card to move a ticket. Drop it in the target stage.
4. Click a card to open the ticket detail panel.

Customizing Stages:

1. Go to Helpdesk Team > Stages.
2. Click New to add a stage (e.g., "Escalated", "Waiting for Customer", "Resolved but Surveyed").
3. Set a description and color.
4. Reorder stages by dragging.

Prioritization: Each ticket has a star rating (0-5). Click the stars to set priority. High-priority tickets (5 stars) typically need faster response. You can filter the kanban to show only starred tickets.

Tags: Add custom tags: "urgent", "refund needed", "vip customer", "external vendor involved". Tags help with filtering, searching, and routing. You can create many tags and apply multiple tags to one ticket.

Sub-Tickets: For complex issues, create sub-tickets. Parent ticket: "Customer requests refund for broken widget". Sub-tickets: "Check return shipping", "Process refund", "Verify refund timeline". Complete sub-tickets, then close the parent. This breaks down big problems into trackable chunks.

Pro Tip: Your stages should mirror your actual process. If you always wait for customers to respond, add a "Waiting for Customer" stage. If you escalate to another team, add "Escalated". Don't create stages you won't use.

Step 5: Define SLAs and Automation Rules

SLAs are promises you make to customers about response time. Automation rules enforce those promises.

Service Level Agreements (SLAs):

1. Go to Helpdesk Team > SLA Policies.
2. Click New.
3. Define conditions: e.g. Priority = High, Customer = VIP.
4. Set response time target: e.g. "2 hours" from ticket creation.
5. Set resolution time target: e.g. "8 hours".
6. Save.

Odoo tracks both. Response time measures how long until the first reply. Resolution time measures how long until Done stage. If a ticket misses an SLA, it's marked as failed. You get reports on SLA performance.

Example SLAs:

• Priority 5 stars (Urgent): Response 1 hour, Resolution 4 hours.
• Priority 4 stars (High): Response 4 hours, Resolution 1 day.
• Priority 2-3 stars (Normal): Response 1 day, Resolution 3 days.
• Priority 1 star or no priority (Low): Response 3 days, Resolution 5 days.

Automation Rules:

1. Go to Helpdesk Team > Automation.
2. Click New.
3. Set a trigger: e.g. "Ticket created with Priority = 5" or "Ticket in stage Pending for 2 days".
4. Set an action: Send email, assign to user, move to stage, create returns/repair, send survey.
5. Save.

Example Rules:

• Rule 1: When ticket is created with Priority = 5, send email to team lead.
• Rule 2: When ticket is in Pending stage for 2 days, send reminder email to customer.
• Rule 3: When ticket reaches Done stage, send satisfaction survey.
• Rule 4: When ticket is created with tag = billing, assign to billing team.

Automation saves time and ensures consistency. A survey should always go out. A high-priority ticket should never sit in New for 4 hours.

Step 6: Enable the Customer Portal

The customer portal is self-service. Customers submit their own tickets and track progress.

Enable Portal Access:

1. Go to Helpdesk Team > Settings.
2. Toggle 'Portal Access: Enabled'.
3. Under Portal Permissions, choose:
   • Can create: Allow customers to create tickets.
   • Can view: Allow customers to see tickets they created.
   • Can update: Allow customers to reply to their tickets.
4. Save.

Customer Workflow:

1. A customer visits yourcompany.com/helpdesk or yourcompany.com/helpdesk/form.
2. If they don't have a portal account, they enter name, email, password, and sign up.
3. They fill in a support form (issue type, description, attachments).
4. Odoo creates a ticket and shows the customer a reference number.
5. The customer's portal dashboard shows all their tickets, responses, and status.
6. When a team member replies, the customer gets an email and can reply directly from email or the portal.

Portal Customization:

1. Go to Helpdesk Team > Portal Configuration.
2. Add custom fields: e.g., "Product", "Service Type", "Device", "Contract Number".
3. Create portal layouts and form variations.
4. Customize the look: branding, colors, instructions.

Why the Portal Matters: It reduces email clutter. Customers stop replying all, and instead add updates in the portal. Your team sees all communication in one place. Customers can also see other replies without creating duplicate threads.

Pro Tip: Link your knowledge base to the portal. If Odoo has a Website app with a knowledge base module, integrate it. When a customer submits a ticket, show them related articles first. 70% might self-resolve.

Integrations: Returns, Repairs, and CRM Links

Helpdesk's power comes from integration. A ticket is not isolated; it can trigger action across your business.

Returns (RMA):

1. Open a ticket about a damaged or defective product.
2. Click New > Create Return.
3. Odoo creates a return (RMA) and links it to the ticket.
4. The return can be fulfilled by your warehouse.
5. Once the return arrives, update the ticket with the next step (refund, replacement, repair).

This works if your Inventory app is configured with return management. If you sell physical goods, returns are critical.

Repairs:

1. Open a ticket about a device that needs repair.
2. Click New > Create Repair.
3. Odoo creates a repair work order with parts, labor, serial numbers.
4. The repair team works the order.
5. Once done, close the repair and mark the ticket Done.

Refunds (Credit Notes):

1. Open a ticket about a billing dispute or refund request.
2. Click New > Create Credit Note.
3. Odoo creates a credit note (negative invoice) for the customer.
4. The customer receives an email with the credit applied.
5. Close the ticket.

CRM Opportunities:

1. Open a ticket from a customer mentioning interest in a new product or upsell.
2. Click New > Create Opportunity.
3. Odoo creates a CRM opportunity pipeline linked to the ticket.
4. Your sales team can close the opportunity.
5. If successful, the original support ticket can note the cross-sell revenue.

Projects & Tasks: If a ticket requires internal work (e.g., "build a custom integration"), create a Project task. The task is assigned to your technical team. When done, mark the task complete and resolve the ticket.

These integrations reduce context switching. A billing dispute flows from Helpdesk to Accounting automatically. A product defect flows to the repair shop. Revenue impact is tracked.

Community Edition Users: Try the OCA Helpdesk Module

If you're running Odoo Community Edition, you cannot use the native Helpdesk app. But you have an option: the OCA Helpdesk Management module.

OCA stands for Odoo Community Association. It's a non-profit that maintains free, open-source extensions to Odoo Community Edition. The Helpdesk Management module is stable and community-maintained.

What OCA Helpdesk Covers:

• Ticket creation and assignment
• Ticket stages (kanban board)
• Email integration (basic)
• Customer portal
• Ticket tags and priorities
• Reporting

What OCA Helpdesk Lacks:

• Advanced SLAs (response/resolution time tracking)
• Live chat integration
• Automation rules (auto-close, auto-assign, surveys)
• Direct integration with Returns/Repairs/Refunds
• Advanced analytics

When to Use OCA Helpdesk:

• Your team is 5-10 people
• Ticket volume is low (under 100 per month)
• You need basic ticket management without extra features
• You're evaluating whether Helpdesk is worth moving to Enterprise

When to Move to Enterprise:

• Your team grows past 10 people
• SLA tracking becomes critical (you're liable for response time)
• You need automation to save labor
• You're managing complex product support (integrations with returns/repairs)

Installation:

1. Download the module from apps.odoo-community.org.
2. Extract it into your /addons folder.
3. Go to Apps > Update Apps List > Install Helpdesk Management.
4. Set up teams and channels like the Enterprise version.

Cost Comparison: OCA Helpdesk is free (but self-hosted). Enterprise Helpdesk requires an Odoo Enterprise subscription or cloud Odoo Online account. If you're self-hosting Community Edition, OCA Helpdesk is the obvious starting point.

Frequently Asked Questions

What is Odoo Helpdesk and which license tier is it available on?

Odoo Helpdesk is an Enterprise-only application for managing customer support tickets. It is not available in Community Edition. Community users must use the OCA Helpdesk Management module (free, open-source) or third-party alternatives.

How do I set up a helpdesk team?

Go to Helpdesk app > Configuration > Helpdesk Teams > New. Enter team name, description, assign users, select visibility (private, company, public), and choose an assignment method (manual, balanced, equal open, by tags). Save.

What are the visibility and assignment options?

Visibility: Private (invited users only), Company (all internal users), Public (internal plus portal customers). Assignment: Manual (you assign), Balanced (equal count), Balanced on Open (fewest active tickets), By Tags (route by issue type).

How do I enable email, web forms, and live chat for ticket capture?

Email: Configure an alias under Channels. Web Form: Add the form to your website. Live Chat: Link Live Chat module to Helpdesk. Tickets are created automatically from all three sources.

How do I manage tickets in the pipeline?

Use the kanban board. Drag tickets between stages (New, In Progress, Pending, Done). Customize stages to match your workflow. Add priority stars and tags. Create sub-tickets for complex issues.

How do I set up SLAs and automation?

SLAs: Define response and resolution time targets by priority. Automation Rules: Set triggers (ticket created, moved to stage, time elapsed) and actions (send email, assign, move stage, create return/repair, send survey).

How do I set up a customer self-service portal?

Enable portal access in Team Settings. Customers create accounts and submit tickets via web form. They track status, reply, and attach files without accessing the full Odoo system.

What operations can I trigger from a ticket?

Create Returns (RMA), Repairs, Credit Notes (refunds), CRM Opportunities (upsell), Project Tasks, or Inventory transfers. All remain linked to the original ticket.

The Bottom Line

Odoo Helpdesk is a powerful, integrated support system for Enterprise Edition users. Setup takes a few hours. Start with email, add web forms later, and automate as you scale. If you're on Community Edition, try the OCA Helpdesk module first.

The real win comes from integration. A ticket doesn't disappear; it flows into returns, repairs, refunds, and sales. Your support team becomes part of your fulfillment and revenue operations. Ready to deploy Odoo Helpdesk? Discover how Opsily's managed Odoo hosting supports your team at /hosting/odoo.