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

**Add a follower to a support ticket.** Add a person as a follower of a support ticket, so they are told of its replies, as the ticket page's Add button. Adding a follower twice changes nothing. Scope: write.

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

## When to use it

Add a person as a follower of a support ticket, so they are told of its replies, as the ticket page's Add button does.
Find the person's `id` with corestack_ticket_subscribers_list and its `search`. Adding someone who already follows
changes nothing and sends nothing. Adding a follower never notifies anyone: they hear of the next reply.

## Inputs

- `ticket_id` (integer, ≥ 1, required): the ticket's number, from corestack_tickets_list.
- `user_id` (integer, ≥ 1, required): the person to add, one of the `candidates` corestack_ticket_subscribers_list offers.
- `client_company_id` (integer, optional): the client company the ticket is in, when your agency raised it for a client;
  your own company when left out.

The answer is the ticket's followers, as corestack_ticket_subscribers_list answers them (without `candidates`).

### Input schema

```json
{
  "additionalProperties": false,
  "properties": {
    "client_company_id": {
      "minimum": 1,
      "type": "integer"
    },
    "ticket_id": {
      "minimum": 1,
      "type": "integer"
    },
    "user_id": {
      "minimum": 1,
      "type": "integer"
    }
  },
  "required": [
    "ticket_id",
    "user_id"
  ],
  "type": "object"
}
```

## Refusals

- `tenant_mismatch`: there is no such ticket, or it is not in your company (or in `client_company_id`), or the person
  only follows it as a subscriber of another company.
- `forbidden`: you may not change who follows this ticket.
- `invalid_arguments` on `user_id`: there is no such person, they are not active, or they are not in a company that can
  follow this ticket (a ticket about websites of more than one company is followed only by its own company's people).
  All three get the same answer.
- `pin_refused`: the token is limited to some sites; a ticket belongs to the whole company.
- The refusals every tool can answer: `scope_required`, `rate_limited`, `temporarily_unavailable`, `internal_error`
  (corestack://guides/how-this-server-works).

## Example

```json
{
  "name": "corestack_ticket_subscriber_add",
  "arguments": {
    "ticket_id": 48210,
    "user_id": 5123
  }
}
```

## Prompt

```text
Using the Corefinity MCP server, call corestack_ticket_subscriber_add with ticket_id 48210, user_id 5123. (Add a follower 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)
