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

> Name a set of technicians once, such as Tier 1 Helpdesk or On-call rota, then pick the group in dispatch and name it in custom instructions

A **group** is a named set of technicians with one line on what it is for, such as "Tier 1 Helpdesk: first line for every new ticket" or "On-call rota: out of hours". Use groups for tiers, teams and rotas: a tier is simply a group.

You manage groups on the [**Technicians** → **Groups**](https://dashboard.neoagent.io/profiles?view=groups) tab.

## Create a group

<Steps>
  <Step title="Name it">
    Select **New group**, give it a name, and describe what it is for. Dispatch reads the description next to the name.
  </Step>

  <Step title="Add members">
    Tick the technicians who belong to it. You can also add someone from their own card: open the technician, go to **Groups**, and tick the group.
  </Step>
</Steps>

A technician can be in several groups. The **Groups** tab flags a group with **One person**: when that person is away, the group has no one else to take its tickets.

## Pick a group in dispatch

In a [Dispatch Ticket](/building-automations/actions/ai/ticket-dispatch-suggest-technician) action, select **Choose technicians and groups**, then add groups in the **Technicians and groups** picker, next to any technicians you pick one by one. The list under the picker shows who is in the pool. On every run, the group's current members join the pool, so a person you add to the group later is included without editing the workflow.

The **Groups** tab shows which workflows use each group under **Used by**, and counts the ones you cannot view here, such as workflows in another environment. Check it before you delete a group: a workflow that still names a deleted group gets no one from it.

## Name a group in custom instructions

Dispatch sees each technician's groups next to their name, on Dispatch Ticket workflows and on agents that use [Get Technician Context](/agents/tools/psa/get-technician-context). So you can write rules such as "Send ransomware tickets to Tier 3 Escalations" or "After 18:00, assign only the On-call rota". An agent that reads "choose from Tier 1 Helpdesk" looks up your groups, matches the one you mean by its name and description, and asks Get Technician Context for that group alone, so it reads only those members' calendars and workload. Neo applies them together with the rest of your instructions; it does not route by group on its own.

## Ask Neo to set it up

The Neo Support Agent can create groups and change their members for you, for example: "Make a group called Weekend cover with Casey and Finley." By default it asks for approval before each change. Groups are also in the [public API](/developers/introduction) under `/public-api/technician-groups`.