333 results found

1. RingCX Dialer ability to merge old leads to new leads

   in RingCX outbound dialer, it would be better to have the ability to merge/combine old lead that was dialed before to the same lead that is being uploaded like 6 weeks ago.

   By doing this, the history of the previous lead are visible to the agent that will take the new lead.

   1 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  ·  Other  ·  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. Stay on Available status when Rejecting Calls

   We would like to have an option to have agents stay on Available status when Rejecting Calls in RingCX

   2 votes

   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  ·  2 comments  ·  Other  ·  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. Transferring RingCX call via User Ext. Deskphone

   The ability to use the User Extensions Deskphone when transferring RingCX calls that were answered using RC Phone as the voice connection would provide customers with greater convenience. This feature would allow users to pick up RingCX calls on deskphones and transfer them without having to return to the RingCX Integrated dialer. Such functionality would streamline the call transfer process for customers using deskphones.

   5 votes

   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  ·  1 comment  ·  Other  ·  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. Allow for custom key-mapping/binding of call control to desktop keyboard

   Allow for the customization of keyboard shortcuts when dialing. This could be for all outbound dialing modes but emphasis for this request is specific to HCI "clicker" agents.

   2 votes

   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  ·  Other  ·  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. Ability to export IVR from Studio

   Need the ability to export IVR Studio so they can be shared and imported.

   41 votes

   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  ·  Other  ·  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. RingCX Analytics Report - Agent Name, Email Address, Status (Active or Inactive)

   Customer wants to have a report in RingCX Analytics that shows Agent Name, Email Address and Status (Active or Inactive) that will tally to the total number of agents in Admin>Users.

   9 votes

   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  ·  Other  ·  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. Feature Enhancement Request: Lead Uploading/Management Testing in RingCX

   Feature Enhancement Request: Lead Uploading/Management Testing in RingCX

   Description:
   RingCX currently lacks sufficient diagnostic tools for troubleshooting issues related to the uploading and management of leads, particularly when leads are moved between campaigns or lists. This results in significant issues like "lost" leads that cannot be located via admin interface or API, as well as leads being improperly marked with an "active" state when no agents are logged in. To resolve these issues effectively, we propose the implementation of an enhanced testing and diagnostic mechanism that will allow RingCentral Tech Support and administrators to directly monitor and test lead uploads and transfers in RingCX.

   Use Case:
   A customer recently encountered an issue where a lead list was being moved from one campaign to another via the admin panel, but many leads (over 5,000) were "lost" in the process. Despite the leads being present in the target list’s search result (via the campaign filter), they couldn’t be found when filtered by individual list IDs. Similarly, the leads were not retrievable using the RingCX Dialing API, even though they had the correct list ID. However, after manually re-moving the leads via the admin interface, they reappeared correctly.

   This highlights a gap in diagnostic capabilities when leads are lost or fail to upload/load correctly during batch processes. The customer was left without sufficient tools to verify whether leads were correctly moved or simply “lost” in the transfer process.

   Proposed Enhancement:

   Diagnostic Tools for Upload/Management Testing:

   Admin Panel Visibility:
   Introduce a diagnostic dashboard within the admin panel to monitor and verify the successful uploading and movement of leads, with real-time feedback for any errors encountered.
   Detailed Error Logging:
   Implement detailed error messages or logs for failed lead uploads or transfers, which would include information such as:
   The specific lead IDs that failed to upload.
   The error type encountered (e.g., network failure, internal server error, missing data).
   The list or campaign where the failure occurred.
   Error Resolution Suggestions:
   Provide actionable suggestions for resolving these issues, including retries, list verification, or system checks.
   Lead State Monitoring:

   Lead State Consistency Check:
   Provide real-time state verification for leads, ensuring that leads are not mistakenly marked as "ACTIVE" when no agents are available. Implement a mechanism to flag or auto-correct leads that remain in an incorrect state after hours or during non-peak periods.
   Lead Activity History:
   Introduce a feature to track the history of a lead’s activity, allowing administrators and support teams to see the transitions between states (e.g., from "ACTIVE" to "INACTIVE") and understand why the lead may still be stuck in an incorrect state.
   Automated Testing for Lead List Transfers:

   Pre-Transfer Validation:
   Introduce a validation step when moving large lead lists between campaigns. This validation would check for potential issues (e.g., lead state discrepancies, duplicates, or missing data) before proceeding with the transfer. If an issue is detected, the transfer would be paused, and the administrator would receive detailed feedback on what needs to be fixed.
   Post-Transfer Confirmation:
   After the list transfer completes, the system should automatically confirm that all leads have been successfully moved. If there is any discrepancy in the number of leads moved or missing, an alert should be triggered, and the leads should remain in the source list until the issue is resolved.
   API Enhancements:

   Lead Search and Fetch Enhancements:
   Improve the API’s lead search functionality to ensure that leads can be reliably fetched after being moved between lists or campaigns. This would include the ability to search using both list ID and campaign ID filters to ensure the integrity of lead location.
   Enhanced API Feedback:
   When using the RingCX Dialing API to move or search for leads, introduce better error feedback, including the specific list IDs involved in errors, and the exact reason why a lead cannot be found or moved.
   Testing Environment for RingCentral Tech Support:

   Sandbox for Lead Management:
   Provide a sandbox environment within the RingCX platform for Tech Support teams to test lead uploads, transfers, and fetching scenarios under various conditions (e.g., large batch uploads, cross-campaign transfers). This will help in reproducing customer issues and improving the overall reliability of lead management features.
   Automated Monitoring and Alerting:

   Real-Time Monitoring:
   Create automated monitoring for large-scale lead transfers that tracks the health of the transfer process and triggers alerts for any inconsistencies or failures. This would help identify issues before they affect the customer experience.
   Customizable Alerts:
   Allow administrators to set customizable alerts for lead upload or transfer failures, ensuring that support teams are immediately notified and can respond proactively.
   Benefits:

   Increased visibility and control over lead uploads and transfers.
   Reduced customer impact by enabling quicker identification of issues with lost or inaccessible leads.
   Enhanced troubleshooting and faster resolution for technical support teams.
   Prevents "lost" leads from being overlooked, ensuring better data integrity and accuracy.
   Reduces the risk of leads getting stuck in incorrect states, improving system reliability.
   This feature enhancement would improve the stability and reliability of lead management in RingCX, empowering administrators and support teams to quickly diagnose and resolve issues with lead uploads, transfers, and fetching.

   Feature Enhancement Request: Lead Uploading/Management Testing in RingCX

   Description:
   RingCX currently lacks sufficient diagnostic tools for troubleshooting issues related to the uploading and management of leads, particularly when leads are moved between campaigns or lists. This results in significant issues like "lost" leads that cannot be located via admin interface or API, as well as leads being improperly marked with an "active" state when no agents are logged in. To resolve these issues effectively, we propose the implementation of an enhanced testing and diagnostic mechanism that will allow RingCentral Tech Support and administrators to directly monitor and test lead uploads… more

   5 votes

   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  ·  Other  ·  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. Expanded Queue Priority Levels

   I have a customer who is utilizing 13 total Queue Priority levels with Dialpad today. They have many customers they service with queues allocated to each of them, around 90 queues total. They assign priority based on SLAs they are contractually obligated to meet. Priority Groups will not work for them as they also utilize agent ranking from 1-100. Today, RingCX has "High Level 5" as the highest tier in priority. This is extremely important to them and has been noted as a deal breaker.

   This is essential to customers who provide 3rd party support to a large client base and with a tiered approach, similar to our Advanced/Enterprise support offerings.

   Opp if needed -https://rc.lightning.force.com/lightning/r/Opportunity/006Hr00001RNd3PIAT/view

   I have a customer who is utilizing 13 total Queue Priority levels with Dialpad today. They have many customers they service with queues allocated to each of them, around 90 queues total. They assign priority based on SLAs they are contractually obligated to meet. Priority Groups will not work for them as they also utilize agent ranking from 1-100. Today, RingCX has "High Level 5" as the highest tier in priority. This is extremely important to them and has been noted as a deal breaker.

   This is essential to customers who provide 3rd party support to a large client base… more

   2 votes

   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  ·  Other  ·  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. Configure "Total" column in RT inbound dashboard to sum-up unique avail agents only

   Remove or reconfigure the "Total" on the RT dashboard. It appears to be misleading in terms of the total availability count.

   The client thinks there are 7 available agents, but the actual number is higher than it should be because agents are assigned to multiple queues, causing them to be counted more than once.

   The total number of available agents (boxed in orange) shown in the dashboard is based on the sum of the "Avail" column. Since some agents are assigned to multiple queues, they are counted more than once, which leads to a higher total than the actual headcount.

   We need the system to summarize unique agents only under the Avail column

   Remove or reconfigure the "Total" on the RT dashboard. It appears to be misleading in terms of the total availability count.

   The client thinks there are 7 available agents, but the actual number is higher than it should be because agents are assigned to multiple queues, causing them to be counted more than once.

   The total number of available agents (boxed in orange) shown in the dashboard is based on the sum of the "Avail" column. Since some agents are assigned to multiple queues, they are counted more than once, which leads to a higher total than the actual headcount.

   … more

   •  

   1 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  ·  Other  ·  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

