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

# Add queue members and skills

> Add or remove queue members, and tag agents with skills so a skills-based queue only routes to qualified agents.

Add or remove agents from a queue, and, for a skills-based queue, tag agents with the skills
that qualify them for its calls.

## Before you start

* You need an existing [queue](/inbound/queues/create-a-queue).
* For skills-based routing, decide your skill tags before you start — they're free text, so
  consistent spelling matters (`spanish`, not sometimes `Spanish` and sometimes `spa`).

## Add or remove members

<Steps>
  <Step title="Open the queue">
    In the left navigation, select **Queues**, then select the queue.
  </Step>

  <Step title="Add a member">
    Select an agent from the member picker to add them.
  </Step>

  <Step title="Remove a member">
    Select **Remove** next to a member to take them off the queue.
  </Step>
</Steps>

## Set required skills on a skills-based queue

<Steps>
  <Step title="Open the queue">
    In the left navigation, select **Queues**, then select the queue.
  </Step>

  <Step title="Enter required skills">
    In **Required skills**, enter comma-separated tags — for example `spanish, billing`. An
    agent needs **every** tag listed to receive this queue's calls under the
    **Skills-based** strategy.
  </Step>

  <Step title="Save">
    Select **Save**.
  </Step>
</Steps>

## Tag an agent with skills

<Steps>
  <Step title="Open the agent">
    In the left navigation, select **Agents**, then select the person.
  </Step>

  <Step title="Enter their skills">
    In **Routing Skills**, enter comma-separated tags matching the ones your queues require.
  </Step>

  <Step title="Save">
    Select **Save**.
  </Step>
</Steps>

## Verify

<Check>
  An agent tagged with all of a skills-based queue's required skills receives its calls; one
  missing even one tag doesn't.
</Check>

<Note>
  Each member also has a priority Get2Dial uses to decide who's offered a call first, but
  there's no way to set it from the product today — every member gets the same default. If
  ordering within a queue matters to you, skills-based routing (or a second queue) is the
  available lever.
</Note>

## Common problems

* **A tagged agent still isn't getting calls.** Confirm the queue's strategy is actually set
  to **Skills-based** — required skills are ignored under **Round robin** and **Least busy**.
* **Skill tags don't seem to match.** Tags are compared as entered; check for typos or
  inconsistent capitalization between the agent and the queue.

## Next steps

<CardGroup cols={2}>
  <Card title="Queues" href="/inbound/queues/overview" />

  <Card title="Set a service level target" href="/inbound/service-level-and-priority" />
</CardGroup>