Genesys Cloud - Main

 View Only

Sign Up

Expand all | Collapse all

How do you split responsibilities between your CRM and Genesys Cloud?

  • 1.  How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 16 days ago
    Hello Genesys folks! 👋
     
    Got another architecture question for everyone. 😄
     
    Curious how others have designed their CRM integration with Genesys Cloud.
     
    Which system owns:
     
    Customer identification
    Queue and skill selection
    Priority
    Agent selection
    Interaction state
    Reporting
     
    And how do you maintain context between the two systems? Is the Conversation ID your main correlation key, or do you maintain a CRM-side interaction/case ID alongside it?
     
    Would be great to understand where everyone draws the boundary between CRM logic and Genesys routing logic.

    #API/Integrations
    #ArchitectandDesign
    #Implementation
    #Telephony

    ------------------------------
    Akhil
    ------------------------------


  • 2.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 16 days ago

    Hi Akhil,

    For our Service Desk, Genesys owns queue/skill routing, priority, agent selection and interaction state. BMC Helix owns support tickets and their lifecycle.

    We capture the customer's ID in the IVR where available, with validation also available in the agent script. A Genesys Function retrieves recent open tickets from Helix, which we display as a Markdown table in the script. Agents can also find and create tickets directly from the same script using Data Actions and Functions.

    We use dynamic text colours-green for successful validation or ticket actions, and orange for unsuccessful lookups-to make the results clear.

    Reporting follows those boundaries: Genesys for contact centre performance and Helix for ticket outcomes. Currently, we retain the incident number in the script. Our next step is to store it as a custom conversation attribute, linking the Helix incident number to the Genesys Conversation ID so the ticket reference remains associated with the interaction.

    Our approach is to keep routing decisions in Genesys and ticket business logic in Helix, while bringing the context agents need into their workflow.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 3.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 16 days ago

    Thanks Phaneendra, really interesting setup! I like the clean split between Genesys handling the interaction/routing and Helix owning the ticket lifecycle.

    A couple of things I'm curious about: when your Function retrieves the recent open tickets from Helix, are you using the Customer ID captured in the IVR as the lookup key, and what happens when that isn't available?

    Also, when you start storing the Helix incident number against the Genesys Conversation ID, how are you thinking of handling cases where multiple incidents are viewed or created during the same conversation? One primary incident, or multiple references?



    ------------------------------
    Akhil
    ------------------------------



  • 4.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 16 days ago
    Edited by Phaneendra Avatapalli 16 days ago

    Thanks, Akhil!

    Yes, we use the customer’s ID captured in the IVR as the lookup key. When it isn’t available, the agent can enter and validate the ID in the script, then retrieve their recent open tickets. Agents can also find a ticket using an INC/REQ number or the last four digits.

    For the conversation link, we’re planning to store the incident number only when a ticket is created from the script. Viewing or finding existing tickets won’t link them to the interaction.

    I’ve also added a guardrail: once a ticket is successfully created, the Create Ticket button disappears to prevent duplicate creation. So our current approach is one created incident reference per conversation.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 5.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 16 days ago
    Thanks Phaneendra. When the same customer calls again, does the Customer ID captured in the IVR automatically retrieve their existing open Helix incidents for the agent? And how do you distinguish between a repeat contact for an existing issue and a genuinely new issue that needs a new ticket?


    ------------------------------
    Akhil
    ------------------------------



  • 6.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 16 days ago

    Yes, the customer's ID retrieves their recent open Helix incidents, displayed as a table in the script with the ticket number, description, submit date, assigned team and status. Agents can open the ticket directly from there, so they already have some context.

    The agent then confirms the reason for contact with the customer and decides whether it relates to an existing incident or needs a new ticket. We don't automatically classify it as a repeat or new issue; the lookup helps agents make that decision and avoid duplicates.



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 7.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 15 days ago
    Thanks Phaneendra, really appreciate you taking the time to explain the whole flow in detail. This was really helpful and gave me a much better understanding of how you've designed the integration. Thanks again for sharing!


    ------------------------------
    Akhil
    ------------------------------



  • 8.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 15 days ago

    You're very welcome, Akhil! Glad you found it helpful. Always happy to share what we've been working on, and it's great to learn how others are approaching similar integrations too! 😊



    ------------------------------
    Phaneendra
    Technical Solutions Consultant
    ------------------------------



  • 9.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 16 days ago

    Great topic 🙌 the rule of thumb I use with clients is pretty simple… Genesys owns the "who, when and how" of the interaction (routing, priority, agent selection, state), and the CRM owns the "what and why" (who the customer is, their open cases, the business outcome).

    Priority is the one that usually gets blurry. what works best for us is the CRM providing the signal (VIP, open complaint, at-risk customer) and Genesys making the routing decision with it, so the logic doesn't end up split across both systems.

    For context, I'd always keep both IDs… the conversation ID written on the CRM activity, and the case ID stored on the conversation. that way you can join both sides in your data warehouse without depending on one system.

    And on Akhil's question about repeat vs new issues, that's where I'd bring the case ID into reporting. same customer, same case, contact again within a few days = repeat contact. it gives you a much more honest FCR than asking the agent to decide.



    ------------------------------
    Ignacio
    Senior CX Advisory Consultant
    ------------------------------



  • 10.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 15 days ago

    Thanks @Ignacio Peredo, this is a really helpful way of looking at the boundary between the two systems

    I particularly like the idea of the CRM providing the business signal while Genesys owns the routing decision. Curious about the fallback though. If Genesys can't retrieve that CRM context for some reason, for example an API timeout, do you just continue with standard routing or have you designed a separate fallback path?


    ------------------------------
    Akhil
    ------------------------------



  • 11.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 15 days ago

    Hi! 👋

    From my perspective, I normally recommend keeping a clear separation between CRM business logic and Genesys Cloud interaction/routing logic.

    A typical approach would be:

    • Customer identification: CRM is normally the source of truth. Genesys Cloud can identify the customer using ANI, email, WhatsApp number, or data collected during the interaction, and then query the CRM through APIs/Data Actions.

    • Queue and skill selection: Genesys Cloud. Architect flows can use customer information from the CRM to dynamically select the correct queue and skills.

    • Priority: Genesys Cloud, based on business rules. For example, the CRM can provide information such as VIP level, product, segment, or case type, and Genesys Cloud uses that information for routing decisions.

    • Agent selection: Genesys Cloud. I prefer to keep ACD, skills, availability, utilization, and routing logic inside Genesys Cloud.

    • Interaction state: Genesys Cloud should own the communication/interaction state, while the CRM owns the business process or case state.

    • Reporting: Genesys Cloud for interaction and operational metrics; CRM for customer/business outcomes. For consolidated reporting, both datasets can be correlated externally.

    For context, I normally use the Genesys Cloud Conversation ID as the main interaction correlation key, but I also recommend keeping the CRM Case/Interaction ID as an external reference.

    Ideally, we store both IDs:

    Genesys Conversation ID -> CRM Case/Interaction ID

    This makes troubleshooting, reporting, APIs, screen pop, and interaction history much easier.

    So, in simple terms, my architecture boundary would be:

    CRM = Who is the customer and what is happening with the customer.
    Genesys Cloud = How, where, and to whom the interaction should be routed and managed.

    The CRM provides the business context, and Genesys Cloud uses that context to orchestrate the customer experience. 🙂



    ------------------------------
    Carlos
    Solution Consultant
    ------------------------------



  • 12.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 15 days ago
    Thanks Carlos, really like this approach. The separation between CRM business context and Genesys routing logic is very clear, and keeping both IDs for correlation makes a lot of sense as well. Appreciate you sharing the detail!


    ------------------------------
    Akhil
    ------------------------------



  • 13.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 13 days ago

    Hi @Carlos Gutierrez,

    Thanks for your insightful post.

    So your cases are handled in the CRM platform which makes sense and Genesys is routing interactions. Which system routes emails?

    Best,



    ------------------------------
    Levy
    Communications Manager
    ------------------------------



  • 14.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 13 days ago
    Hi Levy,
     
    Good question. The environments I have worked with email is handled as Email-to-Case in Salesforce, so Salesforce owns the email/case and its business context. For routing, eligible work is passed through External Routing to Genesys Cloud, where Genesys uses things like queue, skills, priority, agent capacity and availability to select the appropriate agent. The routed work is then presented back in the Salesforce agent desktop.
     
    So the split is roughly:
     
    Salesforce = Email/Case and business context
    Genesys Cloud = Routing decision and agent selection
     
    That keeps the same boundary we were discussing earlier, just applied to email.


    ------------------------------
    Akhil
    ------------------------------



  • 15.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 13 days ago
    Thanks Akhill,

    Makes sense.

    Levy








  • 16.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 8 days ago

    Hi Levy :)

    In this architecture, Genesys Cloud handles the email routing as well. Emails are treated as another interaction channel, so Genesys can use queues, skills, priority, and routing rules to select the right agent.

    The CRM remains the system of record for the customer and case, while Genesys manages the interaction and routing logic across voice, email, chat, and messaging.

    We normally keep both IDs for correlation: the Genesys Conversation ID and the CRM Case/Interaction ID.



    ------------------------------
    Carlos
    Solution Consultant
    ------------------------------



  • 17.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 7 days ago

    Thanks @Carlos Gutierrez and @Akhil Akhil,

    Do the agents have a separate window for Salesforce and Genesys UI or using something integrated like CX Cloud or the legacy Salesforce CTI?

    CTI will be EOL soon and CX Cloud requires expensive salesforce licenses.

    Best



    ------------------------------
    Levy
    Communications Manager
    ------------------------------



  • 18.  RE: How do you split responsibilities between your CRM and Genesys Cloud?

    Posted 7 days ago

    Hi @Levy Mertz,

    In the environment I've worked with, agents use an integrated Salesforce desktop rather than separate Salesforce and Genesys windows. Salesforce remains the system of record/customer workspace, while Genesys Cloud provides the routing and interaction capabilities behind it.
     
    For Salesforce-originated work, External Routing passes eligible work to Genesys for queue/skill/priority and agent selection, and it's then presented back within Salesforce.
     
    And yes, your point around licensing is an important consideration when choosing the integration model.


    ------------------------------
    Akhil
    ------------------------------