Genesys Cloud - Main

 View Only

Sign Up

  • 1.  Genesys Open Messaging with CX Cloud BYOC CCaaS

    Posted 08-14-2026 13:42
    Hi everyone,
    We are evaluating a scenario where an internal application starts the customer journey. When the customer needs to talk to a human agent, the application initiates a Genesys Open Messaging session.
     
    From that point on, Genesys Cloud remains responsible for the interaction, including Architect flow, ACD routing, queues, skills, and agent assignment.
    Today, with CX Cloud for Salesforce, the Genesys interaction is displayed inside Salesforce, but it does not to create an active Salesforce Messaging Session.
     
    The goal is to enable Salesforce Agentforce Service Assistant / Einstein Copilot to assist the agent during the live digital conversation.
     
    While reviewing the available options, we found CX Cloud BYOC CCaaS for Salesforce Service Cloud. Our understanding is that this could allow Genesys Cloud messaging to be represented in Salesforce Service Cloud / Enhanced Chat, while still keeping Genesys responsible for routing and orchestration.
     
    Has anyone implemented or evaluated a similar scenario?
    Any experience, recommendation, or architecture guidance would be appreciated.
     
    Thanks!

    #API/Integrations
    #DigitalChannels
    #Implementation
    #Omni-ChannelDesktop/UserInterface
    #Other

    ------------------------------
    Att,
    Breno Canyggia Ferreira Marreco
    ------------------------------


  • 2.  RE: Genesys Open Messaging with CX Cloud BYOC CCaaS

    Posted 08-16-2026 08:56

    Hi Breno,

    We evaluated a similar use case in which a proprietary application initiates the customer journey and hands the interaction over to Genesys Cloud through Open Messaging when human assistance is required.

    Based on our understanding, standard CX Cloud for Salesforce embeds the Genesys interaction inside Salesforce and provides agent desktop integration, but it does not automatically create a native Salesforce Messaging Session that can be consumed by Agentforce Service Assistant or Einstein Copilot in the same way as Salesforce Digital Engagement channels.

    Regarding CX Cloud BYOC CCaaS, the architecture appears to be more aligned with your objective because Salesforce becomes the conversation workspace while Genesys remains responsible for routing, queueing, skills-based assignment, presence, and overall contact center orchestration. In theory, this should make the interaction available through Salesforce's native messaging framework and therefore easier to leverage with Agentforce capabilities.

    However, one area I would recommend validating carefully is whether the specific Open Messaging conversation can be represented as a Salesforce Messaging Session/Enhanced Chat session end-to-end, and whether all message events, participant states, transfers, and conversation attributes are synchronized in a way that Agentforce can consume them in real time.

    From an architecture perspective, the key questions I would investigate are:

    • Does BYOC CCaaS support Open Messaging as the source channel, or only specific digital channels?
    • How are conversation transcripts and customer context mapped into Salesforce messaging objects?
    • Can Agentforce access the live conversation stream natively, or would additional event synchronization be required?
    • What happens during transfers, consults, and agent reassignments performed by Genesys Cloud?
    • Which platform remains the system of record for conversation history and analytics?

    If your primary goal is Agentforce assistance during an active digital interaction while keeping Genesys as the routing engine, CX Cloud BYOC CCaaS is probably the closest architecture fit. The main validation point is the level of native interoperability between Genesys Open Messaging conversations and Salesforce Messaging Session objects.

    I'd be interested to hear from anyone who has implemented this in production, especially with Agentforce or Einstein Copilot enabled.

    Regards,



    ------------------------------
    Cesar Padilla
    INDRA COLOMBIA
    ------------------------------



  • 3.  RE: Genesys Open Messaging with CX Cloud BYOC CCaaS

    Posted 08-16-2026 22:08

    Hi Breno,

    I reviewed the current Genesys CX Cloud and BYOC CCaaS documentation, and there is an important distinction between the two integration models that directly applies to your scenario.

    With CX Cloud Digital and AI, Open Messaging is explicitly listed as a supported Genesys Cloud digital channel. However, Genesys also explicitly states that this package does not require the native Salesforce Messaging object.

    That explains the behavior you are seeing today: the Genesys Open Messaging interaction can be handled inside Salesforce through CX Cloud, while no native Salesforce MessagingSession is created.

    BYOC CCaaS is architecturally different.

    Genesys describes BYOC CCaaS as the option for digital engagement using the native Salesforce Messaging object. During the documented setup, you:

    1. Create a Salesforce Messaging Channel using Genesys Cloud Channel as the Bring Your Own Channel.

    2. Register that Salesforce channel in the Genesys CCaaS Configuration.

    3. Create a Lightning Record Page based on the MessagingSession object.

    4. Add the Salesforce Enhanced Conversation component.

    5. Add Genesys Cloud Message Controls.

    6. Optionally add Salesforce AI components such as Einstein Replies and Einstein Field Recommendations.

    So, if the requirement is specifically:

    Genesys remains responsible for Architect, ACD routing, queues, skills and agent assignment, while Salesforce owns the native MessagingSession/Enhanced Conversation workspace so Salesforce AI can operate on the live interaction,

    then BYOC CCaaS is the CX Cloud architecture designed for that model.

    There is one important caveat for your specific design, though.

    I would not assume that an existing Genesys Open Messaging conversation can automatically be converted into a BYOC CCaaS Salesforce Messaging Session.

    The current Genesys documentation explicitly lists Open Messaging under the Digital and AI model, while the BYOC CCaaS documentation describes its own Salesforce Messaging Channel registration and requires a functional Genesys messaging deployment and flow. I have not found documentation stating that an arbitrary Open Messaging integration can be used as the ingress channel and then be transparently represented as a BYOC CCaaS MessagingSession.

    That is the critical distinction I would use when designing this solution:

    Current architecture

    Internal App → Genesys Open Messaging → Architect/ACD → CX Cloud Digital & AI → Salesforce

    This keeps the digital conversation as a Genesys interaction. Salesforce provides the agent workspace, but the conversation does not become a native Salesforce MessagingSession.

    BYOC CCaaS architecture

    Supported Genesys Messaging journey → Architect/ACD → CX Cloud BYOC CCaaS → Salesforce MessagingSession / Enhanced Conversation

    Genesys continues to provide CCaaS orchestration and routing, but Salesforce has the native messaging representation required by its messaging and AI capabilities.

    Therefore, I think BYOC CCaaS is the correct direction for the business requirement, but I would treat Open Messaging compatibility as the gating requirement, not assume that BYOC automatically solves it.

    If Open Messaging must remain the entry point from the proprietary application, I would validate that specific channel combination with Genesys before committing to the architecture. I would not build a custom process that creates or synchronizes Salesforce MessagingSession records independently, because that would bypass the lifecycle/event synchronization that the Genesys BYOC CCaaS package is designed to manage.

    So my recommendation would be: choose BYOC CCaaS if native Salesforce MessagingSession and Salesforce AI are mandatory, but first validate whether the proprietary application's Open Messaging ingress can participate in the supported BYOC CCaaS channel lifecycle.



    ------------------------------
    Gabriel Garcia
    NA
    ------------------------------



Related Content