Skip to main content
The Inbox is a centralized place to view, manage, and take action on your customer support sessions across all your channels (email, chat, phone, etc.).
  • You will be able to see all your customer support sessions in one place.
  • You can take action on your sessions from the Inbox (reply, change status, add notes, share, etc.). See Session actions and AI writing tools.
Built-in views:
  • All sessions - Every session you can access, including snoozed sessions, most recent message first.
  • Assigned to me - Sessions assigned to you.
  • Snoozed - Snoozed sessions, earliest wake-up first. Shown when your workspace uses native OpenCX ticketing and session snoozing is on.
Hover over the last-message preview on a session card to read its full text in a tooltip without opening the session, just as you can with the session title. For long messages, move your pointer into the tooltip and scroll to read the rest. When the latest message is an internal comment, the card and tooltip show it with an Internal note: prefix. A newer reply replaces the comment preview; editing an older comment does not make it the latest. The same preview appears on session cards in contact history. This preview does not change session ordering or unread status.

Clear notifications

Open Notifications in the sidebar and select Personal or Team. Choose Clear all beside the selector to remove every notification in that view, including read notifications and older items you have not scrolled to. Clearing applies only to you in the current workspace. Clearing Team does not remove your teammates’ notifications. The other view stays unchanged, and new notifications still appear normally, including new replies to sessions you cleared. Clearing notifications does not change the sessions themselves. Cleared notifications cannot be restored from the notification list.

Session notification sounds

Workspace admins can choose sounds in Settings → Notifications → Session sounds. Each row has a sound dropdown and Preview:
  • Session activity plays when a different session moves to the top of your current inbox view.
  • Customer reply plays when a new customer reply appears in your current inbox view, including an existing session that enters the view because of the reply.
If a reply also moves its session to the top, only the customer reply sound plays. The first customer message in a new session uses Session activity, not Customer reply. If the session already appeared at the top before that message arrived, it is not announced twice. Later customer messages use Customer reply. Sounds work while the Inbox is open, even when no session is selected. Opening or switching inbox views, or loading more history, does not replay old replies. A later teammate or automated response does not hide a new customer reply. Replies from teammates, AI, or workflows and spoken turns during calls do not trigger the customer reply sound. This includes calls inside a web session; written customer replies in that session still play their selected sound. Several replies appearing in the same refresh produce one cue. Choose from Default, Chime, Pop, Bell, Soft ping, Double beep, Doorbell, and Gentle chord, or select Off for silence. Use Preview to compare sounds before testing them with incoming sessions and replies. The selected sounds apply to everyone in the workspace. Default keeps the existing session activity sound; customer replies use Pop initially. Choose Off to silence an event for the workspace. Saved choices update open dashboards. To mute both session sounds for yourself, open a session’s ⋯ menu and turn off New message notifications. This existing switch applies across sessions in that workspace in your browser and syncs across its tabs. Turning it back on does not replay activity that arrived while muted. Sound previews still work while muted. Call sounds and desktop notification preferences are separate. If you cannot hear a preview, check your browser’s sound permission and device volume.

View images in email sessions

In the original email view, wide images shrink to fit the available message width, including when you resize the Inbox panels. Their proportions stay the same. Click an unlinked image to open the image viewer. Use Previous image and Next image, or the left and right arrow keys, to browse loaded, unlinked images in that email. Use Download to save the image and Close or Escape to return to the session. You can also focus an image with Tab and press Enter or Space to open it. Small logos, icons, tracking pixels, and spacers are excluded from the image viewer. Images that link to a website keep their original links. Blocked remote images remain blocked until you choose Show remote images; the viewer does not load them automatically.

See who is viewing a session

Small teammate avatars on the right of an Inbox session card mean someone else is viewing that session. They appear to the left of the summary icon when one is shown. Up to three avatars overlap in a stack; +N counts any additional viewers. Hover over the indicator to see everyone’s names; scroll inside the tooltip when the list is long. Your own avatar is excluded, and multiple tabs belonging to one teammate count once. Viewing is separate from assignment and does not prevent you from opening or replying to the session. Indicators refresh about every 20 seconds while your Inbox tab is visible. After a browser closes unexpectedly, an indicator can take about 50 seconds to disappear. An absent indicator is not a guarantee that nobody else is working on the session.

Answer an AI help request

With Team in the loop enabled, the AI can mention you in an internal Inbox note when it needs help. The customer sees the AI’s progress message, while the note and your thread reply stay private.
  1. Open the session from the mention notification or find it with the AI needs help tag.
  2. Open the help note’s thread and reply with the answer or confirmation the AI needs.
  3. The AI follows up with the customer in the same session. If another question joined the note thread, answer the latest request there.
You can also reply directly to the customer. That answers the open help request, and the AI resumes when the customer next writes.

Reply without taking over

When Team in the loop applies to an AI-assigned session, typing and sending replies keep AI assigned, even if it has not asked for help. Before your first direct reply, a dialog offers:
  • Send reply — send your message and keep AI available.
  • Take over and send — assign the session to yourself, then send.
  • × — close the dialog and keep the draft unsent.
The choice is acknowledged once per member and workspace in that browser. Later replies send without the dialog. To take over at any time, open the AI assignee menu in the session header and choose Take over.

Review past requests

Filter by the AI needs help tag and include closed sessions to review past requests. Save those filters as a view to return to them later. The tag remains after an answer or takeover, so tagged sessions are a history of requests, not a list of unanswered ones.

Send and resolve

To reply and resolve an open session in one action, write your reply, open the arrow beside Send, and select Send and resolve. You can also press ⌘⇧Enter on Mac or Ctrl⇧Enter on Windows and Linux. The main Send button and your existing send shortcut continue to send without resolving. If your workspace requires Structured Fields before closing, complete the form first. The form follows the session team’s requirements and includes values already recorded. Choose Send and resolve to continue, or Cancel to keep your draft unsent. The session resolves after the reply succeeds. If the reply fails, the session stays open and your draft remains. If the reply succeeds but resolution fails, use Resolve session in the same menu to retry without sending the reply again. After successful resolution, your preference to open the next assigned session still applies. This action requires permission to update sessions. It is available for replies to open sessions; internal notes and WhatsApp template sending keep their existing behavior. If your workspace locks Resolved, Send and resolve and its shortcut are hidden; use a Send and [status] entry instead. Workspace admins can change the Send and resolve shortcut under Settings → Workspace → Replies → Send and set status. Select Change shortcut, press a new combination, then select Save shortcut. The default is Ctrl+Shift+Enter on Windows/Linux or Cmd+Shift+Enter on Mac. After saving a custom shortcut, select Reset to default beside the shortcut control to restore this default immediately. The reset action disappears once the default is saved. Ctrl/Cmd, Shift, and Alt/Option are optional; you can also choose an unused function key such as F8. Shortcuts already used by other actions are rejected. Shortcuts that would type text work only outside text fields, so normal typing is preserved. The shortcut shown in the Send menu follows the workspace setting. This changes only Send and resolve; sending normally and choosing custom statuses from the menu keep their existing behavior.

Send and set a custom status

