using it you will able to call most significant tlib functions from ORS or from any 3rd party application via http/ors. why don’t make you own call back?
ors is really much more that urs with http interface
Just to let you all know I have designed and currently developing a Call Queueing solution which will GA in September. It does not use the PSDK or ESDK (which means saving $$$$$) and was designed to be integrated with standard Inbound Routing. Actually it’s not Genesys dependent
How does it differ, well the killer functionality is that persuades URS to route and queue a ‘virtual call’ so that the caller’s position is retained.
The pricing is about the same as the PSDK and this basic package includes a test/dev environment license (non-production) and 2 executable Production licenses (so to provide HA resiliency). This will allow for about 400 concurrent queuing calls!
If you’re interested and want to be the first customer and get the licenses for free, send me a PM.
I’ve implemented a rudimentary callback service too. I didn’t realise I was infringing on any patents though ;D
My solution did not require prioritization or keeping position in queue. All I did was offer a repeatable callback announcement sub at a configurable time and interval in queue, which captured and confirmed DTMF digits, and wrote it to an OCS table. Agents were blended for inbound and outbound calls, so callback occurred when next agent became available. By tuning the time at which callback was offered, it was possible to get it pretty close to EWT.
It worked fine - other than for the fact that the CC manager would sometimes stop the outbound campaign at busy times :