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

# Link Genesys Cloud agents, queues and teams

> Link Genesys Cloud agents, queues, skills, wrap-up codes and presence to OpenCX, and sync every queue as a team. Use after connecting, before you go live.

The directory links each Genesys Cloud item to its OpenCX counterpart, so handoffs reach the right queue, assignees and sub-statuses follow, and presence can sync. Set it up after you [connect](https://docs.open.cx/integrations/genesys/connect.md) and before you go live.

## Link agents and queues

On the **Directory** tab, link each Genesys item to its OpenCX counterpart. Click **Link to** a suggested match or pick one from the list. The directory refreshes about every half hour, or click **Refresh** beside **Refresh directory** on the **Setup** tab.

| Genesys Cloud | OpenCX | Notes |
| - | - | - |
| **Agents** | Teammates | Linked automatically when the email matches. |
| **Queues** | Teams | Handoffs from a team go to its queue. **Import as team** creates the team and adds linked queue members, or turn on [Sync queues as teams](#sync-queues-as-teams) for every queue. Linked agents who later join the queue are added on each sync, and those who leave stay on the team. |
| **Skills** | Skills | Used for routing hints and workitems. |
| **Wrap-up codes** | Sub-statuses | A wrap-up sets the sub-status when the session closes, and the reverse applies when OpenCX closes it. |
| **Presence statuses** | Availability statuses | Optional. **Presence sync** is off by default. **From Genesys** reads it about once a minute. **Both ways** also sets Genesys presence from OpenCX. |

An unlinked presence maps to available for **Available** and **On Queue**, and to away otherwise.

OpenCX moves a conversation between queues only when you link a team to a queue and change the session's team, or turn on **Agent sync** and reassign it.

## Sync queues as teams

Turn on **Sync queues as teams** on the **Directory** tab to bring in every Genesys queue as a team, whatever its channel. Turning it on asks you to confirm, with the number of queues that will get a team, then refreshes the directory at once. Every refresh after that:

* Creates a team for each new queue, named after it, with the linked agents who are members of the queue. A team you already have with the same name is linked instead of copied.
* Renames a linked team when its queue is renamed. While it's on, linked teams take their queue's name.
* Unlinks the team of a queue deleted in Genesys. The team, its members and its sessions stay.

When Genesys moves a conversation to a queue, the session moves to that queue's team. New teams use manual assignment, because Genesys routes their conversations. A team you already had keeps its own settings when it's linked, so turn on support for it if sessions should move into it.

To leave a queue out, such as sales or partner support, switch it off in the **Queues** list. Do this before you turn the sync on, so no team is made for it. A queue you leave out keeps any team already linked to it. To remove a queue's team, switch the queue off first, then delete the team. A deleted team comes back on the next refresh while its queue is on.

**Sync queues as teams** is off by default, so connecting creates no teams. Connecting to a different Genesys org turns it off again and clears the queues you left out, because they belong to the old org.

## Related

> [card] [Handoff settings](https://docs.open.cx/integrations/genesys/handoff.md)
>
> Where handoffs go, and what happens when nobody is free.

> [card] [Every Genesys conversation](https://docs.open.cx/integrations/genesys/every-conversation.md)
>
> Queues you leave out never appear as sessions.


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