corestack_ ticket_ priority_ set
Change a support ticket's priority.
When to use it
Change a support ticket's priority, as the ticket page's priority menu does. Everyone following the ticket is emailed the
change. An emergency pages Corefinity's on-call engineers instead: choose it only for a site that is down or losing
orders, after telling the person the emergency notice from corestack_ticket_options_get, and send
confirm_emergency: true once they agree. Setting the priority the ticket already has changes nothing.
Ask for it
Using the Corefinity MCP server, call corestack_ticket_priority_set with ticket_id 48210, priority high. (Change a support ticket's priority.) Tell me what it returned.Inputs
The client company the ticket is in, when your agency raised it for a client (the same value you listed it with); your own company when left out. At least 1.
true to raise it to emergency, only after the person agreed.
low, medium, high or emergency.
emergencyhighmediumlowThe ticket's number, from corestack_tickets_list. At least 1.
Example call
{
"name": "corestack_ticket_priority_set",
"arguments": {
"ticket_id": 48210,
"priority": "high"
}
}If it is refused
| Reason | What to do |
|---|---|
confirm | An emergency without confirm_emergency: true. Tell the person what an emergency does, then ask. |
tenant_mismatch | There is no such ticket, or it is not in your company (or in client_company_id, a client company your agency reaches), or the person only follows it as a subscriber of another company. |
pin_refused | The token is limited to some sites; a ticket belongs to the whole company. |
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |