CloudTalk Salesforce Integration: Setup, Sync and Limits (2026 Guide)

What the CloudTalk Salesforce integration does

CloudTalk is a cloud phone system for sales and support teams. The Salesforce integration connects it to your CRM so a rep never has to copy a number, a call note or an outcome from one tool into the other.

According to CloudTalk’s help center, as of October 2026 it covers five jobs:

• Calling inside Salesforce. The CloudTalk softphone sits in the Salesforce utility bar. Reps click a number to dial, and they can also dial from the CloudTalk app.
• Caller match on incoming calls. CloudTalk checks the incoming number against Salesforce and shows the matching contact or lead, with history and notes, before the rep answers.
• Call logging. Each call becomes a Task (activity), a Case, or both, with direction, result, durations, numbers, tags, notes and a link to the recording.
• SMS and WhatsApp logging. Messages can be exported as Tasks.
• Contact sync. CloudTalk imports your Salesforce contacts and leads, keeps them updated, and can create a Salesforce lead or contact when an unknown number calls.

It is a calling integration, not a general data sync. Opportunities and accounts only appear as places to attach call activities.

Requirements: plan, edition and people

CloudTalk prices its plans per user per month. The pricing page shows euros by default, with a US dollar option, so confirm the US price before you buy. The Salesforce side adds no license cost for the classic CTI install. The Salesforce Voice route does, as covered below.

Your options compared

Four ways to get CloudTalk calls into Salesforce, from simplest to most work:

Comparing CloudTalk with other phone systems? Our Salesforce CTI integration guide covers vendor packages, Salesforce Voice and custom builds side by side. The RingCentral Salesforce integration and Zoom Salesforce integration guides go deep on two alternatives.

Which option fits you?

The main fork for CloudTalk is classic CTI or Salesforce Voice, so two of these five questions are about your org’s age and Omni-Channel. The rest decide whether workflows or custom code should sit on top.

How the data flows

The design that holds up: Salesforce is the system of record for people (contacts, leads, accounts, owners). CloudTalk is the system of record for calls, messages and recordings. Salesforce gets a Task with the call facts and a link back, not the audio file.

According to CloudTalk, the first connection runs a full import of your Salesforce data. After that, most changes reach CloudTalk through webhooks, usually within about a minute, with a scheduled background sync as a backup. Records match on phone number, email or Salesforce ID.

Field mapping: what goes where

CloudTalk fills a fixed set of Task fields on each call. Your job is to decide which calls log, where they attach, and which extra contact fields CloudTalk needs for routing.

Two details catch most admins. First, new custom field mappings don’t apply to contacts already synced: CloudTalk’s fix is to set the integration to Inactive, save, then set it back to Active. Second, some call data may not show on the Task layout until you add the fields in Object Manager under Task, Page Layout.

How to set it up, step by step

The setup starts on paper and in a sandbox, because CloudTalk connects to one Salesforce org at a time and switching later means reconnecting. For the exact buttons, use CloudTalk’s help center, which tracks the current dashboard.

1. Write down your logging rulesWhich call types should log (outbound answered, unanswered, inbound answered, missed, voicemail, redirected), which should open a Case, and whether calls should attach to opportunities. This becomes your settings sheet.
2. Check plan, edition and peopleExpert plan in CloudTalk, Enterprise or Unlimited in Salesforce, and one admin who exists in both with the same email address. Check your custom field headroom in Salesforce before the install.
3. Start in a sandboxCloudTalk connects to one org at a time. For a sandbox, change login.salesforce.com to test.salesforce.com on the login screen during authorization.
4. Install the CloudTalk CTIIn the CloudTalk dashboard, open Settings, then Integrations, add Salesforce and choose Install CloudTalk CTI. Log in to Salesforce and install for all users, which CloudTalk recommends to avoid authorization errors.
5. Set up the call centerIn Salesforce Setup, open Call Centers, select CloudTalk.io and use Manage Call Center Users to add the reps who will call.
6. Add the softphone to every calling appIn App Manager, edit each Lightning app reps use (Sales, Sales Console, Service Console, Sales Engagement) and add Open CTI Softphone as a utility item. You can label it CloudTalk.
7. Authorize in CloudTalkBack in CloudTalk’s Salesforce integration settings, allow access, confirm the status is Active and save. Contacts start syncing now.
8. Configure logging and sync settingsChoose whether a call is created when answered or ended, and set the activity and case status per call type. Then set the opportunity strategy, connected numbers, business-hours policy, SMS export and the unknown-number rule. Add custom field mappings for routing.
9. Test real scenariosInbound from a known contact, from a lead, from an unknown number and from a number shared by two records. Then a missed call, a voicemail, an SMS, a transfer, and a call from a rep who isn’t a call center user. Check each Task lands on the right record with the recording link.
10. Pilot, then switch on productionRun one team for a week or two, then disconnect the sandbox, connect production, repeat the settings, and add users in waves.

