Explain the ticket routing considering the routing priorities. Useful when a user wants to know why they are being pushed a certain ticket.
curl --request GET \
--url https://demo.enneo.ai/api/mind/profile/{id}/routing \
--header 'Authorization: Bearer <token>'{
"routingPriority": [
123
],
"details": [
{
"routingPriority": 123,
"id": 123,
"ticketNotAssigned": true,
"ticketNotWorkedOnByColleague": true,
"aiSupportLevel": "unprocessed",
"priority": "low",
"channel": "email",
"dueBy": "<string>",
"tagExplanation": "<string>"
}
],
"total": 123,
"query": "<string>"
}JWT-based authentication
The id of the profile to explain routing for
If provided, explain routing relative to this ticket ID ("next" button). If omitted, explains routing for the next ticket.
Maximum number of tickets to return. Defaults to 500.
1 <= x <= 500The number of items to skip
x >= 0Successful operation
Ordered list of ticket IDs by routing priority
Show child attributes
unprocessed, human, bot, automated Priority of ticket
low, medium, high, urgent "low"
Channel of ticket
email, portal, phone, letter, system, chat, walkIn "email"
Total number of tickets that can be routed for this user
SQL-like query used to compute the routing
curl --request GET \
--url https://demo.enneo.ai/api/mind/profile/{id}/routing \
--header 'Authorization: Bearer <token>'{
"routingPriority": [
123
],
"details": [
{
"routingPriority": 123,
"id": 123,
"ticketNotAssigned": true,
"ticketNotWorkedOnByColleague": true,
"aiSupportLevel": "unprocessed",
"priority": "low",
"channel": "email",
"dueBy": "<string>",
"tagExplanation": "<string>"
}
],
"total": 123,
"query": "<string>"
}