10. Display CX and EX Presence Concurrently in the Corporate Directory

    In the corporate directory, display RingCX presence for agents and RingEX presence for non-agents side by side.

    1 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  ·  Other  ·  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. Robust Wallboard Functionality

    Add more comprehensive capabilities in the RingCX Dashboards and allow them to be shared externally.

    RingCX Wallboard is required to have the below features added:

    Images (i.e. Brand Logo)

    Scrolling / Static Text Boxes (Manual Announcements / Information updated)

    Individual Agent Statistics (Not Table View) – (Offered, Answered, Outbound, Status, Time etc)

    Calculated Statistic Values (Example: Presented – Deflected)

    Coloured/Alerting Boxes based on Statistics (Number or Text)

    2 votes

    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  ·  Other  ·  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. RingCX within India

    RingCX within India datacenter topology to provide contact center functionality for incoming and outgoing India calls.

    15 votes

    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  ·  Other  ·  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: Language Selection for Play Hold Time Announcer in RingCX

    Feature Request: Language Selection for Play Hold Time Announcer in RingCX

    Context: When configuring inbound queue events in RingCX, we would like the "Play Hold Time" feature to announce the estimated hold time for the caller in Spanish.

    Current Behavior: Currently, the "Play Hold Time" feature announces the hold time in English by default.

    Expected Behavior: We would like the ability to select the language of the announcer. Specifically, we need the option to set the announcer's language to Spanish to better serve Spanish-speaking customers.

    Support Reference: For more details on configuring inbound queue events, you can refer to the following article:
    Configuring inbound queue events in RingCX

    Feature Request: Language Selection for Play Hold Time Announcer in RingCX

    Context: When configuring inbound queue events in RingCX, we would like the "Play Hold Time" feature to announce the estimated hold time for the caller in Spanish.

    Current Behavior: Currently, the "Play Hold Time" feature announces the hold time in English by default.

    Expected Behavior: We would like the ability to select the language of the announcer. Specifically, we need the option to set the announcer's language to Spanish to better serve Spanish-speaking customers.

    Support Reference: For more details on configuring inbound queue events, you can refer to the… more

    5 votes

    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  ·  Other  ·  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. RCX Must Use CallerID Name Configured in REX

    Use a CCRN number as Caller ID when RingCX agent do a consultation call to RingEX agent

    1 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  ·  Other  ·  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. Provide an API that Allows a 3rd Party Platform to Obtain Disposition and Notes from a Completed Call

    Provide an API that Allows a 3rd Party Platform to Obtain Disposition and Notes from a Completed Call. Typlically, this would be an CRM that pulls the data rather than RCX that pushes it.

    2 votes

    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  ·  Other  ·  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. RingCX - Matching disposition in Voice and Digital Queues

    We want to be able to create a disposition that can be used in both Voice and Digital Queues.

    2 votes

    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  ·  Other  ·  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. Access to Transcript URL for Engage Messaging Channel Type in RingCX Analytics

    Access to Transcript URL for Engage Messaging Channel Type in RingCX Analytics

    Summary: The current implementation of RingCX Analytics provides interaction summaries and transcripts through the Transcript URL for various channels. However, when filtering by the Channel Type "Engage Messaging," the Transcript URL field is empty. We are requesting an enhancement to include and display transcript URLs for Engage Messaging interactions, aligning the functionality with other supported channels.

    Problem Statement: When analyzing interactions through the RingCX Analytics dashboard, transcripts are essential for reviewing communication history, particularly for compliance, training, and quality assurance purposes. While transcript URLs are available for other communication channels (such as voice and email), the URL for the transcript is not accessible when Channel Type = "Engage Messaging." This limitation impacts the ability to efficiently review and audit Engage Messaging conversations, causing workflow disruptions and incomplete data analysis.

    Feature Request: We request that the RingCX Analytics system be enhanced to:

    Generate and display a functional Transcript URL for interactions where the Channel Type is set to "Engage Messaging."
    Ensure that Engage Messaging transcripts are stored, accessible, and follow the same retrieval process as other channels.
    Implement the necessary backend infrastructure to support transcript generation for Engage Messaging interactions, if not already in place.
    Use Case:

    User Role: Support engineers, customer service managers, and compliance teams who regularly analyze customer-agent conversations.
    Scenario: A compliance officer needs to review a set of customer interactions across various channels, including Engage Messaging. Without access to the Engage Messaging transcript, the review process becomes fragmented, potentially leading to incomplete analysis and delayed decision-making.
    Benefits:

    Improves consistency in transcript availability across all supported channels in RingCX Analytics.
    Enhances the ability of users to perform comprehensive interaction reviews, which is crucial for training, compliance, and quality assurance.
    Streamlines the workflow for support and operational teams who need to access and audit Engage Messaging interactions, reducing delays caused by the absence of transcripts.
    Technical Considerations:

    Review the existing infrastructure for handling transcripts from Engage Messaging interactions. If transcripts are already being logged but not linked, the issue may be related to missing links in the analytics display.
    Implement an automated process for generating and linking transcript URLs for Engage Messaging interactions, ensuring the data format is compatible with other channels (e.g., voice, chat).
    Validate that the new functionality complies with the data retention policies and privacy guidelines applicable to RingCX.
    Priority: Medium to High (depending on the volume of Engage Messaging interactions and the frequency of audits in customer environments).

    Expected Outcome: Once this feature is implemented, users will be able to access Engage Messaging interaction transcripts seamlessly through the RingCX Analytics platform, reducing operational friction and ensuring parity with other communication channels.

    Thank you for considering this request. Please let us know if further technical details or use cases are required to support the implementation.

    Access to Transcript URL for Engage Messaging Channel Type in RingCX Analytics

    Summary: The current implementation of RingCX Analytics provides interaction summaries and transcripts through the Transcript URL for various channels. However, when filtering by the Channel Type "Engage Messaging," the Transcript URL field is empty. We are requesting an enhancement to include and display transcript URLs for Engage Messaging interactions, aligning the functionality with other supported channels.

    Problem Statement: When analyzing interactions through the RingCX Analytics dashboard, transcripts are essential for reviewing communication history, particularly for compliance, training, and quality assurance purposes. While transcript URLs are available for other… more

    6 votes

    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  ·  Other  ·  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. RingCX Digital Channel's sender name

    In RingCX Digital Channels's sender name, customers are using the variable {{first name}}{[last name}}.
    This feature is working as expected. However, if they transfer an email from one channel to another, it is still recognizing the first and last name of the agent from the channel the email was initially assigned. The first and last name should recognize the name of the NEW agent assigned from the other channel.

    Please see example below.

    The first screenshot shows the correct sender Toni. You would notice that her signature is also on the email she sent.

    •  

    •  

    2 votes

    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  ·  Other  ·  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

