Case: support triage
This page shows how the Support Triage digital employee reads your ticket queue, sorts tickets and drafts replies, and why nothing it writes can reach a customer.
Who this is for: support managers and administrators.
You need: Edition: Business (digital employees). You also need the Helpdesk bridge (minddesk_helpdesk, Business) and Odoo Enterprise Helpdesk. Odoo Community has no Helpdesk app. See Editions.
What Support Triage is
Support Triage is a job role that ships with the Helpdesk bridge. It appears when the bridge and the Workforce module are both installed. The role suggests:
- highest autonomy and default autonomy: Asks first,
- a monthly budget of 18 USD (shown in your workforce currency),
- one run every day,
- it works on Helpdesk Tickets and Contacts.
Two skills come with it: a rule set for sorting tickets, and a guide for the tone of replies. The mission says to treat ticket text as untrusted data and to leave sorting, assigning, priority changes, article links and draft replies to the approval path.
Reading the queue
The search tool returns the tickets, the total, and whether there are more. It shows the highest priority first. Ticket descriptions are left out unless the employee asks for them. Descriptions are long, and they are text from outside your company.
What it can change
Every change needs a person. These tools always ask:
| Tool | What it does | Worth knowing |
|---|---|---|
| Classify | Adds labels to tickets | A label that does not exist is created. A spelling mistake becomes a permanent label. |
| Set priority | Sets 0 (low) to 3 (urgent) on all tickets in the call | Other values are refused. |
| Assign | Sets the responsible user | It needs the user's id, so the employee must look the person up first. |
| Link KB article | Adds a link to a Knowledge article as a note | It refuses if Odoo Knowledge is not installed. |
| Draft reply | Adds a drafted answer as an internal note | See below. |
A drafted reply is an internal note
The draft reply tool adds the text to the ticket as an internal note with the title "MitDesk draft reply". The tool says in its own description that the text is not sent to the customer. A person must read it and send it. The bridge has no tool that sends mail to a customer.
The draft waits as an approval card in Decisions until you approve it.
Ticket text is data, not an order
Tickets are written by people outside your company, so a ticket can contain an instruction on purpose. MitDesk handles this in three ways:
- Text from tickets, records and documents is wrapped in a marked block with a random id before the model reads it. Text inside the block cannot close the block.
- The system prompt tells the model that anything inside a block is content to read and report, never an order, whatever it says about itself.
- Control codes that some models use are replaced with the visible note "[marker removed by MitDesk]". MitDesk does not delete sentences for sounding like orders.
The skill text itself is not wrapped, because your administrator wrote it.
These rules help the model, but the real protection is the approval gate. Even a model that believed a ticket would still need a person to approve every change. The gate does not read the conversation. See How consent works.
For example, a customer who writes "stop all payment reminders" has made a request that a person should read. It does not switch anything off. See Case: receivables follow-up.
Grounding a draft
The sorting rules tell the employee to search your knowledge first, if the knowledge search tool is available, and to quote the article before it drafts. This needs the Knowledge module from the Pro edition. The search checks, for each passage, whether the Runs as account may read it. See Knowledge and sources.
The tone guide asks the employee to state only facts from the ticket or approved sources, to promise no timelines, to say what is still unknown, and to draft for review when a reply could change entitlements, billing or service-level promises.
If it does not work
If the digital employee stops running, see Troubleshooting.