Workspace admins can add custom statuses to the same menu under Settings → Workspace → Replies → Send and set status. Each enabled status appears as Send and [status], in the order it was added. Choosing one sends your reply and then applies that status. A status that closes the session follows the same rules as Send and resolve: the Structured Fields form, the retry option (Set [status]) if only the status change fails, and your open-next-session preference. A status that keeps the session open skips those steps. Statuses limited to certain teams only appear for agents in those teams.

Delete your own message

You can delete a reply you sent to a customer on a web chat session. On Widget 5.4.4 or later the reply disappears from the customer’s open chat; earlier versions drop it the next time the chat loads. In the inbox, the session keeps a Message deleted marker where the reply was, and the timeline shows an event naming who deleted it. Hover the event to read the deleted text, so your team keeps the context. Attachments on the deleted reply are removed, and the audit log records the deletion as Deleted a message. Deleting keeps the text for your team and cannot be undone. To remove sensitive content from a reply, use Redact Message rather than deleting it. Deleting requires the Delete own messages permission, plus write access to the session (see Limit a role to its assigned sessions). The Admin role has it by default. To give it to another role, open Settings → Roles, edit the role, and turn on Delete own messages. You can delete only your own replies, and only on web chat sessions. Messages on other channels, replies sent by teammates, and AI or workflow messages cannot be deleted. Copies already delivered outside OpenCX, such as an email notification of your reply, are not recalled. To delete a reply, open the options menu on your message, select Delete message, then Delete.

Add Cc recipients to an email session

When replying to an email session or creating a New session by email, type directly in the Cc field. In New session, select Cc first if the field is hidden. Matching contacts appear beneath the field as you type a name or email. Select a result, or enter a full email address and press Enter, comma, or space to add it. Contact search requires permission to read contacts; you can still enter an email address without it. Keep typing to add more recipients. Each address appears as a removable pill. Press Backspace in an empty Cc field to remove the last recipient. The current To address and addresses already in Cc cannot be added again. Moving a Cc recipient to To removes it from Cc; changing To again does not add it back. Entering a full email address selects that exact address, even when other contacts have similar names or addresses. For sub-sessions, turning on Include parent context clears untouched parent Cc suggestions. Cc recipients you explicitly edited are retained.

Change an email session’s primary contact

In a native OpenCX email session, select the recipient beside To above the reply composer. Search for an existing contact by name or email, or enter a new email address and select Use. Contact search requires permission to read contacts; you can still enter an email address without it. Review Cc, then select Send. Sending transfers the existing session to that person as its primary contact. Editing the draft or opening Preview does not transfer the session. If the new contact has no name yet, their email address identifies them in the inbox. When they reply with a sender name, that name appears on their contact.
  • The new primary contact receives your reply and earlier customer-visible history. Earlier file attachments are available as download links beside their original messages in that history. Internal notes and unsent AI suggestions are excluded.
  • Existing Cc recipients remain editable. The previous primary contact is not automatically added to Cc and receives no new email unless included.
  • The timeline records who changed the primary contact, the previous and new contacts, and when the change happened. Earlier messages keep their original authors.
  • Replies from either the new contact or an earlier participant can join the same session. An earlier participant’s reply does not change the primary contact back.
  • Existing AI and human-assignment rules continue. Changing To is a human action; it does not introduce an additional automation mode.
Ordinary Send displays your reply and clears the composer immediately. You can continue working while the email is prepared and sent. If the request fails, the notification offers Retry email for the same message, including its recipients and files. If you have not started another draft, the failed reply is also saved as a draft for your next visit to that session. If delivery fails after the transfer is saved, the new primary contact remains. The email shows its delivery status; use Retry email to retry that message. If sending is interrupted, OpenCX resumes the saved attempt once the previous send is no longer active. Emails already accepted for delivery finish their session updates without being sent again. Older unconfirmed sends require delivery review. Reopening a saved email draft keeps its files and quoted-message reference, so retrying an unchanged draft continues the original send. File removals and changes to the quoted message are saved separately, so reopening an edited draft keeps those edits. Automatic recovery keeps the current assignment if the original author has left the organization. Retrying preserves its original author and recipients without replacing an existing human assignee or reopening the session. If the requested takeover from AI did not complete, retrying finishes it as the teammate who selects Retry email. The session is marked read for that teammate. Redacting email content removes saved delivery copies and disables existing retries in that session and sessions containing linked copies of the redacted messages. If another agent changes the contact while you are drafting, review To and Cc before sending. Send and resolve resolves the session only after sending succeeds. Changing To shares a session’s customer-visible history. For a separate exchange with a supplier or colleague, use a linked sub-session instead. To editing supports one recipient plus Cc in native OpenCX email inboxes and eligible Zendesk email sessions described below. Other integrations and campaign mailboxes are not supported. Sending requires permission to write sessions.

Zendesk email recipients

For workspaces with recipient synchronization enabled, the same To and Cc controls are available on email sessions linked to a Zendesk ticket. A teammate with permission to manage integrations can turn on Edit To and Cc under Settings → Ticketing → Email sessions in Zendesk. After reconnecting Zendesk, turn it on again to verify setup. Turning it off pauses new edits in OpenCX while incoming Zendesk changes and pending reply recovery continue.
  • Send saves your To and Cc changes to the existing Zendesk ticket and sends the reply. Direct replies without To or Cc edits use the recipients already saved in OpenCX. When Zendesk delivers a reply, its current ticket recipients and notification rules apply, including changes that have not yet synchronized to OpenCX. Zendesk changes reach OpenCX through synchronization; sending an ordinary reply does not refresh or rewrite the Zendesk recipient list. For direct delivery, the selected recipients stay with that email during preparation and translation. Later synchronized changes apply to subsequent replies. Retries retain their saved addresses; if recipients have since changed, review is required before an unsent retry can proceed. Opening a preview or editing a draft does not change the Zendesk requester.
  • Requester and email Cc changes submitted in Zendesk also update OpenCX, even without a new comment. Adding or removing a Cc updates the corresponding list in both places.
  • A primary-contact change adds a system event; a Cc-only change does not. Changes made in Zendesk are shown as by Integration; changes made in OpenCX show the agent’s name. Earlier messages keep their original authors and remain in the same session.
  • If recipients change while you are drafting, your text and files stay in the composer. Review the displayed To and Cc, then choose Use reviewed recipients before sending.
  • If recipient editing is paused, choose Use current recipients to discard your To and Cc edits while keeping your reply text and attachments.
  • An AI answer prepared for the former primary contact is cancelled. AI can answer the new primary contact when assigned, using the existing assignment rules.
