Odoo 19 Helpdesk: choose an intake channel and a resolution rule
Choose email, website form or configured Live Chat for support intake, with a fictional ticket handover and a practical failure checklist.
Applicability
Odoo 19; app installation, subscription, access rights and mail configuration must match each workflow. Examples are fictional; UI translations may differ.
Research method
Odoo 19 official documentation research only; no new Odoo product test. Source checks apply only to the scopes listed below.
Choose one support channel whose owner can actually respond. Helpdesk provides a shared ticket record, but it does not turn every mailbox or WhatsApp conversation into the same customer issue automatically. This Odoo 19 document-based guide helps choose an intake design; it does not claim we opened and resolved a live ticket.
Contents
- Choose an intake route
- Configure email before promising intake
- Live Chat commands and chatbot boundaries
- Define the resolution handover
- Diagnose missing or duplicate requests
Choose an intake route
| Situation | Start with | Condition to confirm |
|---|---|---|
| Requests already arrive by email | Helpdesk team email alias | Incoming routing and monitored ownership |
| Requests need an order reference and description | Website Form | Correct website, required fields and published form |
| Operators are available for live conversations | Live Chat | Enabled team channel, operators and website/widget setup |
For a fictional replacement request, ask for order reference, affected item and a short description. Do not require payment-card details or passwords. Agree who reviews unassigned tickets and what “resolved” means before publishing another contact route.
Configure email before promising intake
The official path is Helpdesk → Configuration → Helpdesk Teams. Open the team and check its Channels / Email Alias settings. In the documented workflow, an incoming message's subject supplies the ticket title and its body supplies the description. Odoo Online/Odoo.sh and an on-premise server have different mail setup prerequisites; on-premise aliases require external mail-server configuration.
Record the expected alias and team in a handover sheet. A custom company domain is a separate mail-routing decision, not a prerequisite for every Odoo-hosted alias. A forwarded email may not retain the structured context your team needs, so define which order reference an operator must confirm.
Live Chat commands and chatbot boundaries
To use the documented /ticket command, first enable Live Chat on the Helpdesk team's Channels settings, configure the resulting Live Chat channel and add operators. The command is used inside an actual supported conversation; it is not a generic command to type anywhere in Odoo. The conversation transcript is added to the resulting ticket description. This guide has not executed that command.
A chatbot requires the Live Chat channel and a configured script, not merely Helpdesk installation. In the channel's Channel Rules, select a chatbot and, if required, enable it only when no operator is available. The Chatbots smart button leads to the script, whose steps and conditional answers must be designed. For the company website, check the selected channel in Website → Configuration → Settings → Email & Marketing → Live Chat; external websites need the supplied widget. This is an integration decision, not a promise that a bot understands an arbitrary support question.
Define the resolution handover
Use this fictional ticket worksheet to avoid closing an issue on an internal assumption:
| Checkpoint | Required record |
|---|---|
| Received | Order reference and reported fault |
| Assigned | Named operator and next review date |
| Investigating | Evidence requested and who supplies it |
| Resolution proposed | Replacement/repair proposal and who approves it |
| Closed under team rule | Outcome recorded and customer communication checked |
These checkpoints are proposed operating rules, not claims about default Helpdesk stages. A useful closing note says “Replacement dispatched under agreed reference; customer informed on the recorded date”, rather than “Done”. Whether customer acknowledgement is required depends on your service promise.
For private triage, use Log note and check mentions. Odoo 19 warns that an outside contact tagged in a note can receive its content and attachments by email. For customer communication, inspect Send message recipients and followers before sending. A note and an outbound response are different actions.
Diagnose missing or duplicate requests
| Symptom | First checks | Operational response |
|---|---|---|
| Email produces no visible ticket | Alias routing, intended team and user access | Keep the source email; identify mail routing versus visibility failure |
| Website form is absent | Correct website, publication and team Website Form setting | Correct the entry point before advertising it |
| Chat is absent | Channel selection, URL rule and widget installation | Check the actual page route and intended availability |
| Same issue has multiple tickets | Customer reference and channel of each record | Establish one operator's ownership before deciding how to consolidate |
| Team replies but customer hears nothing | Actual sent message, recipients and delivery status | Separate private note from outgoing-message failure |
Start with one team and one intake route. Ask APAA to scope the intake and handover design using a fictional issue, expected owner and response promise. Add chatbots only when someone owns the script and its unanswered cases.
Sources
- Receiving tickets
Team channels, email aliases, /ticket, chatbot channel rules and website forms
Source checked
- Chatter
Internal notes, external mentions and message recipients
Source checked