CRM Integrations Guide

Keep the CRM you already run, and let ICTCRM handle the calls, two ways.

Plenty of teams have a system of record they are not going to move. ICTCRM ships with 23 connectors so you can keep that CRM and still get the dialer, the campaigns and the call history. Here is how the two-way flow works.

The 23 connectors

Salesforce, HubSpot, Zoho, Dynamics 365, SugarCRM, SuiteCRM, Pipedrive, Zendesk Sell, Freshsales, ActiveCampaign, Keap, Bitrix24, VTiger, Copper, Close, Monday, Capsule, Streak, Apptivo, Agile CRM, Less Annoying CRM, Creatio and YetiForce. If your CRM is on that list, you are ready to connect it.

Pulling contacts in

Import contacts from your CRM into ICTCRM calling lists, so a campaign always runs on current data. Do-not-call flags come across on import, so you are not dialing anyone you should not.

Pushing results back

When a call finishes, the result and the disposition go back to the right record in your CRM. Your system of record stays authoritative, and it gains the one thing standalone CRMs miss: what actually happened on the phone.

Which approach is right for you

If your team lives in Salesforce or HubSpot, connect it and use ICTCRM as the calling engine. If you are starting fresh or your current CRM is a spreadsheet, the honest answer is to run ICTCRM as your CRM directly. You get the timeline, the pipeline and the calls in one product, with nothing to sync. The migration wizard and REST API bring your data across either way.