Frequently Asked Questions
What Click-to-Dial Integrations do you support?
Our Integrator app includes click-to-dial through web browser addons for all the major web browsers (Chrome, Firefox, Opera, etc). We also provide TAPI dialer for your windows apps.
Do you support Custom Integrations?
If you use a CRM that is not supported, we can create a special development project to build a Custom CRM Integration within our integrator. This requires that your CRM has an open API, and will provide us proper access and documentation to access it. Custom integrations typically include the Screen Pop and Contact Search features. The development cost typically starts at $1,495 one-time fee, after which users can be added with no additional development charges.
Can I create Custom Call Events?
Without integration, you can easily create custom call events to pass a caller’s phone number in a URL. We can also pass a phone number as a Windows program Command Line Parameter if you are using an installed application that supports that method.
Some CRMs support screen pops or other interactions by passing a phone number in a URL to trigger a contact search, such as: https://YourCRM.com/search/ [phone-number]
You can create custom events to trigger on a ringing call, and answered call, an outbound call, or a manual button press. This is not only limited to screen pops – any functionality your CRM can support by passing a phone number could be customized with these events.
Windows TAPI drivers
Windows TAPI is a protocol user by some Windows applications to initiate phone calls. This will allow Windows TAPI-enabled apps to use Verve Go Integrator to initiate phone calls.
You can enable TAPI drivers in Verve Go Integrator in the Configuration > Dialing > Dialing Helpers section – simply click “Enable” next to the TAPI driver you would like to enable.
Note: Refer to the manual of your TAPI-enabled application to configure dialing.
| Driver type | Function | Examples |
|---|---|---|
| TAPI driver (dial only): This option refers to any application that supports/allows TAPI dialing. |
Once you have enabled TAPI and configured your CRM application, you will be able to dial out telephone numbers directly from your CRM application. Please note that when Skype for Business or Lync is installed, it can take over the Call function within Outlook causing the TAPI option to be disabled in Outlook. | For TAPI-enabled programs like GoldMine, our software provides a TAPI (dial only) driver to handle call requests from such CRMs to the telephone system. |
| TAPI request handler: Certain types of TAPI applications don’t specify a device to use. They simply hand-over the command to Go Integrator Client to handle the TAPI request. |
Once you have enabled TAPI, turned on this option and configured your CRM application, Go Integrator Client will handle the TAPI requests and allow you to dial telephone numbers directly from your CRM application. | If you happen to use one of this type of CRMs (e.g. Sage Line 50), our software will capture and handle the TAPI request sent by this application. |
| CallTo protocol handler: CallTo is a protocol used for marking up telephone numbers. |
By enabling this option Go Integrator Client will identify the CallTo protocol and use the marked parameters (e.g. CallTo:0123456789) to handle the “Dial” request via our in-built PhoneHelper.exe application. | Our software can work with any type of application (e.g. Maximizer) that supports CallTo protocol to handle calls. |
Troubleshooting
For specific troubleshooting topics, see the following sections:
Need more help with this?
Don’t hesitate to contact us here.