> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Exclude a company's tickets

> Keep one end client's tickets out of Neo on any PSA: no sync, no triggered agent runs from their webhooks, and the synced tickets deleted

Some end clients must not have their tickets in Neo, for example a customer whose contract or regulator forbids a third-party AI processor. Excluding a company's tickets keeps them out on every PSA Neo supports.

## What changes when you exclude a company

| | Excluded company |
| - | - |
| Scheduled ticket sync | Skips its tickets before Neo summarizes or indexes them |
| PSA webhooks | Dropped before they start a triggered agent |
| Agents | No triggered agent runs on its tickets |
| Tickets already in Neo | Deleted from Neo's ticket search |
| The company itself | Stays on the Companies tab with a **Tickets excluded** badge |

The exclusion takes full effect within a minute of saving it. Work that had already started on one of the company's tickets, such as a webhook being processed or an agent run, finishes. In that first minute, a webhook that names the company can still reach Neo's job queue before Neo drops it, and a ticket can still be written to Neo's ticket search. A second pass, 30 minutes after you exclude the company, deletes such tickets.

An agent that reads your PSA directly, such as a scheduled agent that searches tickets or a chat question about a ticket, can still read the company's tickets from the PSA. What it reads is part of that agent run, and the run's record keeps it like any other run.

Most webhooks name their company, and Neo drops them on arrival. For a webhook that does not (ServiceNow, an Autotask webhook without the company field, a Syncro comment), Neo reads the ticket from your PSA first, then drops the webhook before it saves it or matches an agent. Such a webhook passes through Neo's job queue before the drop, and the queue keeps its record for 30 days.

## Exclude or include a company

<Steps>
  <Step title="Open your PSA's settings">
    On [**Integrations**](https://dashboard.neoagent.io/integrations), pick your PSA and expand **Advanced settings**. **Excluded companies** sits below **Company filters**. For ServiceNow, which has no Advanced settings, **Excluded companies** is its own card on the ServiceNow page.
  </Step>

  <Step title="Exclude a company's tickets">
    Pick the company, choose **Exclude tickets** and confirm. It joins the list of excluded companies.
  </Step>

  <Step title="Include them again (optional)">
    Choose **Include tickets** on the company's row. Neo syncs the company's tickets updated in the last 90 days again. An older ticket comes back when it next changes in your PSA.
  </Step>
</Steps>

You can also ask the Neo Support agent to exclude or include a company, or call `PUT /public-api/end-companies/{psa_company_id}/ticket-exclusion` with `{"excluded": true}` (see the [public API](/developers/introduction)).

<Note>
  Deleting a company from the Companies tab removes its exclusion, and Neo processes its tickets again. Keep the company and exclude its tickets instead.
</Note>

## Restrict the PSA account Neo uses

Excluded companies covers Neo's sync and its triggered agents. A scheduled agent or Chat Agent reads your PSA as the account Neo signs in with, so it can still read an excluded company's tickets. Most PSAs let you restrict that account; each page says what yours allows:

* [ConnectWise](/integrations/psa/connectwise/creating-api-member#keep-neo-away-from-specific-companies)
* [Autotask](/integrations/psa/autotask/creating-security-level#keep-neo-away-from-specific-companies)
* [HaloPSA](/integrations/psa/halopsa/creating-agent#keep-neo-away-from-specific-companies)
* [ServiceNow](/integrations/psa/servicenow/creating-oauth-app#keep-neo-away-from-specific-companies)
* [Syncro](/integrations/psa/syncro/creating-security-group#keep-neo-away-from-specific-customers)

A restricted account also stops Neo's sync from reading the company's tickets.

## How this differs from other filters

* [**Company filters**](/integrations/psa/company-filters) decide which companies are in Neo's company directory. They do not stop a company's tickets.
* **PSA filters** (boards, queues, assignment groups) decide which tickets Neo syncs by where they sit in your PSA, not by company.
* A triggered agent's condition on the company name stops that agent, but Neo still syncs and stores the tickets.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.