Sub Account Architecture within ACE for RingCX
In order for ACE to be a true solution for a BPO customer, we need for the solution to follow our RingCX sub account architecture. What belongs with Sub Account A within RingCX should be within ACE for Account "A" and so on and so forth. Without this architecture we risk muddying the analytics and conversational intelligence across different industries and intents, not to mention the data integrity of our clients. I'd imagine for non BPO, this would be important for varying lines of business that require segregation from one another as well.
2
votes
Jaimie
shared this idea