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

**Reply to a support ticket.** Reply to a support ticket, as the ticket page does: Corefinity and everyone following the ticket are told. body is Markdown; attach files with upload_ids from corestack_ticket_upload_create. Scope: write.

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

## When to use it

Add a reply to a support ticket, as the person would in the ticket page's reply box: Corefinity's support team and everyone
following the ticket are told, and the person's email signature is added as on the page. A reply hands a ticket that is
waiting on the customer, resolved or closed back to Corefinity (it opens again). Each call posts a new reply, so do not
repeat it after a timeout without reading the ticket with corestack_ticket_get first. Replies are always public: internal
notes are for Corefinity staff on the page.

## Inputs

- `ticket_id` (integer, ≥ 1, required): the ticket's number, from corestack_tickets_list.
- `body` (string): the reply in Markdown. Required unless you send files.
- `upload_ids` (list of strings, up to 20): files to attach, each the `upload_id` corestack_ticket_upload_create answered
  and you have already sent the file to. Each upload is yours alone and is attached once; the same types are refused as on
  the page (scripts and programs).
- `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": {
    "body": {
      "maxLength": 65535,
      "minLength": 1,
      "type": "string"
    },
    "client_company_id": {
      "minimum": 1,
      "type": "integer"
    },
    "ticket_id": {
      "minimum": 1,
      "type": "integer"
    },
    "upload_ids": {
      "items": {
        "maxLength": 36,
        "minLength": 36,
        "type": "string"
      },
      "maxItems": 20,
      "type": "array"
    }
  },
  "required": [
    "ticket_id"
  ],
  "type": "object"
}
```

## Refusals

- `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` naming `upload_ids`: an upload that is not yours or has expired (open a new one), one whose file
  has not arrived yet (PUT it to its url first), a file type that is not allowed, or more than 20 files.
- 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_reply",
  "arguments": {
    "ticket_id": 48210,
    "body": "The error stopped after we cleared the cache at 10:15. Can you confirm nothing else is wrong?"
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_ticket_reply with ticket_id 48210, body The error stopped after we cleared the cache at 10:15. Can you confirm nothing else is wrong?. (Reply to a support ticket.) Tell me what it returned.
```

## The same task elsewhere

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