If you run a field-service CRM — Jobber, Housecall Pro, or ServiceTitan — that’s the integration that matters most for booking and dispatch. See Field-service CRM.
Supported
GoHighLevel
GoHighLevel
Contact sync, lead management, and campaign automation. GHL calendars can also serve as the availability source the agent books against — see Calendars.The most complete of the general CRM integrations, and a common choice for agencies running Recepta.ai on behalf of clients.
HubSpot
HubSpot
Contact sync and lead management. Contacts created by calls and forms flow into HubSpot so your pipeline reflects phone activity.
Pipedrive
Pipedrive
Contact sync and lead management.
Zoho CRM
Zoho CRM
Contact sync and lead management.
Google Sheets
Google Sheets
Contact sync to and from a spreadsheet. Useful for teams whose list lives in Sheets today, and as a quick way to get data out for analysis.
Connecting
All of these connect over OAuth from Integrations. Authorize with an account that has permission to read and create contacts, and that will still exist in six months.Choosing a direction
CRM as source of truth
Your CRM holds customer data; Recepta.ai reads from it and pushes back call and booking activity. The usual arrangement when you already run a mature CRM.
Recepta.ai as capture point
New leads arrive through calls, web forms, and ads, and flow out to the CRM. Sensible when most of your new business starts on the phone.
Depth varies
These integrations are built around contact and lead sync. Deeper write-back — deals, pipelines, custom objects — differs by provider and is not uniform across them. If you depend on a specific field or object being written, test it end to end before you rely on it, and contact info@recepta.ai if you need something that isn’t there.Building your own
When the native integration doesn’t reach far enough, the API and webhooks do:Contacts API
Create, read, update, and delete contacts from your own systems.
Webhooks
Receive
call.ended, sms.received, and contact.created as they happen.