61 results found

1. Integrate Salesforce within the RC App

   The more our customers leverage RingCX, they need a way to avoid web page refreshes disconnecting calls. Salesforce (SFDC) encounters a lot of random refreshes that are impacting the SFDC Agent widget when on calls (since it's just the RCX native with a skin on it). If the agent can use the embedded RCX within the desktop version of RingEX, and they can access SFDC content in-app, that would be a solid workaround for the refresh issue.

   SFDC content to access in-app includes: customer profiles, records, accounts, opportunities, etc.

   20 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Planned  ·  1 comment  ·  Integrations & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Persistent Login for RingCX Salesforce Agent

   Feature Request: Persistent Login for RingCX Salesforce Agent
   Description:
   The RingCX Salesforce Agent logs users out whenever they switch tabs or applications within Salesforce, requiring repeated logins and disrupting workflow.

   Current Behavior:

   Users must log in again after navigating to a different tab or application.
   This causes delays and frustration.
   Proposed Enhancement:

   Maintain login sessions while users switch tabs or applications.
   Keep authentication valid for the duration of the Salesforce session unless manually logged out.
   Business Impact:

   Reduces login fatigue and improves efficiency.
   Minimizes workflow disruptions.

   17 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  3 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Salesforce embedded Agent to have "All messages" for agents to view old/closed messages

   Salesforce embedded Agent to have "All messages" for agents to view old/closed messages

   If its an old message , agents need to check photos or videos through text but it disconnects them from the Salesforce call since RingCX agent can only have one login session at a time

   10 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Needs More Information  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. display queue name when call comes in in embedded RingCX for Zoho

   It's important to see what call queue the call is comin in so that agents would know their opening spiel

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Implemented  ·  1 comment  ·  Integrations & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. RingCX for Salesforce integration to RingCentral Desktop App

   Customer wants to integrate RingCX for Salesforce to RingCentral desktop app so that when agent receives a call in RingCX, agent can retrieve Salesforce data or have popup in the RingCentral desktop app.

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  1 comment  ·  Integrations & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add “All Messages” View for RingCX for HubSpot Embedded Agent

   Add “All Messages” View for RingCX Embedded Agent in HubSpot

   Description:
   Currently, agents using the RingCX embedded Agent in HubSpot can only see active or open messages. There is no option for agents to view old or closed messages within the same interface similar to what is currently available in the native RingCX web version.

   Requested Feature:
   Add an “All Messages” view or filter in the RingCX embedded Agent for HubSpot so agents can easily access and review previous or closed interactions.

   Value/Benefit:

   1. Provides agents with full conversation history for better context.

   2. Improves customer experience by avoiding repeated questions.

   3. Increases agent productivity by eliminating the need to switch between systems to find past messages.

   Who needs this:
   All agents using RingCX embedded in HubSpot who handle customer messaging and need to reference conversation history.

   Add “All Messages” View for RingCX Embedded Agent in HubSpot

   Description:
   Currently, agents using the RingCX embedded Agent in HubSpot can only see active or open messages. There is no option for agents to view old or closed messages within the same interface similar to what is currently available in the native RingCX web version.

   Requested Feature:
   Add an “All Messages” view or filter in the RingCX embedded Agent for HubSpot so agents can easily access and review previous or closed interactions.

   Value/Benefit:

   1. Provides agents with full conversation history for better context.

   2. Improves customer experience by avoiding repeated questions.

   3. Increases… more

   8 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Future Consideration  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. To Have Start and End Time Attributes in RingCX for Salesforce

   We would like to request the addition of attributes in RingCX for Salesforce that capture both start and end times. This functionality would provide better tracking, reporting, and integration with workflows, ultimately improving visibility and efficiency for users.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Implemented  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Ability to search for contact name in Outbounds SMS (CRMs)

   Specific Request: Enable CRM Contact Search for Outbound SMS in RingCX for HubSpot Embedded Agent

   Summary:
   Allow RingCX agents to search and select contacts directly from the connected CRM (HubSpot) when sending outbound SMS messages via the Embedded Agent interface.

   Description:
   Currently, RingCX agents must manually copy and paste contact numbers from the CRM (HubSpot) into the SMS field on the agent user interface. This process is time-consuming and increases the risk of human error.

   By enabling CRM contact search functionality within the outbound SMS interface, agents will be able to:

   1. Search for and select contacts by name, email, or phone number.

   2. Automatically populate the phone number field based on the selected CRM contact.

   3. Streamline the workflow and improve agent productivity.

   4. Reduce manual data entry and potential mistakes.

   Proposed Functionality:

   1. Add a "Search Contact" field in the outbound SMS window.

   2. Integrate real-time search and filtering from the HubSpot CRM contact list.

   3. Auto-fill the phone number upon selecting a contact.

   4. Optionally display key contact details (e.g., name, phone number, company) to confirm identity.

   Benefits:

   1. Improved efficiency and accuracy for outbound SMS communications.

   2. Enhanced user experience for agents.

   3. Better alignment between RingCX and HubSpot CRM data.

   Use Case Example:
   An agent needs to send a quick follow-up SMS to a lead. Instead of switching tabs, finding the number in HubSpot, and copying it, they can simply search the contact within the SMS interface, select it, and send the message—seamlessly.

   Specific Request: Enable CRM Contact Search for Outbound SMS in RingCX for HubSpot Embedded Agent

   Summary:
   Allow RingCX agents to search and select contacts directly from the connected CRM (HubSpot) when sending outbound SMS messages via the Embedded Agent interface.

   Description:
   Currently, RingCX agents must manually copy and paste contact numbers from the CRM (HubSpot) into the SMS field on the agent user interface. This process is time-consuming and increases the risk of human error.

   By enabling CRM contact search functionality within the outbound SMS interface, agents will be able to:

   1. Search for and select contacts by name, email, or… more

   •  

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Implemented  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. RingCX HubSpot Extension Ability to send SMS

   While using the RingCX HubSpot extenstion you should be able to send SMS by hovering over the contact records phone number just like you can with the EX extension. You should also be able to send SMS through the workflows with the CX extension. It is inefficient to have agents go back and forth between EX and CX so they they can do SMS.

   7 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating
   Implemented  ·  AdminPaula (Group Product Manager, RingCentral) responded

   We're excited to announce that we've listened to your feedback have rolled out a new update for the RingCX for HubSpot extension!

   The Click to SMS feature is now available.

   https://support.ringcentral.com/article-v2/Navigating-RingCX-for-HubSpot-as-a-user.html?brand=RingCentral&product=RingCX&language=en_US

10. Option to see the number of calls are in queues and agents statistics

    currently an agent cannot be logged into bot the Ringcx web app and the RingCX Salesforce integration. This means agents that use salesforce with the ringcx integration cannot see how many calls are in the ques they log in to or their agent stats. Please make that information available to the ringcx salesforce integration

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Implemented  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. End Call Tone (RingCX/Salesforce)

    When a call ends within the Salesforce integration, it would be great to have some sort of tone play that notifies the user the call has ended. This is great for instances where the customer hangs up while we have them on hold, preparing the representative for the next call instead of being surprised when a new call comes in.

    7 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Future Consideration  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Access RingCX Voicemails in the RingCentral Chrome Extension

    Ability to route and access RingCX voicemails in the RingCentral Chrome Extension

    6 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Feature Request: RingCX | API for Microsoft Company Directory Integration

    Description

    • Requesting the ability to integrate their Microsoft Company Address Book (Azure AD / Microsoft 365 Directory) with RingCX.

    They would like RingCX to consume directory data via API so agents can access corporate contacts directly within the platform.

    Requested Capability

    • API-based integration between RingCX and Microsoft Company Directory

    • Sync or query users and contacts from Microsoft 365 / Azure AD

    • Make company directory contacts searchable and usable within RingCX (e.g., dialing, identification)

    Business Value / Use Case

    • Improves agent efficiency by eliminating the need to manually maintain contacts

    • Ensures a single source of truth for corporate directory data

    • Reduces operational overhead and data inconsistency

    • Enhances enterprise adoption for Microsoft-centric environments

    Current Limitation
    • RingCX does not currently provide a native API or connector to integrate with Microsoft Company Directory.

    Description

    • Requesting the ability to integrate their Microsoft Company Address Book (Azure AD / Microsoft 365 Directory) with RingCX.

    They would like RingCX to consume directory data via API so agents can access corporate contacts directly within the platform.

    Requested Capability

    • API-based integration between RingCX and Microsoft Company Directory

    • Sync or query users and contacts from Microsoft 365 / Azure AD

    • Make company directory contacts searchable and usable within RingCX (e.g., dialing, identification)

    Business Value / Use Case

    • Improves agent efficiency by eliminating the need to manually maintain contacts

    • Ensures a single source of… more

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Future Consideration  ·  1 comment  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Feature Request: Improve Call Logging Reliability in RingCX Embedded Agent for Dynamics 365

    Subject: Feature Request: Improve Call Logging Reliability in RingCX Embedded Agent for Dynamics 365

    Product Area: RingCX
    Component: Embedded Agent – Microsoft Dynamics 365 Integration
    Request Type: Feature Enhancement / Reliability Improvement
    Priority Impact: High (Data integrity, reporting accuracy, agent workflow)

    ---

    Problem Statement

    The RingCX Embedded Agent integration with Microsoft Dynamics 365 has several limitations that result in missing or incomplete phone call records when required fields (specifically the Name and Call To / Call From fields) are not populated at call end.

    These limitations cause gaps in call reporting, incomplete CRM activity history, and inconsistent agent workflows—particularly in healthcare and high-volume contact center environments where calls may end abruptly or contacts may not yet exist in Dynamics.

    ---

    Current Behavior

    1. Name field dependency

    • If the Name field is not populated at disposition time:

      • Phone call records may not be created in Dynamics 365
      • Placeholder customer/patient records may be auto-created with no populated data

    1. Common scenarios leading to missing Name field

    • Phone numbers associated with multiple Dynamics records (ambiguous match)
    • Inbound calls from contacts not yet in Dynamics
    • Outbound calls to external parties not stored in Dynamics (e.g., physicians, vendors)
    • Calls going directly to voicemail or ending abruptly
    • Immediate transition to the disposition screen, increasing missed data entry
    • Agents intentionally leaving calls untracked due to workflow constraints

    1. Dynamics constraints

    • The Call To / Call From field is required by Dynamics 365
    • RingCX currently cannot create call records without these required fields populated

    ---

    Business Impact

    • Inaccurate call volume and performance reporting
    • Missing CRM activity records for completed calls
    • Increased manual cleanup and reconciliation work
    • Reduced agent compliance and usability
    • Risk to auditability and operational visibility in regulated environments

    ---

    Requested Enhancements

    1. Decouple Call Record Creation from Name Field Completion

    Allow phone call activity records to be created in Dynamics 365 even if the Name field is empty, using a temporary or system-generated reference (e.g., “Unknown Caller”).

    This would:

    • Preserve call metadata (time, direction, duration, agent)
    • Allow post-call completion of required fields
    • Ensure accurate reporting and historical tracking

    ---

    2. Prevent Automatic Customer/Patient Record Creation

    Add an option to disable auto-creation of customer/contact records from RingCX calls.

    Desired behavior:

    • Call records can exist independently of customer/contact records
    • Customer/contact creation remains a manual, user-driven action

    ---

    3. Improve Name Field Visibility and Workflow

    Enhance agent UI to reduce missed Name entries by:

    • Making the Name field more prominent
    • Displaying the Name field on both call and disposition screens
    • Optionally merging Name entry and disposition into a single workflow step
    • Preventing disposition submission until required CRM fields are reviewed

    ---

    4. Support Deferred Field Completion

    Allow agents or supervisors to populate or correct:

    • Name
    • Call To / Call From after the call record has already been created in Dynamics.

    ---

    Expected Outcome

    • All RingCX calls generate a corresponding Dynamics phone call record
    • Improved data integrity and reporting accuracy
    • Reduced agent friction and training overhead
    • Better alignment with real-world call center workflows
    • Increased adoption of RingCX Embedded Agent in Dynamics-heavy environments

    ---

    Environment Details

    • Platform: RingCX
    • Integration: Embedded Agent for Microsoft Dynamics 365
    • Use Case: High-volume inbound and outbound contact center operations
    • Industry Impact: Healthcare, enterprise support, regulated environments

    ---

    Request

    Please review the feasibility of these enhancements and advise:

    • Whether these changes align with the RingCX product roadmap
    • If configuration-based alternatives are planned
    • Recommended next steps for prioritization

    Thank you for considering this request.

    Subject: Feature Request: Improve Call Logging Reliability in RingCX Embedded Agent for Dynamics 365

    Product Area: RingCX
    Component: Embedded Agent – Microsoft Dynamics 365 Integration
    Request Type: Feature Enhancement / Reliability Improvement
    Priority Impact: High (Data integrity, reporting accuracy, agent workflow)

    ---

    Problem Statement

    The RingCX Embedded Agent integration with Microsoft Dynamics 365 has several limitations that result in missing or incomplete phone call records when required fields (specifically the Name and Call To / Call From fields) are not populated at call end.

    These limitations cause gaps in call reporting, incomplete CRM activity history, and inconsistent agent workflows—particularly in healthcare… more

    5 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Hubspot embedded agent

    Instead of Hubspot being an extension, work with hubspot to embed the agent console into the CRM

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Future Consideration  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Ability to allow Litify objects to mapped on RCx SF embedded agent

    We need the ability to screenpop Intake or Matter and have the ability to create call logs unto those objects as well

    4 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Implemented  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Feature Request: Embedded Integration for RingCX + Zoho

    I’d like to submit a feature request regarding the current RingCX integration with Zoho.

    At present, the only available method for connecting RingCX to Zoho is through the Chrome extension. Several customers have expressed the need for a more seamless workflow by having this functionality embedded natively within RingCX instead of relying on the extension.

    Requested Enhancement:

    Add support for a native or embedded RingCX–Zoho integration, removing the dependency on the browser extension.

    Goal: Improve agent workflow efficiency, reduce extension-related issues, and provide a more streamlined user experience.

    This enhancement would greatly improve usability and stability for customers leveraging Zoho within their RingCX/CC environment.

    I’d like to submit a feature request regarding the current RingCX integration with Zoho.

    At present, the only available method for connecting RingCX to Zoho is through the Chrome extension. Several customers have expressed the need for a more seamless workflow by having this functionality embedded natively within RingCX instead of relying on the extension.

    Requested Enhancement:

    Add support for a native or embedded RingCX–Zoho integration, removing the dependency on the browser extension.

    Goal: Improve agent workflow efficiency, reduce extension-related issues, and provide a more streamlined user experience.

    This enhancement would greatly improve usability and stability for customers leveraging Zoho… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Under Review  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

18. Salesforce for RingCX - allow login sessions to be kept active even when browser refresh so agents do not log out.

    Allow login sessions to be kept active even when browser refresh so agents do not log out.

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    1 comment  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    Implemented  ·  AdminPaula (Group Product Manager, RingCentral) responded

    Release 25.4.2 (December)

    RingCX for Salesforce - Persistent Login Across Browser Refreshes:

    Agents using the integrated softphone will now remain logged into the adapter even after refreshing a browser page. This eliminates a major point of friction, prevents workflow interruptions, and provides a more stable and reliable user experience, especially for agents working in complex Salesforce environments.

19. Surface Pre-Chat Form Data to Agents and Use It for Dynamics 365 Record Pop

    Currently, when a chat is accepted in RingCX with Dynamics 365 integration, the information a visitor submits in the Pre-Chat form (e.g., name, email, phone, member ID) is not surfaced to the agent nor used to open the corresponding record in Dynamics.

    This creates an inconsistency across channels:

    Phone: Caller ID matches and pops a record in Dynamics.

    Email: Sender address matches and pops a record in Dynamics.

    Chat: Pre-Chat data is ignored, leaving agents without context.

    As a result, agents must re-ask for information the visitor already provided, handle time increases, and member experience suffers. Displaying Pre-Chat data to the agent and using it to pop the Dynamics record would bring chat in line with phone and email, improving accuracy, efficiency, and overall consistency.

    Currently, when a chat is accepted in RingCX with Dynamics 365 integration, the information a visitor submits in the Pre-Chat form (e.g., name, email, phone, member ID) is not surfaced to the agent nor used to open the corresponding record in Dynamics.

    This creates an inconsistency across channels:

    Phone: Caller ID matches and pops a record in Dynamics.

    Email: Sender address matches and pops a record in Dynamics.

    Chat: Pre-Chat data is ignored, leaving agents without context.

    As a result, agents must re-ask for information the visitor already provided, handle time increases, and member experience suffers. Displaying Pre-Chat data to… more

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Future Consideration  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. RingCX | Zendesk Integration Refresh feature

    The ability to keep the RingCX Embedded app logged in when refreshing just the Zendesk integration. Currently

    3 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    Future Consideration  ·  0 comments  ·  Integrations & APIs  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating