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

# Technician companies

> Send a company's tickets to a technician first, keep a technician away from a company, or limit a technician to a set of companies

Dispatch reads three company rules on a technician. Each company in the first two lists can carry an optional note:

* **Preferred companies**: Neo sends their tickets to this technician first. The technician still takes other tickets.
* **Never assign from**: Neo does not send their tickets to this technician, unless the note names an exception.
* **Only these companies**: the technician takes tickets from the preferred companies only.

You set them on the [**Technicians**](https://dashboard.neoagent.io/profiles) page, in two places that edit the same rules: open a technician and go to **Companies**, or open the **Companies** tab to work one company at a time.

## Add a company

<Steps>
  <Step title="Pick the company">
    Under **Preferred companies** or **Never assign from**, select **Add** and pick the company from your PSA. A company can be in one list only.
  </Step>

  <Step title="Add a note (optional)">
    Type a note for dispatch, such as "Only P1 and P2 tickets" or "Except P1 outages". The note saves when you leave the field. Dispatch reads it with the company.
  </Step>
</Steps>

A technician can have up to 30 companies.

## Work by company

The [**Companies**](https://dashboard.neoagent.io/profiles?view=companies) tab lists every company that has a rule, with its preferred technicians and the technicians who never take its tickets, and each note. **One person** marks a company with a single preferred technician. Search by company or technician name, or filter to the companies with preferred technicians, with never-assign technicians, or with a preferred technician limited to their preferred companies.

Select a company to change who takes its tickets, or select **Add a company** to start one. Add technicians under **Preferred technicians** or **Never assign**, add a note to each, then select **Save**. The save changes only that company; every technician's other companies stay.

**Only these companies** stays on each technician's own **Companies** pane. A save that would leave a technician limited to their preferred companies with none is refused: turn the switch off on their profile first.

## Limit a technician to their companies

Turn on **Only these companies**. You need at least one preferred company first.

* In a [Dispatch Ticket](/building-automations/actions/ai/ticket-dispatch-suggest-technician) action, Neo removes the technician from the pool for a ticket from any other company, before it decides. A ticket with no company goes to other technicians.
* If every technician in the pool is limited to other companies, the ticket stays unassigned and Neo sends a message to your inbox.
* An agent that uses [Get Technician Context](/agents/tools/psa/get-technician-context) gets a warning from Verify Dispatch Decision when it picks the technician for another company.

A note cannot add an exception to **Only these companies**. Turn it off if the technician takes some other tickets, and write the rule in a note.

## How dispatch uses the lists

Dispatch shows each technician's companies and notes next to their name, on Dispatch Ticket actions and on agents that use Get Technician Context. It shows them when the **Profile** setting of the Dispatch Ticket action is off too. Neo reads the preferred and never-assign lists as rules, together with the notes.

A Dispatch Ticket action that uses **round robin** reads no notes. It skips a technician who never takes the ticket's company, and it tries the technicians who prefer that company first.

If a rule is in both a list and the technician's custom instructions, keep it in one place, so dispatch reads one rule.

## Ask Neo to set it up

The Neo Support Agent can set the companies for you, for example: "Make Harbor Dental Group a preferred company for Alex, only for P1 and P2 tickets." It can also move company rules from a technician's custom instructions into the lists. By default it asks for approval before each change. Companies are also in the [public API](/developers/introduction): `PATCH /public-api/technicians/<id>` per technician, and `GET /public-api/technicians/companies` and `PUT /public-api/technicians/companies/<psa_company_id>` per company.


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