When email stops being enough

Every business starts with support in a shared inbox. It works for a while.

Then it stops. Two people reply to the same customer. A request sits for four days because everyone assumed someone else had it. Nobody can say how many open issues there are, or how long customers typically wait.

Helpdesk fixes those specific problems. If none of them are happening to you, you do not need it yet.

Teams and tickets

A helpdesk team handles a category of support. You might have one team, or several — technical support, billing, a team per product line.

Each team has its own members, its own stages, its own email alias and its own performance targets.

A ticket is one customer request. It has a customer, a description, an assigned person, a priority and a stage.

The important part is what a ticket is connected to. Because Helpdesk sits in the same database, the agent can see the customer’s orders, invoices, deliveries and past tickets from the ticket itself. No searching in another system, no asking the customer to repeat information they already gave you.

How tickets arrive

Email. Each team gets an email alias. Anything sent there becomes a ticket, and replies thread onto it.

Website form. A support form on your site creates tickets directly.

Customer portal. Logged-in customers submit and track their own tickets.

Live chat. A conversation that needs follow-up converts to a ticket in one click.

Manually. An agent creates one after a phone call.

Set up email first. It is the route most customers will use regardless of what else you offer, and it lets you move without asking customers to change their habits.

Stages

Same rule as every other pipeline in Odoo: few stages, each one a fact.

A working set: New, In Progress, Waiting on Customer, Solved.

“Waiting on Customer” is the one people forget, and it is the most useful of the four. Without it, tickets blocked on a customer reply look like tickets your team is ignoring, and your response time reports become meaningless.

SLAs

A service level agreement is a promise about response or resolution time.

You define policies — for example, high priority tickets get a first response within four hours. Odoo tracks each ticket against its policy and shows what is at risk.

Two pieces of advice.

Set targets you can actually meet. An SLA everybody misses is worse than no SLA. It trains the team to ignore the warnings.

Measure before you promise. Run Helpdesk for a month without SLAs, look at your real response times, and set targets from that.

Assignment

Three approaches:

Manual. A team lead assigns. Fine for small teams.

Round-robin. Tickets distributed evenly in turn.

Balanced. Assigned to whoever currently has the fewest open tickets.

Balanced works best for most teams, because it accounts for the fact that some tickets take far longer than others.

Whichever you choose, every ticket needs an owner. An unassigned ticket is a ticket nobody is working on.

Features worth using

Canned responses. Saved replies for common questions. Saves real time and keeps answers consistent.

Knowledge base. Published articles customers can find themselves. Every article that answers a common question is a ticket you never receive.

Ticket to task. Convert a support ticket into a project task when it turns out to need development work.

Time tracking. Log time on tickets. Necessary if you sell support contracts.

Customer satisfaction rating. A one-click rating on ticket closure. The response rate is low and the trend is still worth watching.

Merging. Customers often send three emails about one problem. Merge the tickets rather than closing two without explanation.

Selling support

If support is a product you sell, Odoo handles it.

Support contracts can be sold as a service product, with a number of hours. Time logged on tickets draws down the balance, and the customer can see their remaining hours in the portal.

When the hours run out, you have a factual conversation instead of an awkward one.

Reports worth using

Tickets by stage. Where the queue is sitting right now.

Average response and resolution time. Your actual service level, as opposed to the one on your website.

SLA success rate. How often you meet your own promises.

Tickets by type. What customers actually contact you about. This is the most valuable report in the module and the least used — it tells you what to fix in the product or document in the knowledge base.

Agent workload. Volume by person. Read alongside resolution time, not on its own.

What usually goes wrong

No “Waiting on Customer” stage. Response time reports become meaningless and your team looks worse than it is.

SLAs set too ambitiously. Everyone misses them, everyone ignores them.

Nobody reads the ticket-type report. Support becomes a treadmill instead of a source of improvement.

Knowledge base never written. The same question answered a hundred times individually.

Closing tickets without a real resolution. Tickets closed to clear the queue come back as new tickets, and now your data says you have twice as many problems.

Tickets with no owner. The single most common cause of a customer waiting a week.

Getting started

1. Create one team and set up its email alias
2. Use four stages, including Waiting on Customer
3. Set assignment to balanced
4. Run for a month with no SLA and measure your real times
5. Set SLA targets based on that measurement
6. Write knowledge base articles for your five most common questions
7. Review the ticket-type report monthly and fix the top cause

Point 7 is what separates a helpdesk that improves your business from one that just processes complaints faster.