Your existing delivery setting still applies. With a connected inbox that sends directly, recipient edits are saved to an editable Zendesk ticket first and the sent email is recorded as a private note. If Zendesk leaves out a newly added Cc, OpenCX keeps that address in Cc and sends the email anyway, including when Zendesk restricts light agents. These OpenCX-only Cc addresses remain selected through later synchronization until removed in OpenCX. Zendesk does not list them, and its refusal alone does not show a send error. If the email fails, the confirmed recipients remain saved. If only the private note fails, OpenCX retries the note without sending the email again. If delivery is uncertain, retry the same message instead of composing a duplicate. If the linked Zendesk ticket is closed, an inbox configured to send directly can still change To and Cc and send replies. These recipient changes are saved only in OpenCX; the closed Zendesk ticket keeps its previous requester and Cc list. Later synchronization does not overwrite the recipients saved in OpenCX. The private copy is skipped without retrying the delivered email. An inbox configured to send through Zendesk cannot send a reply on a closed ticket and shows an error. The controls are unavailable for unlinked sessions, deleted or shared Zendesk tickets, non-email channels, and campaign mailboxes. Zendesk uses the selected user’s primary email address; a secondary address may require choosing that primary address instead.

Create sub-sessions

A sub-session is a separate session linked under the one you are viewing — use it for a follow-up exchange that should not share the customer-visible history, such as a thread with a supplier or another team. Open the Sub-sessions card in the session sidebar and select Create sub-session. Creating one requires permission to manage sub-sessions.
  • Contact auto-fill. The dialog starts with the parent session’s contact already picked, since most follow-ups go back to the same customer. You can clear or swap the recipient before creating. A workspace admin can turn this off under Settings → Workspace → Sessions → Sub-sessions (Auto-fill contact on sub-session creation); with it off, the parent’s contact is offered as a one-click suggestion instead.
  • Draft protection. If you have typed a message or attached files, closing the dialog — clicking outside it, pressing Escape, or selecting Cancel — asks before discarding the draft. Keep editing returns to the dialog exactly as you left it.
  • Automate on creation. The Sub-session Created workflow trigger fires whenever an agent creates a sub-session, carrying the new session and its parent. Use it to apply macros, routing, or AI steps to every follow-up thread automatically. Sub-sessions opened by a workflow’s own Create Sub-session action do not fire it, so flows cannot re-trigger themselves.
  • Filter the Inbox. Add the Session Type filter: is Sub-session lists only sub-sessions, is not Sub-session hides them, and is Has sub-sessions lists the sessions that have at least one. Save it as a view to keep the list.

Change the session subject

Hover the session name in the session header and select the pencil icon to open Edit subject. Type the new subject and select Save or press Enter; Cancel or Escape closes it without saving. A subject can’t be empty and is at most 255 characters. Changing it requires permission to edit assigned sessions. The new subject replaces the email subject or AI-generated title everywhere in OpenCX, and the AI title never overwrites it afterwards. The change shows on the session timeline with the agent who made it. It is not sent to connected helpdesks. On email sessions, replies sent after the change use the new subject, so most mail clients show them to the customer as a new conversation. When Show summary as subject is on for the session’s channel and the session has a summary, the header shows the summary instead, so the pencil is hidden.

Set session priority

Priority is off by default. With native OpenCX ticketing, a workspace admin can open Settings → Workspace → Sessions → Session priority and turn on Enable session priority. Changing this setting requires Helpdesk settings write permission. Priority is not connected to other external ticketing integrations. With Genesys Cloud, a priority change also reaches the Genesys conversation (see Genesys conversations). Once enabled, changing a session’s priority requires Sessions write permission.
  1. Open a session and select Set priority beneath its title, or select its current priority badge.
  2. Choose a standard or custom priority from your workspace’s list. Choose None to clear the priority.
  3. Check the internal timeline to see who changed it. Priority also appears on session cards.
Sessions start with None. Priority stays set when a session closes, reopens, or moves to another team. It does not change the assignee, send a customer message, or set an SLA target, and it does not increase automatically as the customer waits. Use the Priority filter to find sessions at a particular level, or select Priority in the sort menu. Descending order follows your workspace’s configured order, highest first and None last. Ascending reverses that order. Sessions at the same level are ordered by their last activity. Changing the display order does not change automatic assignment. Turning the workspace setting off hides the priority controls, filters, sorting option, and new workflow action. Teams return to their default waiting order, and saved priority filters and sorts are ignored. Saved priorities, team assignment settings, and timeline history are kept and become available again when re-enabled. For agents who serve multiple teams, workspace admins can enable Prioritize across Priority-first teams in the same Workspace settings section. It compares eligible waiting sessions across those teams while preserving each team’s assignment delay. It is off by default; see cross-team priority assignment.

Create and order custom priorities

Open Settings → Workspace → Sessions → Session priority with Helpdesk settings write permission. Enable session priority to manage the list.
  1. Select Add priority, enter a unique name such as VIP or Security, choose a Priority color, and select Save. The color styles the whole priority pill—flag, text, border, and tinted background—on session cards and in the session header.
  2. Once an active custom priority exists, the Priority order list appears. Drag the priority to its place, highest first. You can also focus its move handle, press Space, use the arrow keys, and press Space again.
  3. Use the pencil to edit a custom priority’s name or color. Select Reset to return to the default appearance. The standard names stay fixed, and None always remains lowest.
New priorities start just above None. Standard and custom levels can be reordered together—for example, Security → VIP → Urgent → High → Medium → Low → None. The order is shared by the Inbox, workflow pickers, and teams using priority-based assignment. Changes apply to waiting sessions on subsequent assignment passes and do not move existing assignees. To remove a custom priority, select its trash icon and choose a replacement. Existing sessions, saved filters, and workflow actions and conditions use the replacement automatically. Renaming or removing a priority does not rewrite names in historical timeline events. Standard priorities cannot be removed. Removing the last active custom priority hides the ordering list; Add priority remains available, and the saved order is kept.

Set priority in a workflow

Add Set session priority, select the session number, and choose a standard or custom level. Use Session priority in a workflow condition to branch on levels such as VIP. Place this action before the team assignment step when priority should affect that assignment. Changing priority alone does not start a Session Updated workflow. While the workspace setting is off, existing priority actions are skipped and the rest of the workflow continues. Conditions can still read saved priorities. Existing actions and conditions follow the chosen replacement if a custom priority is removed. Automatic assignment uses priority when the team selects Priority first or SLA first. See team assignment order for how priority, SLA deadlines, and waiting time interact.

Pin tags to the session header

Pin a tag to keep it in view while you work a session, for example a customer tier or the topic of the request. A pinned tag shows in the session header as a pill with its icon and name, and on the session’s card in the list as a small round chip with its icon only; hover a chip to read the tag name. Pinning requires Sessions write permission.
  1. Open the session and find the tag under Session tags in the session sidebar.
  2. Right-click the tag and select Pin tag. It appears in the header straight away. In the sidebar, pinned tags move to the front of the list and show a pin before their name.
  3. To unpin it, select that pin, or right-click the tag and select Unpin tag. The tag stays on the session.
To remove a tag from the session, hover it and select the x, or right-click it and select Remove tag. A pin belongs to one session: pinning a tag on one session does not pin it on others. Removing a tag from a session also unpins it. A session card shows up to four pinned tags and counts the rest; the header shows all of them, in the order they were pinned.

Show pinned tags side by side or stacked

Workspace admins choose how session cards show pinned tags in Settings → Workspace → Inbox layout → Pinned tags in the session list. Changing it requires permission to edit workspace settings.
  • Default: each pinned tag sits side by side.
  • Compact: pinned tags stack to save room, and spread out when you hover them.

