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

# Erasing Genesys Cloud sessions in OpenCX

> What happens to a Genesys Cloud linked session when you redact or erase it in OpenCX: what is removed, what is kept, and what comes back from Genesys.

Redacting or erasing a session in OpenCX reaches what the Genesys Cloud integration keeps for it. Read this before you erase a customer's data on a Genesys workspace, to know what goes and what Genesys still holds.

## When you erase a session

[Erasing a session](https://docs.open.cx/api-reference/redaction/redact-session.md) removes its messages, attachments and notes in OpenCX as on any workspace. On a Genesys workspace it also:

* Removes the copies of the session's messages kept for retrying deliveries. Messages written before the erasure never come back into the session; messages written after it still arrive.
* Stops the Genesys summary, evaluation scores and notes from the Genesys external contact for that session. See [Quality and insights](https://docs.open.cx/integrations/genesys/insights.md) and [Notes, both ways](https://docs.open.cx/integrations/genesys/contacts.md#notes-both-ways).
* Hides the session's internal notes from the [Assist panel](https://docs.open.cx/integrations/genesys/assist-panel.md) and clears its cached draft.

Within a few minutes, OpenCX also clears what it wrote about the session in Genesys:

* **On the session's Genesys conversation, and on callbacks booked from it:** every `opencx_*` participant data key, and the **OpenCX summary**, **OpenCX notes** and **OpenCX session** fields agents see in **Conversation Details**, are emptied.
* **On the linked external contact:** the notes OpenCX added for this session are deleted. That is a teammate's note that ends with a link to this session, and the CSAT note that names it.
* **On the session's workitem:** the name becomes **OpenCX session** with the ticket number, the description is emptied, and the custom fields OpenCX filled from the session are cleared. Fields your agents or workflows filled stay, and a closed workitem Genesys won't change keeps its text.

Notes for the contact's other sessions, notes Genesys agents wrote, and participant data your own flows or agents set are left alone. If Genesys can't be reached, OpenCX tries again. Erasing a session never deletes the customer in Genesys.

While **Genesys connection on** is off or the connection needs reconnecting, OpenCX waits: **Health** shows how many erasures are waiting, and they reach Genesys as soon as the connection works again, for up to 6 days. If they still can't, or you disconnect Genesys or connect another Genesys organization first, OpenCX records in the audit log that the Genesys copy wasn't cleared, and **Health** warns. Clear those in Genesys by hand. A deletion request for a contact you delete meanwhile, or one OpenCX was about to file, is handled the same way.

## What stays in Genesys

Some data stays in Genesys after you erase a session. Genesys's own retention settings apply to it:

* The conversation's transcript and recordings, the agent's wrap-up and notes, and analytics.
* Participant data on a conversation that Genesys no longer lets anyone change, usually because it ended. OpenCX tries once, records that it was refused, and doesn't try again.

To remove a person's data from Genesys itself, file a GDPR deletion request for them in Genesys. With **Delete contacts in Genesys too** on, deleting their contact in OpenCX files the request for you.

## Erasure in both directions

Two settings link erasure across OpenCX and Genesys. Both are off by default. To find them, open **Settings → Ticketing → Genesys Cloud**, then the **Erasure** section of the **Handoff** tab. Turning either one on asks you to confirm. Before you can turn either one on:

* Genesys must be live for your workspace.
* The role OpenCX uses in Genesys needs `gdpr:request:view` and `gdpr:request:add`. Without them, OpenCX refuses the setting and asks you to reconnect Genesys with an admin who holds them.

| Setting | What it does | Default |
| - | - | - |
| **Delete contacts in Genesys too** | When you delete a contact in OpenCX, OpenCX files a GDPR deletion request for the same person in Genesys. The request names their Genesys external contact, email addresses and phone number. Genesys then deletes the person's conversations, recordings and contact data. Genesys can't undo this. | Off |
| **Apply Genesys deletion requests** | When a GDPR deletion request is completed in Genesys, OpenCX erases the sessions of the OpenCX contact it names, as if a teammate had erased each one. | Off |

### Deleting a contact files a deletion request

* OpenCX files a request only for a contact Genesys knows: one linked to a Genesys external contact, or one with a session that went to Genesys.
* OpenCX files one request per contact. If you delete the same contact again, or Genesys doesn't confirm the request, OpenCX doesn't file a second one.
* Only deleting a single contact files a request, from the contact's page or with the [API](https://docs.open.cx/api-reference/contacts/delete.md). Deleting several contacts at once doesn't.
* Deleting the contact doesn't erase its sessions in OpenCX. Erase them separately if you need to.

### A deletion request in Genesys erases sessions

OpenCX checks Genesys for completed deletion requests every few minutes. It applies them oldest first, and never skips one that is still running in Genesys.

* OpenCX only applies a request that names exactly one OpenCX contact Genesys knows: one linked to a Genesys external contact, or one with a session that went to Genesys. It matches by external contact, email (in any case, verified or not) or phone number (with or without the `+`). OpenCX then erases the sessions that contact had when the request was filed. Sessions the customer starts afterwards are kept, and the contact stays in OpenCX.
* If a request matches several contacts, OpenCX skips it and shows a warning on **Health**. Erase those sessions by hand after you check who the request was about.
* If a request matches no contact Genesys knows, OpenCX skips it and shows a warning on **Health**. The person may still have sessions in OpenCX under other details: check, and erase them by hand.
* The requests OpenCX filed itself, when you deleted a contact, are never applied back.
* Requests filed in Genesys before you turned the setting on are left alone.

## Who can see what was erased

Each of these is recorded in the [audit log](https://docs.open.cx/security/audit-logs.md):

* Clearing Genesys data after an erasure, including anything Genesys refused.
* Each deletion request OpenCX files. The entry shows who deleted the contact, and the request's Genesys ID so you can follow it in Genesys.
* Each session erased because of a Genesys deletion request.

The entries say which kinds of identifiers a request used, never the values. Only roles with the **Audit logs** permission can see them.

## Related

> [card] [Sessions and sync](https://docs.open.cx/integrations/genesys/conversations.md)
>
> What OpenCX and Genesys exchange for a session.

> [card] [PII redaction](https://docs.open.cx/safety/pii-redaction.md)
>
> Redaction settings for the whole workspace.

> [card] [Permissions](https://docs.open.cx/integrations/genesys/permissions.md)
>
> What the role OpenCX uses in Genesys can do.

> [card] [Troubleshooting setup](https://docs.open.cx/integrations/genesys/troubleshooting-setup.md#health-shows-an-erasure-warning)
>
> Erasure warnings on Health and how to fix them.


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