Has anyone got any experience of routing calls with CTI instead of using large amounts of vectors. I have 2 switches in 2 sites - in Europe with all the languages that are spoken and different products we have - vectoring is becoming one big headache!
Ok basically you need an external scripting or routing process.
MicroAutomation should have this module available and so should the IVR.
What would happen is a call would come in and get directed to the IVR (for instance). The IVR would run a script ( your business rules, holiday.............. then transfer the call. This transfer can occur to a vdn, agent depending on the value returned in the script or database.
This is a standard feature on most CTI systems and IVR's but you have to have the routing module available.
Ive done this within Genesys integrating into Avaya, Alcatel, Nortel.
You can add alot of value by introducing CTI and associated modules.
Dont forget it can also add certain types of complexity as well.
The value I like - the complexity - NO. Did you incorporate a back up for a potential CTI outage? I'm wondering if I should - then they would need to be a complex as the existing vectoring is anyway.
In terms of redundancy depending on the how much the customer deems acceptable service in an outage. I have had customers that want to mimic the CTI and others that can live with general service no customer segmentation stuff.
Most cases i will build in enough redundancy, but yes it can become complicated, but with multiple languages, skills, agents, business units and maybe multimedia the script or routing engine will eventually be easier to manage.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.