Give a tag an icon and a color

Open Settings → Tagging, select a tag (or New tag), and use the Icon and Color pills under the tag name. Choose No icon or No color to clear one. Changing tags requires permission to edit tag settings. The color styles the whole tag (icon, name, border and a light tint) in settings, in the session sidebar and in the session header; on a session card the pinned tag’s chip takes the color. A pinned tag without an icon shows a tag symbol.

Pin tags in a workflow

In a Tag Ticket step, turn on Pin to session header to add the tag and pin it in one step; it also pins a tag the session already has. Add Unpin Tag to take a tag out of the header while keeping it on the session. Remove Tag from Ticket removes the tag and its pin.

Snooze a session

For native OpenCX ticketing, enable Settings → Workspace → Sessions → Session snoozing → Enable session snoozing. It starts off. Changing the setting requires Helpdesk settings write permission; snoozing from the inbox requires permission to update sessions. Select Snooze from an open session’s status menu. Choose 1 hour, 3 hours, Tomorrow at 9 AM, 3 days, Next Monday, 1 month, or a custom date and time. Times use your local timezone. 3 days keeps the same local time. Next Monday returns at 9 AM, the following week if today is Monday. 1 month keeps the same local time and uses the last day of the next month if that month is shorter. Only human-assigned or unassigned sessions can be snoozed; sessions with an active call cannot be snoozed. Snoozed sessions leave working views and free agent capacity. They remain unresolved, keep their assignee and custom status, and stay accessible through All sessions, search, direct links, and the Snoozed view. The Snoozed view lists the earliest wake-up times first. When sorting mixed views by Snooze time, sessions without a scheduled return appear last. Use the Snooze filter to include or exclude snoozed sessions in a saved view. A session returns when its snooze time arrives, a customer replies, an active SLA breaches, a new call starts on the session, or an agent selects Open to unsnooze it. A wake-up is scheduled for the chosen deadline; it does not wait for the periodic recovery check. Select Snooze again to adjust the deadline. Agents’ replies, notes, and human reassignment do not end Snooze. Customers do not see a snoozed status. SLAs continue under their existing rules. Inactivity follow-ups wait while the session is snoozed and start a fresh inactivity period after it wakes, where applicable. Workflows already running are not suspended. When a customer reply, snooze expiry, SLA breach, or a workflow’s Reopen action wakes a session, an agent who is offline in the workspace is unassigned by default. The session stays with its support team and returns to the team’s normal assignment queue. If no eligible agent has capacity, it waits unassigned; sessions without a support team remain unassigned for manual routing. Online agents keep their sessions even when at capacity or unavailable for that team. Manually opening a session, starting a call, or disabling snoozing preserves its assignment. With Snooze enabled, workspace administrators can turn on Keep assigned agent when recently offline and set Offline threshold (hours), initially 12. This option starts off. When a session wakes, it keeps its assigned agent if the agent has been continuously offline for less than the threshold. At or above the threshold, or when the offline start time is unknown, normal queue routing applies. The check happens only when the session wakes; it does not reassign the session later if the agent remains offline. Changing between offline statuses does not restart the offline period. Agents already offline before tracking began use normal queue routing until their next online-to-offline transition. Closing a session or assigning it to AI cancels Snooze. Disabling session snoozing returns existing snoozed sessions to active work on the next processing cycle. Snooze is available in the inbox and through the Snooze Session workflow action. This feature does not add external integration synchronization or bulk actions.

Snoozed sessions in custom dashboards

Ask Companion to add a Snoozed count or session list to a custom dashboard, including scheduled wake-up times. No additional workspace setting is needed to report on Snooze; normal reports permissions apply. Existing custom dashboards need to be updated to use this information. For custom analytics queries, report_sessions exposes snoozed_at and snoozed_until. A snoozed session still has main_status = 'open'. Use snoozed_until IS NOT NULL for Snoozed sessions, and main_status = 'open' AND snoozed_until IS NULL for active Open sessions. The timestamps clear when the session wakes. Reports reflect the latest synced state, so a recent change can take a short time to appear.

Snooze from a workflow

With Enable session snoozing on, add Snooze Session to a workflow. Set Session Number (for example, the triggering session’s number) and Snooze Duration to a preset (5, 15, or 30 minutes; 1 or 3 hours; or 1 day), or choose Custom duration and enter at least 1 minute. The duration starts when the step executes. The workflow continues to its next step immediately; Snooze does not wait for the session to wake. The same eligibility and wake-up rules apply as inbox Snooze. The timeline records which workflow run snoozed the session. If the workspace setting is disabled before execution, the step fails without changing the session. Use the Reopen action to end native Snooze from a workflow. It clears Snooze and the custom sub-status. With session snoozing enabled, an offline human assignee follows the workspace’s offline threshold setting described above; with the option off, the session returns to its team’s queue. An online assignee stays assigned. The timeline records the workflow that woke the session.

Use Snooze in workflow conditions

In a Session Updated workflow, watch Status and compare {{trigger.ticket.ticketStatus}} with snooze in an If/Else condition. Entering Snooze and returning to Open fire status updates. Changing only the wake-up time does not fire another status update. Group by → Status also places these sessions in their own Snooze group.

Correct session attributes

Use session attribute dropdowns to search a predefined list and correct a contact reason or another session attribute. Link an enum under Settings → Structured Fields, then select a value directly in the session sidebar.

Group sessions

In Filters → Group by, choose Custom status, Tags, Contact attribute, or Session attribute alongside the existing channel, assignee, status, AI status, language, and support team options. Custom status puts sessions without a custom status in a No custom status group. For an attribute, select a suggested key or type its exact name. The list stays ungrouped until you choose a key. You need permission to edit personal or shared views to change grouping. Save the view to keep its grouping and attribute key.
  • Tags: A session appears under each of its tags. Sessions with no tags appear under Untagged, so a tagged session can appear more than once in the list.
  • Contact attribute: Uses the linked contact’s verified attributes.
  • Session attribute: Uses the session’s attributes, including editable attributes when the same key is absent from its stored attributes. If a key exists in both, the stored value takes precedence, even when empty.
Attribute groups support text, numbers, and booleans. Missing, null, and empty values appear under Not set, always at the bottom. Objects and arrays appear in a separate Object / array group. Hidden attributes remain hidden and cannot be used to recover their values through grouping. Grouping covers loaded sessions only. Scrolling loads more sessions into the groups; the API still returns individual sessions. Other groups appear in the order their first session occurs, and sessions keep their sort order within each group. Choosing None restores the flat list. The right side of each group header shows the full number of matching sessions you can access across the whole view, including sessions that have not loaded yet. Counts refresh about once a minute while the Inbox is visible and can briefly lag session changes. A blank count means it is still loading or unavailable; it does not prevent you from opening or browsing sessions. Groups still appear as their sessions load. Counting does not change the list’s ordering or scrolling. A session with several tags counts once in each matching tag group, so adding tag counts can exceed the number of unique sessions.

Collapse session groups

