Click2Call Integrations

Find out how to create and manage Click2Call integrations and implement them in your CRM for seamless one-click phone call functionality.

A Click2Call integration lets you easily integrate calling services in your CRM. It is a VoIP API integration via an HTTP GET request that uses a hyperlink to initiate a phone call. The Click2Call integration will be displayed as a button in your CRM for a one-click connection.

You can access Click2Call integrations and create a new one in Settings > Click2Call Integrations.

Screenshot of Click2Call Integrations in the Settings menu

Click2Call Integrations in the Settings menu

Creating a Click2Call Integration

To create a new Click2Call integration:

  1. On the Click2Call Integrations page, click Add New Click-to-Call.

    Screenshot of adding a Click2Call integration

    Adding a Click2Call integration

  2. On the page that opens, fill in the general information for your integration:
    ​C2C name - specify the name of your integration to be able to find it in the list
    ​CRM name - select between a custom and HubSpot integration
    ​Allowed IPs - enter all the allowed IPs
    ​Activate Click-to-Call - use the toggle to choose if the integration will be enabled or disabled.

    Screenshot of integration settings

    Integration settings

  3. In the Custom C2C Fields for Call Records List (CDRs) section, add custom parameters that will be displayed on the Call Records List page in the c2c_details column. The fields you add will also be automatically included in the Click2Call integration link.

  4. Click Add New Click-to-Call.

The new integration will be added to the list.

Click2Call Integration Link

On the right of the Click2Call integration creation page, you will see the Click-to-Call Integration Preview window.

Screenshot of copying the integration link

Copying the integration link

Once you add a new integration, an integration link will be generated in this window. To implement Click2Call, copy the link and paste it into your CRM.

📝

EXAMPLE

lega = the caller (the agent's virtual extension)
leg_b = the destination phone number
route_number = outbound call prefix (the default prefix is _00
).
This prefix must match the existing prefix configured at the dial pattern on the outbound route.

Screenshot of the static and dynamic parts

Static and dynamic parts

Managing Click2Call Integrations

The list of your integrations will be displayed on the Click2Call Integrations page.

Screenshot of the Click2Call Integrations page

Click2Call Integrations page

You can perform the following actions:

  • Find the needed integrations using the filters in the Search C2C Integration by Filter section.
  • View the list of your integrations in the table below the search filters.
  • Disable or enable your integration by using the toggle in the Active column.
  • Edit or delete an integration by clicking on the respective icon in the Actions column.
  • Disable or enable multiple integrations: select the required integrations in the list and use the actions in the drop-down lists above it, then click Process.

Click2Call Errors Explained

The following table describes errors you may encounter while operating the Click2Call feature:

Response CodeErrorDescription
404Record Not FoundClick2Call adapter does not exist or is disabled.
403Requests from this IP address are not allowedAdd your IP to the Click2Call adapter Allowed IPs
401Missing Required ParametersThe mandatory fields that must exist inside your C2C request are uid leg_a and leg_b. One of them is missing.
501Leg A wasn't foundYour agent extension (leg_a) is not found on your account, or the agent is disabled. The call can't be made to the destination.
501Can not make phone connection - destination exceeds max attempts limit.You reached the maximum allowed number of times to dial the same destination (leg_b). Wait until the next day or call support.
501Can not make phone connection - no outbound route matchedYour account has a missing outbound route configuration that matches your destination and agent. Go to the "outbound routes" page and set the missing logic.
501Leg A didn't answerCan't make a call to the destination (leg_b). The agent (leg_a) did not answer the initial call, so click2call failed to make the outgoing call.
201OKThe call was initiated successfully at the destination (leg_b).