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
{
"routingPriority": [
123
],
"details": [
{
"routingPriority": 123,
"id": 123,
"ticketNotAssigned": true,
"ticketNotWorkedOnByColleague": true,
"aiSupportLevel": "unprocessed",
"priority": "low",
"channel": "email",
"dueBy": "<string>",
"tagExplanation": "<string>"
}
],
"query": "<string>"
}
Cookie-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.
The number of items to return
1 <= x <= 1000
Response format. When "html", an HTML table is returned for human inspection.
json
, html
Successful operation
The response is of type object
.
curl --request GET \
--url https://demo.enneo.ai/api/mind/profile/{id}/routing
{
"routingPriority": [
123
],
"details": [
{
"routingPriority": 123,
"id": 123,
"ticketNotAssigned": true,
"ticketNotWorkedOnByColleague": true,
"aiSupportLevel": "unprocessed",
"priority": "low",
"channel": "email",
"dueBy": "<string>",
"tagExplanation": "<string>"
}
],
"query": "<string>"
}