Choose a grouping in Filters → Group by. Each group starts expanded. Click its header or chevron to collapse its sessions and bring the next group into view; click again to expand it. You can also focus a group header and press Enter or Space. This works with every grouping option. While you scroll through a group’s sessions, its header stays at the top of the list. Click the pinned header to collapse the group without scrolling back up. The header changes as you reach the next group, and its count stays on the right. Collapsing a group only changes the list display. It does not change the sessions or the view’s filters. Groups cover loaded sessions and update as more sessions load. Collapsed groups stay collapsed while you browse the inbox; reloading the page expands them again.

Limit a role to its assigned sessions

Under Settings → Roles, the Inbox permission has two nested rows: Team sessions, and under it Assigned sessions. Inbox grants both automatically, and Team sessions grants Assigned sessions. To limit a role, untick Inbox and keep the row you want ticked, with read or write as needed:
  • Team sessions: the agent sees the sessions assigned to them and the unassigned sessions waiting in the teams they belong to.
  • Assigned sessions only: the agent sees just the sessions assigned to them.
Read and write are limited separately. A role can hold Inbox read with Assigned sessions write, for example: the agent sees every session but can reply to, assign or change only the ones assigned to them. Every other session is out of reach: it does not appear in the inbox list, saved views, search results or exports, and opening it by link shows the same not-found page as a deleted session. Its messages, notes, tags and attachments are hidden with it. Once a session is assigned to the agent, or lands in one of their teams’ queues for a Team sessions role, it appears; when it is reassigned to someone else, it disappears again. The rest of the inbox works as before for a limited role: macros, translations, skills, priorities and integration panels inside a visible session all keep working. Contacts are not limited by this setting; use the Contacts permission to hide the directory from a role.

Workspace settings

Open Settings → Workspace to manage defaults for everyone in your workspace. Choose Inbox, Replies, Sessions, Agents, or Session details to see the settings in that category. Editing requires Helpdesk settings write permission; teammates with read access can view the settings. For every setting on this page, see Workspace settings. Use Find a workspace setting… to search across all five categories. For example, search first name to find agent-name privacy settings, or snooze to find session snoozing when your workspace uses native OpenCX ticketing. While searching, results replace the category tabs. Clear the search or press Escape in the search field to return to your previous category. Press / outside an input or dialog to focus settings search. Use the arrow keys to move between category tabs when a tab has keyboard focus.

Emoji picker

The emoji picker is off by default. A team member with Helpdesk settings write permission can enable Emoji picker under Settings → Workspace → Replies. The setting applies to every agent in the workspace. When enabled, click the smiley button in a reply, internal note, or new-session composer. The picker opens beside the button. Search by emoji name, or use the category tabs to jump through the list. The selected tab follows your scrolling. Select an emoji to insert it at the cursor. The picker closes and returns you to your message. Use the arrow keys to browse, Enter to select, or Escape to close without inserting. Frequently used emojis are remembered for your account in the current browser; they do not sync between devices. The picker uses default emojis with your device’s appearance. Emojis are sent as text, so their appearance can differ for the recipient.

Assignment

Under Settings → Workspace → Sessions → Assignment, workspace admins decide when agents get assigned to a session without assigning it manually:
  • Auto-assign on typing: pick the channels where a session is assigned to an agent as soon as they start typing a reply.
  • Assign on reply: on by default. Replying to a session assigns it to the agent who replied. Turn it off to keep the current assignee, for example when another system decides who owns a session. Agents can still assign sessions manually, and taking a session over from the AI still assigns it to the agent.
Changing these settings requires Helpdesk settings write permission.

Personalization

For each agent’s own inbox preferences, see Personalization.

Session tabs and panel scrollbars

Under Settings → Workspace → Inbox → Inbox layout, workspace admins can configure:
  • Open sessions in tabs by default: on initially. Agents can override it under Settings → Personalization → Inbox → Open sessions in tabs, or select Use workspace default to follow their current workspace again. Personal overrides follow the user across workspaces. Existing personal tab choices are reset once when this workspace default is introduced; agents can choose again.
  • Show contact names in session tabs: off initially; this option appears when workspace tabs are enabled. When enabled, tabs show the contact’s name instead of the session number. Missing names fall back to the number. Name tabs show only the title/subject and session number on hover; number tabs keep their regular session-heading tooltip. Hide contact name continues to apply to session cards and headers, independently of tab labels.
  • Show inbox panel scrollbars: off initially. When enabled, the session list and session details each show a slim draggable scrollbar while your pointer is over that panel, if its content overflows. The scrollbar hides when you leave the panel. Each panel scrolls independently.
Tab labels and panel scrollbars apply to everyone in the workspace. Turning tabs off hides the tab strip without deleting saved tabs.

Views sidebar

Enable Show views in sidebar under Settings → Personalization → Inbox to keep views beside the session list. Search views by name, select a view to open its sessions, and see counts alongside each view. Contact and session attributes remain on the far right with their existing resize and hide controls. Use Create view (+) to build a view, the row’s Actions menu to edit or delete it, and Manage views for saving filters, saving a new view, or reordering personal views. Available actions depend on your permissions. Shared ordering and your workspace’s visibility settings still apply. Workspace admins can enable Show views in sidebar by default under Settings → Workspace → Inbox → Inbox views. Changing this setting requires Helpdesk settings write permission. It starts off and applies to teammates without a saved personal sidebar choice. An existing personal on/off choice is preserved. Your personal choice follows your account across browsers and workspaces and does not affect teammates. To follow the active workspace’s default again, select Use workspace default beside the sidebar switch in Personalization. Changing another personal preference does not stop you from following the workspace default. Smaller windows automatically use the dropdown; widening the window restores the sidebar unless you have hidden it. Press V to search views in either layout. Use Hide views beside the active view name to give the session more space. The same button becomes Show views so you can bring the sidebar back. Your selected view, open session, and unsent reply stay in place. The collapsed state is remembered in this browser without changing your Personalization setting.

Group views into categories

Shared views can be grouped under categories. In Create view, Save as new view, or Edit view, type a Category or pick an existing one from the suggestions. The field appears for shared views and needs permission to manage shared views; personal views are never categorized, and making a view personal removes its category. Names match regardless of capitalization and surrounding spaces, so “Sales” and “sales” are the same category. Leave the field empty for no category. In the views sidebar, each category is a collapsible group under Shared views, named after its first view, with its views inside. Select a category to collapse or expand it; the views sidebar remembers your choice in this browser. Searching views shows matches inside collapsed categories too. In the dropdown, each category appears as its own heading. Under Settings → Workspace → Inbox → Shared views order, drag categories and uncategorized views into the order everyone sees, and drag views within a category to order them there. In the same list, use the pencil on a category to rename it on every shared view that uses it, or the trash icon to remove it; removed categories leave their views uncategorized. Renaming onto an existing category merges the two. Renaming and removing need both Helpdesk settings write permission and permission to manage shared views, and apply to restricted views too.

Filter views

