Callingly Destination

Callingly automatically gets your sales team on the phone with your incoming leads within seconds, generating better results and happy customers.

This destination is maintained by Callingly. For any issues with the destination, please reach out to their team.

NOTE: The Callingly Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on April 2, 2019. If you are interested in joining their beta program or have any feedback to help improve the Callingly Destination and its documentation, please let their team know!

Getting Started

The first step is to make sure Callingly supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.

WebMobileServer
📱 Device-mode
☁️ Cloud-mode
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “Callingly” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the “API Key” into your Segment Settings UI which you can find from your Callingly Integrations page. Click “Connect” on the Segment integration to enable it.
  4. In the Segment integration settings on the Callingly Integrations page you can also select which Team will receive the calls triggered from Segment events.

Identify

If you haven’t had a chance to review our spec, please take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  firstName: 'John',
  lastName: 'Doe',
  phone: '555-555-5555',
  email: 'john.doe@segment.com'
});

Identify calls will be sent to Callingly as an identify event. To trigger a call, you must include a phone number as aphone trait.

If the phone trait is valid, formatted either in E.164 or your country’s local standard, Callingly will add the visitor as a Lead to your account and trigger a phone call to the Team selected in your Integration settings.

To configure agents, schedules, call routing options and retry settings edit the Team settings on the Callingly Teams Page.


Personas

You can send computed traits and audiences generated through Segment Personas to this destination as a user property. To learn more about Personas, reach out for a demo.

For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property order_completed_last_30days: true, and when this user no longer satisfies we will set that value to false.

When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

API Key

Go to the Integrations page in the Callingly Dashboard and click Connect on the Segment integration to get your API key.

Adding Callingly to the integrations object

To add Callingly to the integrations JSON object (for example, to filter data from a specific source), use one of the 1 valid names for this integration:
  • Callingly


  • Questions? Need help? Contact us!
    Can we improve this doc?
    Email us: docs-feedback@segment.com!