19. receive 2 calls

    Customer is looking for an option to receive multiple calls at the same time in the RingCX platform

    11 votes

    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  ·  Other  ·  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
    Needs More Information  ·  AdminYulia (Group Product Manager, CX, RingCentral) responded

    Thank you for sharing your request regarding the ability to receive multiple calls simultaneously in the RingCX platform. To better understand your needs and explore potential solutions, could you provide more details about the specific business scenario?

    
    

    For instance:

    • Are you looking for agents to handle multiple calls simultaneously?
    • If so, could you elaborate on why this is needed and how it aligns with your workflow?
    • Are there particular use cases or challenges you’re trying to address with this feature?
    • 
      

    Your input will help us gain clarity and ensure that we can address your requirements effectively.

20. RingCX Global Secondary Nodes

    While we have a pretty full roadmap, just this past week we have had several Global requests for RingCX. Our global requirements go beyond GDPR.

    Some requirements bubble up like multiple languages operating in the same system
    And that’s not just a voice language pack for system messages, TTS, ASR its also what language the agent uses within the RingCX Agent workspace. For call recording we must hairpin back to the US. Not to mention where data is stored and how to comply with “Forget Me” in GDPR regions.

    Those and more need to be addresses down the road, laying the groundwork for RingCX to be globally deployed is something I think I can help with.

    Today RingCentral Office can Federate https://support.ringcentral.com/article-v2/9415.html?brand=RC_US&product=RingCentral_MVP&language=en_US multiple UID’s making a larger unified system. Now it does have advantages and limitations. I have a technical proposal to leverage integrating RingCX into a Federated RCO global environment.

    Lets start with the idea of adding in our current infrastructure the ability to have the US based system configured as the Primary Node.
    The primary node will have the ability to connect to RCO API stream and operate as an API gateway that allows two way API stream between the RCO API and RingCX Primary>Secondary Nodes (this would be where Global MVP isn’t big enough to have a Federated set of UID’s)
    The Primary Node will have the ability to connect to multiple Federated RCO API streams. Then act as a gateway to RingCX secondary Nodes

    From there the creation of Secondary RingC Nodes will also support a failover API to connect to its actual paired RCO UID for “in Region/Country” fallback operation.

    Secondary RingCX Nodes will store and share meta data with Primary for use as a central Admin using Real-Time dashboards and one central reporting, while the Secondary RingCX node will maintain only its activity for GDPR.
    Secondary Nodes will have the ability to have agents programmed in Skills that exist on the Primary or other Secondary RingCX Nodes. This is critical to overcome any obstacles here as the request are to have agents anywhere answer any interaction if the agent is language proficient.

    Secondary Nodes will have a node identifier used within RingCX Admin and help in administration. Might be helpful where the secondary node is connected to a Federated RCO to show the UID and have a space for naming the node such as “rotterdam netherlands”

    Programming from the Primary Node allows for centralizing Skills etc, Programming from a Secondary Node only changes the local environment with the exception of add global agents to a local skill. Agents will need to be designated in the Primary Node as Multi Node Skilled.

    While we have a pretty full roadmap, just this past week we have had several Global requests for RingCX. Our global requirements go beyond GDPR.

    Some requirements bubble up like multiple languages operating in the same system
    And that’s not just a voice language pack for system messages, TTS, ASR its also what language the agent uses within the RingCX Agent workspace. For call recording we must hairpin back to the US. Not to mention where data is stored and how to comply with “Forget Me” in GDPR regions.

    Those and more need to be addresses down the road, laying… more

    19 votes

    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  ·  1 comment  ·  Other  ·  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