Use Filter views, the filters button beside Create view (+), to list only the views whose saved filters include the filters you pick. It uses the same filters as the session list, and only changes which views the sidebar lists: views and their sessions stay as they are.
  • A view is listed when it has the same filter with the same is or is not and every value you picked. Status is Open lists a view filtering on open sessions, or on open and closed ones, but not a view where status is not Open.
  • Filters combined with AND must all be part of the same AND group in a view. Groups combined with OR list views that match any of them.
  • Dates, custom data and SLA statuses must match the view’s value exactly. A filter with no value picked yet lists every view.
  • Built-in views are filtered the same way, so All sessions, which has no filters, is hidden while a filter is set. An assignee of Me matches views saved for “Me” and for your own name; Unassigned matches views saved for unassigned sessions.
While a filter is set, collapsed categories open to show their matching views, and searching by name narrows the list further. The number on the button shows how many filters are set; select Clear All in the menu to see every view again. The views filter is remembered in this browser.

Session sidebar layout

Workspace admins decide what the session sidebar shows and in which order, either from a session or under Settings → Workspace → Session details → Session details cards. Changing it requires Helpdesk settings write permission.
  • Adjust widgets in a session’s ⋮ menu makes that session’s sidebar editable in place. Everything looks as agents see it: the session list and the conversation stay as they are, and cards with nothing to show stay hidden. Point between two cards, or above the first one, and a + opens a gap. Select it and it grows into a panel that reaches out to the left of the sidebar, while the cards stay where they are. The panel lists everything that isn’t in the sidebar yet, each as it looks in this session: built-in cards first, then a line, then mini-app widgets. Search at the top to narrow the list, pick one to put it there, or press Esc to close. Cards for channels or integrations your workspace doesn’t use, such as X posts, app store reviews or AI call recordings, aren’t offered.
  • Companion can arrange the same layout when you ask it to, such as moving a widget between two cards, and the REST API and MCP expose it too (see Session sidebar).
  • Drag cards up and down to reorder them. While you drag, the card shrinks to a row and the sidebar is outlined; it returns to full size where you drop it. The buttons on each card (move up, move down, ×) do the same without dragging, and keyboard users can pick up a card with Space and move it with the arrow keys. ⌘Z or Ctrl+Z steps back.
  • Undo, Cancel (or Done) and Save sit in the session header, next to the ⋮ menu. Nothing changes for agents until you select Save. Opening another session, going back or leaving the inbox ends Adjust widgets, and you’re asked first; if another admin saved a layout while you were editing, you’re asked before yours replaces it.
  • Any card can be taken out, the contact card included, so the sidebar can show only your widgets.
  • Every widget is its own card in the sidebar, in the same place the widgets have always been, until you move it. A widget appears for everyone it’s shared with, on the channels it’s enabled for, and only the layout removes it. A newly shared widget nobody has placed shows up in that same place.
  • If the layout holds widgets you can’t see (not shared with you, or deleted), Adjust widgets keeps them in place; select Remove them to drop them when you save.
  • Reset to default in Workspace settings restores the built-in cards and also removes widgets placed in the sidebar; you’re asked first when there are any.
  • Widgets show their name only, without a description underneath.
Most cards appear only when they have something to show. Session notes remains available even when empty.

Session notes

Keep reminders and a plain-text to-do list for a session in Session notes. Each session has its own pad, shared with agents who can access that session. Agents with permission to edit the session can update it; agents with read-only access can read it. Notes stay with the session when it is reassigned and are separate from its message history. Customers and AI cannot read the pad. Session notes is off by default. An admin with Helpdesk settings write permission can enable it under Settings → Workspace → Session details → Session details cards, or add it through Adjust widgets. It starts after Contact and can be reordered. The public sidebar layout API can reorder or hide the card, but does not independently enable it. Edits save automatically after you pause typing. If a save fails, your edits remain in that session’s pad; select Retry. You can switch sessions or visit other dashboard pages while a save is pending or has failed; each session keeps its own draft when you return. Leaving the dashboard with unsaved edits asks you to stay or discard them. Closing or reloading the tab also warns about unsaved edits. Signing out or losing workspace access clears unsaved edits; saved notes remain with their session. If your sign-in changes or expires, the pads clear when the change is detected and ask you to Reload before editing again. When multiple agents, tabs, or devices edit a session’s pad, the latest successful save wins. Reopen the session or return to the browser tab to load newer saved notes when you have no unsaved edits. The pad supports plain text and line breaks, up to 20,000 characters. It has no interactive checkboxes or formatting. Clear the text to empty it for everyone with access to that session. Hiding the card or choosing Reset to default preserves saved notes; reset turns the card off until an admin enables it again. Redacting a session also clears its saved Session notes, including when it has notes but no messages.

Composer toolbar

Open Settings → Personalization and enable Pin composer toolbar under Inbox to keep formatting and AI Copilot controls above the session composer. In email sessions, the toolbar sits above Cc. It also applies when writing internal comments. This setting is off by default: the toolbar appears when you select text. Your choice is saved for your account across browsers and does not affect teammates. It applies to session replies and comments, not the New Session dialog. Available formatting and delivery behavior remain the same for each channel. Enable Macros button under Inbox to add a macros button to the session composer toolbar. It opens a searchable list of your macros with a preview of the highlighted one; choosing a macro inserts it where your cursor is. While the button is on, macros no longer appear in the / menu. This setting is off by default: macros are inserted from the / menu. Your choice is saved for your account across browsers and does not affect teammates. It applies to session replies and comments, and to the first message in the New Session dialog. There, the picker fills in contact variables but shows no suggested macros and no macro language, since no session exists yet.

Export macros

Open Reports & Apps → Data Export → Macros → Export CSV, then choose Download CSV. You need access to Reports and permission to view Macros or workspace settings. The file contains the shared macros and personal macros visible to you. Where you have a personal version of a shared macro, only your personal version is exported. Other users’ personal macros are excluded. Session filters do not affect this export. Each row includes the macro’s title, category, original HTML content, visibility, owner ID, shared-original ID (for personal versions), suggestion setting, and creation and update dates. Custom variables, options, and attachment metadata are included as JSON lists in the same row, so no separate variables file is needed. The custom_variables column includes the names and stored values of referenced custom variables, including variables referenced by other variables. Missing custom variables have a null value. System placeholders such as {{contact.full_name}} remain in the template; they are not filled with customer data. Unused custom variables are not exported. Attachments are exported as links and metadata, not bundled files. The CSV downloads immediately and does not add an entry to session export history.

Suggested macros

