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

# Genesys Cloud workitems for OpenCX sessions

> Give handed-off OpenCX sessions a Genesys Cloud workitem, fill its custom attributes, and keep its status and assignee in step with the session.

A Genesys Cloud workitem tracks a session as a task in Genesys, alongside or instead of a conversation. Use it when your team plans work in Genesys task management, or when **When no agents are on the queue** is set to **Create a workitem**.

| Setting (on the **Handoff** tab) | What it does | Default |
| - | - | - |
| **Worktype** | The worktype every workitem uses. Every option other than **Never** needs one. | None |
| **Create a workitem for** | Which sessions get a workitem, below. | Never |

| Create a workitem for | Which sessions |
| - | - |
| **Never** | None |
| **On handoff** | Sessions handed off to Genesys |
| **Email sessions** | Email sessions handed off to Genesys |

A workspace that chose the former **All sessions** option shows **On handoff**: both gave a workitem to every session handed off to Genesys.

## What the workitem holds

A session gets at most one workitem, with its title, summary, queue, skills, language and priority. To fill custom attributes, set session attributes named `genesys_workitem_<attribute>` before handoff. Values the worktype rejects are left out. The ID is stored on the session as `genesys_workitem_id`.

A session that has only a workitem, with no Genesys conversation, carries its summary and link in the workitem's description only. Its internal notes stay in OpenCX.

## Kept in step

| When | Then |
| - | - |
| The session is closed in OpenCX, by anyone including the AI, or merged into another session | The workitem moves to the nearest **Closed** status. |
| The session is reopened in OpenCX | The workitem moves to the nearest open status. |
| A member is assigned in OpenCX, with assignee sync to Genesys on | The workitem goes to the member's linked Genesys user. |
| An agent moves the workitem to a **Closed** status in Genesys | The session closes, within about a minute, and your session-closed workflows and webhooks run. |
| An agent reopens the workitem in Genesys | The session reopens, unless it was merged into another session. |
| The workitem is assigned in Genesys, with assignee sync from Genesys on | The linked member gets the session. |

Workflows can create and update workitems too: see **Create Genesys Workitem** and **Update Genesys Workitem** in [Workflow actions](https://docs.open.cx/integrations/genesys/workflow-actions.md).

## Workitem statuses and custom statuses

By default only open and closed are kept in step, as above. OpenCX moves the workitem to the nearest **Closed** or open status your worktype's transitions allow. Statuses are matched by their Genesys ID, never their name, so a **Closed** status closes the session even if its name reads as open.

Each of your custom session statuses can also be mapped to one workitem status:

* Setting that custom status on a session moves its workitem to the mapped status.
* An agent moving the workitem to that status in Genesys sets the custom status on the session, or closes the session with it if it's a closed status.
* A custom status for open sessions can't be mapped to a **Closed** workitem status.
* Saving a mapping fills in the custom status of open sessions that have none, from their workitem's current status. It never closes or reopens a session.

## Related

> [card] [Handoff settings](https://docs.open.cx/integrations/genesys/handoff.md)
>
> Create a workitem when nobody is on the queue.

> [card] [Permissions](https://docs.open.cx/integrations/genesys/permissions.md)
>
> Workitems need the workitem permissions on the role.


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