Click To Call

[Guest TheyCalled Paul]

Hi,

 

Is anyone doing Click to Call with voiceguide. Our web server and VG servers are different. We would like to do a click to call feature but are unsure of the best (fastest response time) way to do this.

 

If we use External OutDialQue Source and put a row into this table do you know how long it will be until VG dials? Or should our web page call a web service on the vg server? Inserting data into SQL is the cleanest for us. I hope that some of you are doing this and would like to hear how its going. Once it places the outbound call we are all set.

 

We did something like this using tapi and another platform for a client at www.nophonetrees.com but would like to do it with vg.

 

Thanks.

 

Paul

[SupportTeam]

We would like to do a click to call feature but are unsure of the best (fastest response time) way to do this.

At this stage the delay between dialing would be on average 0.5 seconds regardless of the method used. The delay would be at most 1 second. The COM and the Remoting and WCF interfaces all place the outgoing entry into the local VG database, and then VG takes any new calls from the databases (local and external) within a second. We have made customized versions of VoiceGuide which remove this 0.5 seconds delay as well, but for most people the 0.5 second (1 second at most) delay is fast enough.

 

If you need absolutely no delay then please contact sales@voiceguide.com for pricing on the customized version.

 

If we use External OutDialQue Source and put a row into this table do you know how long it will be until VG dials?

0.5 seconds on average. Maximum delay would be 1 second.

 

Or should our web page call a web service on the vg server?

You can use WCF services with VoiceGuide v7 as well.