Enable Suggested macros under Settings → Personalization → Inbox to see the macros that best fit the customer’s latest message at the top of your macro list, in the / menu and in the macro picker. Up to three appear, best first, with a sparkle and a Strong or Possible mark. When none fits, your macros stay in their usual order. This setting is off by default and saved for your account. Suggestions work on every channel, appear when replying but not when writing internal comments, and never read internal comments. Your personal macros are suggested only to you. Workspace admins can turn suggestions off for everyone under Settings → Workspace → Replies → Suggested macros. Changing this setting requires Helpdesk settings write permission. It starts on; each agent still opts in. To keep a macro out of suggestions, turn off Suggest this macro when you create or edit it in Settings → Macros. The workspace section and the Macros page show how often suggestions were shown and used in the last 30 days. Suggestions learn from how agents use them. Open a saved macro in Settings → Macros and look at Insights at the bottom of its dialog. It shows where the macro stands, a 12-week sparkline, its hit rate (the share of times it was used when it was suggested) and how many recent adjustments there are. Select the expand icon for the details: Hit rate, how often it was Suggested and Used in the last 30 days, the hit rate week by week, and Recent adjustments, the sessions from the last 30 days where the AI suggested one macro and the agent sent another, with this macro on either side. Each links to its session and has a one-sentence What I learned note. The mark tells you where the macro stands:
  • Learning — not enough use yet to tell.
  • Steady — suggested at the usual bar.
  • Proven — agents use it when it’s suggested, so it is suggested a little earlier.
  • Muted — it is often suggested and never used, so it needs a closer match to the customer’s message before it appears again.
Insights is hidden for a macro with Suggest this macro off, or when suggestions are off for the workspace. Integrations can read the same numbers, without the adjustments: see List macro suggestion insights.

Translate messages in your view

Open the session’s More options → Translation → Target language menu to choose which language you read. Under Display style, choose Show translation beneath original content or Only show translation. These settings affect your dashboard view; they do not rewrite stored messages or change outbound translation settings. Translation in your view needs Google Chrome. Agent & AI replies, AI suggestions under Translated content covers agent replies, AI replies, and the AI suggestions you review before sending. A session without a detected language is translated message by message; a message whose language can’t be recognized confidently stays in its original language. While a session is translated, the session header shows a translation switch with the language pair, such as NL → EN. Turn it off to read that session’s original text; turn it on to translate it again. This affects only the open session and resets when you reload. With translation off, the switch appears when a session is in a language your browser isn’t set to, and turning it on sets your target language to your browser’s language. A session’s detected language shows as a flag on its session card and in the session header, so you can tell which language the customer wrote in while reading a translation. Hover the flag for the language name; a session without a detected language shows no flag. Translated message bodies preserve paragraphs, line breaks, emphasis, links, lists, and nested quotations. In email sessions, quoted history stays behind ••• in both the message view and the email experience. Expand it to read the history; its original text remains visible while its translation loads. A failed history translation leaves the translated message body visible and labels the history as original. If only the history is translated, only that section is labeled as a translation. If translation is unavailable, the original content remains readable. In the email experience, Only show translation displays one translated email once it is ready, retaining its inline images, layout, and quoted-history control. Show translation beneath original content displays both versions. Attachments remain available below the email; inline images are not repeated as attachments. The original stays visible while translation is loading or unavailable. Text inside image files is not translated.

AI suggestions when customer messages are translated

When your workspace translates customer messages, an AI suggestion is shown in the language you read, and Show original message in the message menu shows the version written for the customer. Copy to composer copies the version you read. Send it unchanged and the customer receives the suggestion exactly as written for them; no second translation runs. Edit it first and your edited reply is translated like any other reply. The AI agent’s replies, and workflow and sequence messages, are shown in your language the same way, following your Display style, and Show original message in the message menu shows what the customer receives. See what agents see for AI replies.

Macro groups and team-only macros

To create and edit macros, see Macros. Sort macros into groups so agents find them faster. When you create or edit a macro in Settings → Macros, search the Group list and pick one, or type a new name and select Create, such as Backoffice / Disputes. General means no group. To start a group, select New group, name it and pick the macros that go in it. Once a workspace has two or more groups, Settings → Macros shows each group as a section you open and close, with its macro count and a tag for each team its macros are limited to; the first group starts open, and a search opens every group with a match. Select + on a group to create a macro in it. The macro picker in the composer lists the macros under their group, with suggested macros on top. Searching for a group’s name in the picker or the / menu finds its macros. To keep an org-wide macro to the agents who need it, choose Teams in the same dialog. Only agents in those teams see it in the inbox: the macro picker, the / menu and suggested macros. Leave Teams empty for every agent. People who can edit macros in Settings → Macros always see every macro, so they can manage them. Personal macros can’t be limited to teams.

Macro version history

In Settings → Macros, the Created by column identifies the person who created each macro. Integration identifies creation through an integration without a user identity; a dash means the creator was not recorded. The column is hidden when none of the macros shown has a recorded creator. Select the Version history icon beside a macro to open its history in a side drawer. Choose a version to see its editor, timestamp, contents, and changes from the previous version. History shows only changed fields, with removed words marked in red and added words in green. Formatting edits highlight the affected text while preserving its styling. Attachment additions and removals include file names, sizes, and types. Use the version picker to move between revisions. History includes changes made through the dashboard, API, and Companion. Unchanged saves do not create another version. Shared macro history requires permission to edit macros. Personal macro history is visible only to its owner. History is read-only; previous versions cannot be restored. Older macros start with a Baseline, the earliest available state. Earlier edits and original creators cannot be reconstructed. Attachment history keeps names and metadata only; files cannot be opened from history, and inline images appear as references. Variables remain literal references, and personal macros do not capture changes to inherited options. Deleting a macro also deletes its version history.

Macro options

A macro can carry up to 3 buttons the customer taps instead of typing, such as Yes and No on a consent question. When you create or edit an org-wide macro in Settings → Macros, select Add option and type a Button label of up to 20 characters. Press Enter to add the next one, or Backspace in an empty label to remove it. You can also set options through the API (options on POST /macros and PATCH /macros/{id}) or the Companion. Personal macros can’t have options; a personal version of an org-wide macro sends the org-wide macro’s options. A tap reaches the session as the customer’s message and is handled like anything they type. Through the API or the Companion, an option can instead have the type workflow: the tap runs your Macro Option Clicked workflows for that macro and the AI doesn’t reply. Branch on Option ID or Option Label in the workflow. This works whoever owns the session. If no active workflow listens for the macro, the tap is handled like a message the customer typed. In the macro dialog these options show a lightning mark (Triggers a workflow) and keep working when you edit their label. Workflows can send an org-wide macro too, with the Send macro action. It sends the macro’s text, attachments and options, in the session’s language when the macro has a translation into it. A workflow can’t send a macro that uses variables, or a macro with attachments to a WhatsApp, Messenger or SMS session. When a First Contact Message Received or Contact Message Received workflow that runs synchronously answers a message with a macro whose options trigger a workflow, the AI doesn’t reply to that message and waits for the tap; the tap then runs your Macro Option Clicked workflows. While the question waits, the web chat hides the text box, so the customer answers by tapping. Turn on Run synchronously on the Macro Option Clicked workflow so its reply appears as soon as the customer taps. Use this for scripted questions, such as confirming a security report before it goes to your team. Only the first tap on the newest message with options counts. A second tap, a tap on an older message’s options, or a tap on a closed session arrives as a normal message and runs nothing. The message in the session timeline shows the options that were sent and marks the one the customer picked. The / menu, the macro picker and the composer show a macro’s options before you send it; remove them from the composer to send the message without options. Options are sent as buttons on the web widget, WhatsApp, Messenger and Instagram, and delivered to your own client on API sessions (see Send a message). A website running an older widget version shows the message without the buttons; the customer can still type their answer. On other channels, including sessions linked to HubSpot or Intercom conversations, only the message is sent, and the inbox tells you so when you insert the macro. The first message of a new session is always sent without options. On WhatsApp, a message with options is limited to 1,024 characters.