Built by Gilzor

Results we’ve shipped

70+products launched

98%delivered on time

85%clients come back

Aviation33%faster baggage weigh-inWeb and Mobile application for Airlines→Healthcare+30%lab test ordersMedical Lab Web and Native Mobile Applications→Retail · Startup700+stores aggregatedMobile application for Grocery shops→

Talk to the people who build it. Tell us about your project and get a free estimate of scope, timeline and cost.

See how we’d approach yours →

Pitfalls and how to fix them

The Open CTI retirement and what it means for CloudTalk

According to Salesforce’s Trailhead, Open CTI has been in maintenance mode since 2020. It has been unavailable for newly created Agentforce Service orgs since February 16, 2026, and retires entirely on February 28, 2028.

After that, the Open CTI JavaScript API, call center adapters, softphone layouts, call center definition files and custom CTI logic built on them stop working. Salesforce points customers to its Voice products, such as Partner Contact Center or Agentforce Contact Center.

CloudTalk’s classic setup adds the Open CTI Softphone to your apps, so it sits on that timeline.

CloudTalk also offers a Salesforce Voice integration on partner telephony and describes it as built on Salesforce’s current framework rather than Open CTI. According to CloudTalk, it is part of the same Expert plan, and Salesforce bills its own Voice and telephony charges separately. Its admin guide covers the setup:

• Salesforce side: Service Cloud Voice enabled, the Partner Telephony Permission Set with the contact center rep, admin and supervisor permissions, and a Partner Telephony contact center created with a certificate CloudTalk provides.
• Security and console: CloudTalk’s CDN added as a trusted URL, presence statuses and decline reasons in Omni-Channel, and the Voice Calls related list on contacts.
• Known gaps: warm transfers take an extra click because Salesforce Voice doesn’t support single-click warm transfers, and CloudTalk lists Salesforce Classic support as not confirmed.

What to do now: new Agentforce Service orgs can’t use Open CTI at all, so start there on the Voice route. Existing orgs can run the classic CTI for now, but budget for Salesforce Voice licenses, or another plan, before early 2028. Our Salesforce CTI integration guide compares the Voice options and their list prices.

When to go beyond the standard integration

CloudTalk has two levels of extension before you write a separate service:

• Workflow Automations. Triggers on calls, messages, contacts, users, recordings and transcriptions, with optional conditions and actions such as an API request, an SMS or a Slack notification. CloudTalk’s Salesforce actions let a workflow call the Salesforce API with the integration’s own OAuth connection, for example to update a lead status after a connected call. Note that they run only on the most recently created Salesforce instance.
• Webhooks and the API. CloudTalk streams events to your own endpoint through webhooks. Its REST API uses HTTP Basic authentication on API keys and covers call history and recording downloads, contacts, and SMS and WhatsApp messages. CloudTalk’s pricing page lists APIs, webhooks and the workflow designer on its Essential and Expert plans.

Custom work pays off when:

• Calls must update several objects with business rules: lead scoring, next steps, SLA timers on cases.
• You need call data in a custom object or a data warehouse, not only in Tasks.
• You run several Salesforce orgs, or CloudTalk next to another phone system.
• You need an audit trail of what was written where, with retries and alerts.

A typical build is a small middleware service: CloudTalk webhooks in, the Salesforce REST API out. Around that sit a link table of call IDs and Salesforce record IDs, idempotency so retries don’t create duplicate Tasks, and monitoring. Our Salesforce API integration guide covers the Salesforce side.

If a CloudTalk workflow action or a single webhook covers the gap, you may not need a build at all; multi-object rules and audit trails are what push the price up. The ranges are from our API integration cost guide. For the wider picture of Salesforce connections, see the Salesforce integration guide.

Go-live checklist

Use this list before you disconnect the sandbox and connect production. Ticked items show how much of the rollout is settled, including your route past Open CTI.

FAQ

Where Gilzor fits

For CloudTalk, the big choice is classic CTI now or the Salesforce Voice route, and that choice shapes everything else. Gilzor, a software development company in Poland and Cyprus, builds and maintains Salesforce integrations.

We can set call logging rules with your sales and support leads, configure either CloudTalk route, or add custom flows on the CloudTalk and Salesforce APIs, and support them after launch. How we scope that is described under Salesforce integration services.