Supported CRMs
- General
- Industry
- Bring your own
HubSpot, Salesforce, Zoho, Pipedrive, Microsoft Dynamics 365, Bitrix24, Close, Copper, Capsule,
Insightly, Keap, Nimble, Nutshell, Salesflare, SugarCRM, Vtiger, Freshsales, ActiveCampaign,
GoHighLevel
Capabilities vary by CRM, because their APIs do. Everything supports contact and lead reads and
writes. Richer features like pulling a segment into an outbound audience are available where the
CRM exposes them, and a driver that does not support one says so clearly rather than failing.
What the agent does with your CRM
Reads during a conversation. A caller who already exists in your CRM is recognised, and what you know about them is available to the agent. Writes what it learns. A new enquiry becomes a contact and a lead. A booking becomes an appointment. A qualified conversation updates the record with what the customer said. Writes to your field names. Not generic ones. See Field mapping.Appointment sync
Bookings made in Vorel appear in your CRM, and changes flow both ways where the CRM supports it. A reschedule in your CRM is reflected in Vorel, so your team does not have to remember which system to change.CRM events drive automation
Every CRM webhook event feeds the trigger engine. A stage change, a new deal or an updated contact in your CRM can assign a conversation, change its priority, or place an outbound call. This is the integration most teams underuse. It means “call the lead when they reach proposal stage” is a rule you configure, not a project.Reliability
CRM writes are queued rather than performed inside the customer’s turn. A CRM outage slows the mirror, it does not stall the conversation or lose data. Failed writes retry with backoff, and the retry state is visible under Reliability so a persistent failure is not silent. Availability paths fail open by design: if your CRM is unreachable, the conversation still happens and the write catches up.Health and diagnostics
The connection page shows the live state of your CRM connection and surfaces credential problems before they turn into a queue of failed writes. You can also inspect what fields the CRM exposes, which is how field mapping is configured against reality instead of a guess.If you have no CRM
Use the custom webhook driver to receive the same records at your own endpoint, or the public API to pull them. Leads and bookings are still captured and visible in Vorel either way.Related
Field mapping
Writing to your field names.
Triggers
Acting on CRM events.
Webhooks
Getting Vorel’s events into your own systems.
Outbound
Pulling a CRM segment into a campaign.