Macro workflows

Run a workflow every time an agent sends a macro, as a reply or as an internal note. First create a workflow with the Macro Called trigger. Then open an org-wide macro in Settings → Macros, select Add workflow under Workflows and pick it from the searchable list; each one shows Active or Draft. A workflow listens to one macro at a time: one already linked elsewhere shows Used by and that macro’s name, and can’t be picked. Changes apply when you save the macro. Removing a workflow from a macro turns the workflow off; it keeps its steps and can be linked again. Linking needs Workflows write permission as well as Macros settings write. Without it, the dialog lists the linked workflows read-only. Personal macros can’t trigger workflows. To have a macro set the session subject, as helpdesk macros often do, add a Set session subject step to its workflow. Build the subject from variables, for example {{trigger.macro.name}} for {{trigger.ticket.contact.name}}. The subject changes when the agent sends the macro and the change shows on the session timeline. See Set the session subject.

Translated macros

Write each macro in any language; its language is detected automatically. Choose the languages your customers speak and OpenCX translates every macro for you, so agents insert the right version without translating by hand. Choose the languages. Open Settings → Macros. The Translate macros section at the top shows your languages as chips. Select Add language, search, and pick up to 10; remove one with the × on its chip. No languages are chosen by default: until you add one, nothing is translated and macros are sent as written. Changing the languages requires Macros settings write permission; everyone else sees the section read-only.
  • Existing and new macros are translated once into each language you choose, in the background. A line under the chips shows how many macros are still being translated.
  • Editing a macro’s title, text, or options refreshes its translations.
  • Use your own wording. In a saved macro’s dialog, pick a language beside Content and select Edit to replace that translation with your own. It is used until the macro’s title, text, options or a custom variable it uses changes, and then translated again. Retranslate brings back a generated translation. An Overridden tag beside the language shows who wrote the wording you are looking at, and each change is recorded in the audit log.
  • Adding a language translates all your macros into it, so add only the languages you need. Removing a language stops using it, but its translations are kept, so adding it back is instant.
  • Variables such as {{contact.full_name}} are never translated; they are filled in as usual. Your custom variables are translated with the macro, and editing one refreshes the macros that use it.
In the inbox. When you insert a macro from the / menu or the macro picker (the Macros button), you get the version in the customer’s language, which is the session’s language, and a flag marks the macros that were translated. The macro picker also says which language a macro is sent in under its title. The macro is inserted as written when it is already in the customer’s language, when that language is not one you chose, or while its translation is still in progress. Translated macros apply when you reply to the customer, not when you write an internal comment. Read macros in your language. When the inbox translates a session for you (its language is not your target language or one you ignore, and you haven’t switched it back to the original), the / menu and the macro picker show each macro in your target language: its translation when you chose that language, or the macro as written. The macro picker translates the preview in your browser when there is no such translation, the same way it translates the session’s messages. What you insert does not change: it is still the customer’s language, or the macro as written in an internal comment. The macro picker says both under the title, for example “Shown in English · sent in German”. Search finds a macro by the title you see or the title as written. Tappable options (Macro options) are sent in the same language as the text you inserted, so the buttons match the message. Check a translation. Open a saved macro in Settings → Macros. A language button beside Content shows Original. Select it and pick a language from the searchable list to preview that translation; languages still translating or that failed are marked there. A failed one says Couldn’t translate to that language, with Try again. Select Retranslate (the refresh icon) on the preview to translate the macro again into every language. A macro with no translations yet shows Translate now instead. Translations are generated copies: to change the wording everywhere, edit the macro itself, or use Edit to replace one language with your own wording. Integrations can manage the languages and read or redo translations through the Macros API and the MCP tools.

FAQ

Periodic refreshes of the session list and selected session details pause while the browser tab is hidden. They refresh when you return to the tab. Live session updates can still arrive while the tab is in the background.
Check the assignee in the session header and your current Inbox filters. When Team in the loop applies, replying keeps the session assigned to AI. If you took over, find it among sessions assigned to you. For other sessions, the existing assignment behavior still applies.
If you reply to a phone session using text, OpenCX sends this text message to the customer’s phone number.

Export a session as PDF

Open a session in the Inbox, select the three-dot Session options menu, then choose Export as PDF. Anyone who can read that session can export it. The PDF downloads when it is ready; no additional settings are required. The filename includes the session ID; the PDF itself does not show the session ID or title. The PDF includes the customer name, email and phone number when available, channel, export date, and all customer-facing messages in chronological order. Each message includes its sender and timestamp with a timezone. Agent names follow the workspace’s first-name setting, with aliases preserved. Text is selectable and pages are numbered. The header uses your organization profile image from Settings → General, including the image derived from its website. Customer messages appear on the left; replies appear on the right, with purple AI, blue human-agent, and green workflow and sequence bubbles matching the Inbox. Internal comments, workflow comments, unsent drafts, AI suggestions, deleted messages, and system activity are excluded. Customer-facing workflow and sequence messages are included. The export always covers only the selected session, even when the WhatsApp view shows messages from other sessions for the same contact. Inbox visibility and translation settings do not change the exported messages. Attachments are listed by filename. Accessible PNG and JPEG attachments up to 10 MB also appear as previews. Other files, unavailable images, and call recordings are not embedded. If the session has no exportable messages, a notification appears instead of an empty PDF. If an export fails, reopen the menu and try again.

Available APIs

OpenCX provides APIs for developers to build on the platform, including inbox APIs.

Inbox

List and manage sessions from web, phone, and email channels in a single place.

Connected contact history

The session sidebar’s Contact Session History shows permitted sessions across the contact’s connected accounts, including snoozed sessions. Use This contact to narrow the list or All connected contacts to expand it; the latter is selected whenever you open another contact. Load more fetches further sessions, ordered by latest message. Each card identifies the session’s actual contact. This history selection does not change the main inbox’s contact filters or snooze filtering.

Agent first names

In Settings → Workspace → Agents → Agent names, enable Show agents’ first names only to use human agents’ first names in customer-facing names supplied by OpenCX, generated email signatures, saved-reply agent-name variables, copied session transcripts, and PDF exports. The setting is off by default and requires Helpdesk settings write permission. For example, Sarah Novak appears as Sarah. OpenCX uses the first word of the agent’s workspace profile name, or their account name when no workspace name is set. Existing customer-facing aliases stay unchanged, including aliases with multiple words. Use an alias to preserve a compound given name such as Mary Jane. If Workspace settings cannot be loaded, saved replies use only the agent’s first name until settings are available again. Known aliases still take precedence. Full names remain available internally for assignment, team lists, and audit history. Existing session history shown in the widget and newly generated exports follow the current setting. Refresh already-open dashboard tabs after changing it so saved-reply variables use the new setting. This setting does not rewrite message text or attachments, redact manually typed names or existing signatures, change agent email addresses, or recall emails and PDFs already delivered. Names supplied independently by an external system follow that system’s settings.