Recognise the caller
Planned CRM connections include HubSpot, Salesforce, Pipedrive and Zoho. The intended workflow opens a matching contact and keeps call activity with the record.
Integrations
Put the call beside the customer record.
The planned Calls UK integrations are intended to reduce the copying and searching that follow a call. Start with the task you want to make easier.
Work with Teams
A Teams calling requirement needs its own connectivity, licensing and implementation scope. Include it in the design discussion.
Connect your own tools
Planned events and webhooks could trigger follow-up work in your application, Zapier or Make. Each connection needs defined permissions and checks.
What to work through
Step 1
Pick one task
Describe what should happen when a call starts, ends or goes unanswered.
Step 2
Identify the records
Agree which customer data the connection needs and who can access it.
Step 3
Test before enabling
Check matching, duplicate events and failures in a separate test environment.
Questions you might have
Are these connectors live in this preview?
No. The catalogue reflects the CRM development brief. You can explore the intended experience without granting access to any external account.
Can our developer integrate directly?
The developer page explains the intended event model and includes a clearly labelled sample. Production endpoints and credentials are supplied when the platform is released.
Put it into a design.
Add your teams, try the caller journey and download an itemised estimate from the builder.
Build your system