Availability and permissions
Inbox merges require themerge-sessions:write permission. Merging is available with OpenCX (open), Zendesk (zendesk_v2) or Genesys Cloud (genesys) as the organization’s ticketing system. It is unavailable with other ticketing systems. The merge permission authorizes merging any sessions in the organization, regardless of the merger’s assigned or team session scope.
Any channel can be merged into any other channel. All selected sessions must belong to the same organization. Sessions assigned to AI must first be handed off, unassigned, or assigned to a human. Wait until active calls end before merging.
The same permission authorizes public API and MCP execution. API calls execute directly without a separate acknowledgment field. The MCP tool description instructs the caller to warn the user about the irreversible action before executing it.
Merge from the inbox
- Open the session you want to keep as the primary.
- Open More options and choose Merge sessions into this one.
- Review the Primary session card. Select Change primary to choose a different destination.
- Under Source sessions, search by session number and add one or more sources.
- Choose a closure status for each source and review the permanent-closure, different-contact, and parent-change warnings.
- Complete any Required fields shown beneath the source sessions. Existing answers are prefilled; completed sections show Ready and can be expanded to edit.
- Select Merge permanently.
merge_sessions tool.
Merge from a workflow
Add Merge sessions to a workflow after the steps that identify duplicates and choose the primary. Configure:- Primary session number: the session to keep.
- Source session numbers: a list containing one or more source session numbers. You can map the list from an earlier step.
- Source closure status: Closed resolved or Closed unresolved, applied to every source.
1201 as the primary and pass [1202, 1203] as the sources. For one source, pass [1202]. The action does not detect duplicates or choose the primary itself.
Creating or editing the workflow requires workflows:write; the action runs within the workflow’s workspace. It uses the same merge behavior and supported ticketing systems described on this page. All selected sessions must belong to that workspace. Hand off or unassign AI-owned sessions first, and wait for active calls to end. An invalid source rejects the entire merge; no source is partially merged.
Workflow merges run automatically and bypass the required-field checks that apply when a human merges sessions in the Inbox. This matches other automated and API closures. All other merge safeguards still apply.
What changes
For each source, the merger chooses closed-resolved or closed-unresolved. The source receives theclosed_by_merge tag, an internal entry linking to the primary, and its new parent relationship.
The primary retains its status, assignee, contact, channel, team, priority, tags, and custom attributes. Contact profiles are never combined. Source messages stay in their original history; they are not interleaved chronologically with the primary’s history.
If a source is already an ordinary subsession, merging moves it from its previous parent to the primary. The dashboard warns you about this move. A merge that would create a circular hierarchy is rejected.
Messages received after merging
When an incoming message is addressed to a specific source session, such as an email reply to its original thread, it is stored in that source without reopening it. The primary receives a top-level internal entry identifying the source session and sender, with the message and a link to its original history. This updates the primary’s last-message timestamp without changing its status or assignee. The internal entry is visible to agents, not to customers; its message body is available only to agents who can read the source. Email replies from people outside the source’s participants remain private notes and are also mirrored, preserving the sender and private-note explanation. They never reopen the source or add recipients. It does not add the source contact to the primary’s recipients. When the sessions have different contacts, review the red dashboard warning carefully: a reply from the primary may not reach the source contact. If a voicemail finishes processing after its source was merged, the recording stays with the source and a single internal entry appears in the final primary. The source stays closed, and the entry provides access to the recording subject to the source’s read permissions. Mirrored messages can display their saved translation using your translation display preferences. If no saved translation is available, the original is shown. Native WhatsApp, Messenger, Instagram, and SMS channels keep their normal incoming-message routing: reuse an open session for the contact on that channel, or create a new one. Merging does not redirect these incoming messages into the primary. The merged source stays closed, and the new or existing open session can be replied to normally. Quoting an older WhatsApp message does not change this routing. Redaction preserves merge entries and their source/primary links. Redacted entries hide message content and summaries while keeping the merge trail visible. Redacting a source session also clears its summary; opening a linked source history still requires access to that source.Merging with Zendesk
The merge completes in OpenCX without waiting for Zendesk. Linked Zendesk tickets remain separate; OpenCX does not perform Zendesk’s native ticket merge. Merging tickets directly in Zendesk does not create an OpenCX merge relationship. After the local merge, OpenCX attempts to set each linked source ticket to Closed, regardless of the source’s resolved or unresolved status in OpenCX, and add private merge notes to the source tickets and the primary ticket. Notes include the actor, merge time, OpenCX session links, and Zendesk ticket IDs when available. Each source points to the primary, and the primary lists the sources. Notes contain no message content and do not change the primary’s status or either ticket’s recipients. If a source and the primary share the same Zendesk ticket, that ticket receives private merge notes without changing its status; the source still closes permanently in OpenCX. These updates run in the background with no retries. Missing tickets are not created, and permanently closed tickets cannot receive notes. Merging does not fill required Zendesk fields. Failed or skipped updates do not undo the OpenCX merge or appear in the merge dialog. Once a source ticket is Closed in Zendesk, it cannot be reopened. A customer reply to that closed ticket creates a new Zendesk follow-up ticket; the new ticket does not automatically inherit the OpenCX merge relationship. If closing the Zendesk ticket failed and it later reopens, its OpenCX session still stays permanently closed. New customer and agent replies addressed to that source through Zendesk remain in its history and appear as private references in the final primary. This does not send the reply again, restart AI on the source, or reopen either OpenCX session. Source-history access restrictions still apply.Merging with Genesys Cloud
The merge completes in OpenCX without waiting for Genesys Cloud. Genesys has no conversation merge, so linked Genesys conversations stay separate. After the local merge, OpenCX attempts to label each source session’s Genesys conversation with the primary session ID in theopencx_merged_into participant attribute, then end that conversation. The primary’s Genesys conversation gets the source session IDs in opencx_merged_from. If a source and the primary share the same Genesys conversation, that conversation is not ended. Labels contain no message content.
These updates run in the background with no retries. Failed or skipped updates do not undo the OpenCX merge or appear in the merge dialog. Set the Open Messaging threading timeline to 0 in Genesys Cloud so a customer who writes again does not rejoin an ended source conversation. See Genesys Cloud conversations and status sync.
Merging a primary later
A session can become a merged source only once, but it can receive multiple sources while it remains a primary. If B is merged into A and A is later merged into D, the original links and histories remain. New messages received in B stay in B and appear once in D, identified as messages from B. Neither B nor A reopens.Workflows, billing, and reporting
Merge closure emits the ordinary closure event afterclosed_by_merge has been saved. Workflows can use Get Ticket Tags to check this tag and decide how to handle the closure. The closure event payload does not gain a tags field.
Only a newly completed merge dispatches closure workflows. Retrying an already completed merge does not dispatch them again or recover workflows missed if dispatch was interrupted.
Configured workflow actions may still run, but merged sources cannot be reopened or replied to. Merging does not change billing or transfer or reset SLAs. Use closed_by_merge in your reporting to distinguish merged closures from other outcomes.