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.