Customer support chaos is one of the fastest ways to lose clients. When tickets get lost in email threads, response times slip, and nobody knows who is handling what, your team looks unprofessional and your customers get frustrated.
Odoo Helpdesk solves this by bringing every support channel into one place. But most businesses never set it up properly. They install the app, create one generic team, and wonder why tickets still fall through the cracks.
This guide walks you through a complete Helpdesk setup that actually works. You will learn how to structure teams, configure ticket stages, set up email automation, and build a customer portal that reduces repetitive work.
TL;DR
- Create separate Helpdesk teams for Technical Support, Billing, and Pre-Sales
- Design ticket stages that match your real workflow (New → Triage → In Progress → Waiting → Escalated → Resolved → Closed)
- Connect email, website forms, and live chat to auto-create tickets
- Use automated actions for routing, priority boosts, and escalation
- Enable the customer portal for self-service ticket tracking
- Review response time, resolution time, and satisfaction metrics weekly
Step 1: Create Focused Helpdesk Teams
One generic "Support" team is a mistake. Your technical issues, billing questions, and pre-sales inquiries need different people, different priorities, and different workflows.
Go to Helpdesk > Configuration > Teams and create separate teams:
- Technical Support — Product bugs, setup issues, integration problems
- Billing & Accounts — Invoices, payments, subscription changes
- Pre-Sales — Demo requests, pricing questions, feature comparisons
For each team, set:
- Assignment method: Round-robin or balanced workload
- Visibility: Public (for customer portal) or private
- SLA policy: Response time targets per priority level
Each team gets its own email alias automatically. Customers email technical@yourcompany.odoo.com and the ticket lands in the right queue without manual sorting.
Step 2: Design Ticket Stages That Match Reality
Default stages are too simple for most businesses. You need stages that reflect what actually happens when someone reports an issue.
Go to Helpdesk > Configuration > Stages and build a pipeline like this:
- New — Ticket just arrived, not yet reviewed
- Triage — Quick assessment of priority and team
- In Progress — Agent is actively working on it
- Waiting on Customer — Need more info before continuing
- Escalated — Requires senior engineer or manager input
- Resolved — Fix applied, waiting for customer confirmation
- Closed — Confirmed fixed, no further action needed
For each stage, configure:
- Email template: Auto-notify customer when ticket moves here
- Folded in kanban: Hide closed tickets from default view
- Closing stage: Mark "Closed" as terminal so metrics calculate properly
Step 3: Connect Every Channel
Customers should not have to hunt for your support email. Odoo Helpdesk collects tickets from multiple channels automatically.
Each team gets an alias like support@yourdomain.com. Configure this in Settings > Technical > Email > Aliases. Every email creates a ticket with the sender as the customer.
Website Form
Go to Website > Forms and create a support request form. Map fields to ticket fields:
- Name to Customer name
- Email to Contact email
- Subject to Ticket title
- Issue Type to Team routing
- Message to Ticket description
Live Chat
Install the Live Chat app. When agents are offline, chats convert to tickets automatically. When online, agents can escalate complex chats to tickets with one click.
Understanding SLA Policies in Odoo Helpdesk
Service Level Agreements (SLAs) are what separate professional support operations from chaotic email management. Without SLAs, every ticket becomes "whenever someone gets to it." With SLAs, you have clear expectations and accountability.
Odoo Helpdesk lets you define SLA policies per team. Go to Helpdesk > Configuration > SLA Policies and create rules like:
- First Response Time: Reply within 4 hours for High priority, 24 hours for Low
- Resolution Time: Close tickets within 48 hours for bugs, 72 hours for feature requests
- Business Hours Only: Count SLA time only during working hours, not nights and weekends
Each SLA policy can target specific teams, ticket types, or customer tags. A Premium customer might get 1-hour response guarantees while free-tier users get 24 hours. This tiering prevents your team from burning out while keeping high-value clients happy.
The SLA dashboard shows which tickets are on track, which are at risk, and which have breached their targets. Use this data in weekly team reviews to identify bottlenecks before they become systemic problems.
Integrating Helpdesk with Other Odoo Apps
Odoo Helpdesk becomes significantly more powerful when connected to the rest of your Odoo ecosystem. Here are the most valuable integrations:
Helpdesk + CRM
Link tickets to opportunities and customers. When a pre-sales ticket comes in, the agent sees the full CRM history — past quotes, communication logs, and deal stage. This context eliminates the "can you explain your situation again" frustration.
Helpdesk + Sales
Convert support tickets into sales quotations. If a customer asks about upgrading their plan, the agent can create a quote directly from the ticket without switching apps.
Helpdesk + Project
Escalate complex issues to project tasks. A bug report that requires development work can spawn a project task with the original ticket linked for traceability.
Helpdesk + Timesheets
Track time spent on each ticket. This is essential for billable support contracts and for understanding the true cost of your support operations.
Helpdesk + Knowledge Base
Build a self-service knowledge base from resolved tickets. When agents close tickets, they can mark solutions as public articles. Over time, this reduces repetitive questions.
Setting Up Email Templates and Notifications
Communication is the heart of support. Odoo Helpdesk uses email templates to keep customers informed at every stage.
Go to Settings > Technical > Email > Templates and customize:
- Ticket Created: Confirmation with ticket number and expected response time
- Agent Replied: Notification that someone is working on the issue
- Waiting on Customer: Request for more information with clear instructions
- Ticket Resolved: Summary of the fix with a satisfaction survey link
- Ticket Closed: Final confirmation with knowledge base links
Use dynamic placeholders like ${object.name} for ticket number and ${object.partner_id.name} for customer name. Personalization makes automated emails feel human.
Pro tip: Add a "Reply Above This Line" separator to email templates. This keeps threaded conversations clean and prevents Odoo from creating duplicate tickets when customers reply.
Step 4: Automate Repetitive Work
Automation is where Odoo Helpdesk saves hours every week. Go to Helpdesk > Configuration > Automated Actions and set up rules like these:
Auto-Assign by Keyword
If ticket subject contains "invoice" or "payment," assign to Billing team. If it contains "bug" or "error," assign to Technical Support.
Priority Boost for VIP Customers
If the customer has a Premium subscription tag, set priority to High and assign to senior agent.
Auto-Response on Creation
Send an immediate confirmation: "We received your request and will respond within 4 hours. Ticket number: #12345."
Escalation on Stale Tickets
If a ticket sits in "In Progress" for 24 hours with no update, move it to "Escalated" and notify the team manager.
Step 5: Build a Customer Portal
The portal reduces repetitive "what is the status" emails. Customers log in and see:
- All their tickets with current stage
- Response history and agent notes (if shared)
- Knowledge base articles related to their issue
- Option to reopen closed tickets if the fix did not work
Enable this in Helpdesk > Configuration > Settings > Customer Portal. Set visibility so customers only see their own tickets, not everyone else's.
Step 6: Measure What Matters
Without metrics, you are guessing. Odoo Helpdesk reports show:
- Average response time: How fast do you first reply?
- Resolution time: How long from ticket creation to close?
- Ticket volume by team: Is one team overloaded?
- Customer satisfaction: Post-resolution survey scores
- Reopened rate: Are fixes actually working?
Review these weekly. If Technical Support has a 48-hour average response time while Pre-Sales responds in 2 hours, you have a resource problem, not a process problem.
Common Mistakes to Avoid
- One team for everything: Leads to misrouted tickets and overloaded agents
- No SLA targets: Without deadlines, everything becomes "whenever"
- Skipping the portal: Customers will email for status updates forever
- No escalation rules: Complex tickets rot in queues instead of reaching experts
- Ignoring reopened tickets: High reopen rates mean your fixes are superficial
Frequently Asked Questions
Can I use Helpdesk without the Website app?
Yes. Email and live chat channels work independently. The portal requires Website, but the core ticketing system does not.
How do I migrate tickets from Zendesk or Freshdesk?
Use Odoo's import tool with CSV exports. Map ticket ID, subject, description, stage, and customer email. Attachments require manual upload or API scripting.
Can customers rate agent performance?
Yes. Enable satisfaction surveys in team settings. After a ticket closes, the customer receives a one-click rating email.
Is there a mobile app for agents?
Agents can use Odoo's responsive web interface on mobile. There is no dedicated Helpdesk mobile app, but the web experience handles ticket updates, stage changes, and replies.
Can I bill customers for support hours?
Yes. Install the Timesheet app and link Helpdesk tickets to timesheet entries. Then invoice billable hours directly from the ticket.
Need Help Setting Up Odoo Helpdesk?
Explore Odoo Skillz for pre-built Helpdesk configurations, training modules, and expert guidance to get your support operations running smoothly.