---
title: "corestack_ticket_priority_set"
url: https://docs.corefinity.com/mcp/tools/corestack_ticket_priority_set
type: tool
last_updated: 2026-11-13
feature: support
related:
  - https://docs.corefinity.com/guides/support/raise-and-follow-a-ticket.md
---
# corestack_ticket_priority_set

**Change a support ticket's priority.** Change a support ticket's priority, as the ticket page does. emergency pages on-call engineers: confirm_emergency must be true, after the person agreed. Scope: write.

- Scope: `write`
- Runs as a task: no

## 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.

## Inputs

- `ticket_id` (integer, ≥ 1, required): the ticket's number, from corestack_tickets_list.
- `priority` (string, required): `low`, `medium`, `high` or `emergency`.
- `confirm_emergency` (boolean, optional): `true` to raise it to emergency, only after the person agreed.
- `client_company_id` (integer, optional): 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.

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "client_company_id": {
      "minimum": 1,
      "type": "integer"
    },
    "confirm_emergency": {
      "type": "boolean"
    },
    "priority": {
      "enum": [
        "emergency",
        "high",
        "medium",
        "low"
      ],
      "type": "string"
    },
    "ticket_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "ticket_id",
    "priority"
  ],
  "type": "object"
}
```

## Refusals

- `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.
- The refusals every tool can answer: `invalid_arguments`, `scope_required`, `rate_limited`, `temporarily_unavailable`,
  `internal_error` (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_ticket_priority_set",
  "arguments": {
    "ticket_id": 48210,
    "priority": "high"
  }
}
```

## Prompt

```text
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.
```

## The same task elsewhere

- Guide: [Support tickets](https://docs.corefinity.com/guides/support/raise-and-follow-a-ticket.md)
