Contacts and companies
At handoff, OpenCX links the contact to a Genesys external contact by phone number, then email, or creates one. A contact with neither isn’t linked. Its company links to an external organization the same way. When an agent wraps up, a name edited in Genesys comes back, and an edited email or phone fills only an empty field. When Genesys has matched a call, an email, or an SMS or WhatsApp conversation to an external contact, the session joins the OpenCX contact already linked to that external contact, so one person keeps one contact across channels. Otherwise the contact found by phone number or email is linked to it, and the external contact’s name, email and phone fill in, with its address and custom fields as contact attributes of the same names (address, and each field’s own name). A contact that already has the older genesys_contact_<field> name keeps it. Web messaging never joins a contact this way, because a page can claim anyone’s identity, and neither does a session signed in with a contact token.
Custom fields keep their type: numbers stay numbers, checkboxes become true or false, dates and text stay text, and a list of tags becomes one comma-separated value. A field of a type OpenCX can’t hold is left out. Without externalContacts:customFields:view on the role, text, numbers and true/false come over as they are and lists stay out. Custom fields update when the contact links and when an agent wraps up.
Editing one of those attributes in OpenCX updates that custom field on the external contact, so Genesys and OpenCX keep the same value. If Genesys refuses the edit, for example because the contact is in a division the role can’t edit, the edit stays in OpenCX and isn’t retried. Whichever side changed a field last wins: a later change in Genesys replaces the value in OpenCX, and an OpenCX edit stays until Genesys changes that field.
The external contact’s organization becomes the contact’s company in OpenCX, and the contact is added to it. A company already linked to that organization is used, such as one OpenCX created at handoff, and keeps its name. Otherwise a company is created with the organization’s name. The organization’s custom fields become company attributes of the same names, with the same types. A company that already has the older genesys_organization_<field> name keeps it.
Only the attributes your AI Context Rules allow reach the AI.
Notes, both ways
Notes your Genesys agents keep on an external contact appear in OpenCX as internal notes on that contact’s newest Genesys session, under the agent’s name and dated, when the contact links and each time an agent wraps up. OpenCX contacts have no notes of their own, so the session is where they go. The 50 newest come over, each once, and they’re never shown to the customer or the AI. They’re redacted under your PII redaction settings, and a session whose history was erased gets none. In the other direction, an internal note a teammate writes on a session linked to Genesys is also added to the external contact’s notes, ending with a link back to the session, while Share OpenCX context with Genesys is on. Genesys signs every note with an agent, so the teammate must be linked to a Genesys user; otherwise the note stays in OpenCX only. Notes OpenCX writes, including CSAT scores, never come back as Genesys notes.AI attributes
Under AI attributes on the Handoff tab, list what the AI should look for in a session, and where it goes: participant data, a custom field on the external contact, or a suggested wrap-up code (opencx_suggested_wrapup). For a wrap-up suggestion the key only names the attribute in OpenCX: the suggestion always goes to opencx_suggested_wrapup. The AI fills them at handoff and when OpenCX ends the conversation, and never replaces an agent’s entry. A custom field is written only on an external contact whose schema has that field. External contacts OpenCX creates have no schema, so nothing is written to them for those fields. None are set up by default.
Participant data on contacts
Under Participant data on the Handoff tab, OpenCX lists the participant data keys it has seen on your sessions. Turn a key on to keep it on the contact too, under the same name, so the customer’s next session starts with it. The contact gets it the first time Genesys sends it for that customer, then updates when the value changes in Genesys, so an edit your team makes on the contact stays until Genesys sends a new value. Every key stays on the session either way.Conversation custom attributes
With Genesys Cloud CX 2 or higher, flows and agents can set custom attributes on a conversation. Each becomes the session attribute of the same name, with numbers and true/false kept and lists comma-separated. A teammate’s change to it in the inbox, or a change to agenesys_custom_<name> attribute from anywhere, goes back to the custom attribute of that name, as its type. OpenCX only updates attributes the conversation already has, because a new set of custom attributes needs a schema that you choose in Genesys.
If Genesys refuses them because of the licence or the role’s permissions, Health shows a Custom attributes warning for a day, and the rest of the sync carries on. OpenCX tries again after that day.
Related
Sessions and sync
When participant data and attributes come in and go out.
What the Genesys agent sees
Notes and context in the agent desktop.