Integration · Talkdesk to Salesforce

Talkdesk and Salesforce integration

Talkdesk decides who answers and Salesforce is where it has to be recorded. We connect them so agents see the record on answer and every call is logged — built on Flow, sized against your field limits, and documented well enough to survive three Salesforce releases a year. It is a one-time setup by our team, not a monthly middleware subscription.

  • From $100, one-time setup
  • No monthly fees from us
  • Tested on your own calls before go-live
Get a written scope
Talkdesk Salesforce

One call ends in Talkdesk. In Salesforce:

  1. Studio routes the callRing group, attribute or agent
  2. The agent sees the recordContact, lead or case history
  3. Logged and the Flow runsCall, outcome, next step
One-time setup
From $100
Monthly fee from us
$0
Working days to a written scope
2
Working days to build and test
5–10

Two systems that both change underneath you

This is an enterprise pairing, and the risk is not whether it can be built. It is what happens six months later. Salesforce ships three major releases a year, and it stopped supporting Workflow Rules and Process Builder at the end of 2025 — existing ones still run, which is exactly why so many orgs are carrying call logic in tools that will never be improved again. Meanwhile a Talkdesk Studio flow can be re-pointed by whoever owns the contact centre, and an assignment step that used to reach a ring group now reaches named agents.

So the build is as much about seams as features. Logic goes in Flow. Outcomes go into a small number of fields, because Enterprise allows 500 custom fields per object and field history tracks only 20 per object without Field Audit Trail. And everything the integration relies on in Studio is written down, so when the contact centre changes a flow, someone knows what else it affects.

  • Contact centres on SalesforceAgents answer with the record already open.
  • Orgs modernising automationCall logic built on Flow rather than retired Workflow Rules.
  • Teams with long queuesCalls that time out through an exit are recorded, not lost.

What we connect between Talkdesk and Salesforce

A typical setup. We adjust each line to how your team uses Talkdesk and Salesforce.

When this happensThis is what you get
An inbound call routed by StudioThe matching contact, lead or account, shown to the agent
A call endsA logged call on the record, with the agent and duration
The agent dispositionThe field you choose, with the Flow that should follow it
A call that leaves through an exitLogged with a task for the record owner
The call recordingLinked from the logged call
A caller not in Salesforce yetA new lead, checked against existing records first

Field mapping, event by event

Each Talkdesk event and exactly what it writes in Salesforce. Pick an event to see its fields.

1. Trigger · Talkdesk When a call ends Every call made or received in Talkdesk
2. Action · Salesforce Log the call In Salesforce, on the contact or lead — Where your team already works
Salesforce field Mapped from What happens
Activity date Timestamp start15 Sep, 4:00 pm Shown in your time zone
Call length Call duration seconds3 min 04 s Stored the way Salesforce expects
Direction Call directionInbound Inbound or outbound
Call outcome Call outcomeInterested Matched to your own list of outcomes
Recording Call recording urlPlayable audio Added once the file is ready
Call notes Call notesAsked for pricing Saved as note text
Owner Rep’s nameMaria Lopez Matched to the same person in Salesforce
Contact or lead Matched by phone number+1 415 555 0142 A new contact or lead is created only if none match
1. Trigger · Talkdesk When an outcome is set A rep marks how the call went
2. Action · Salesforce Update the opportunity In Salesforce — Moves one record, not all of them
Salesforce field Mapped from What happens
Which opportunity Most recent open opportunityNorthwind — 12 seats On the matching contact or lead, owned by the rep on the call
Stage Call outcomeInterested Looked up in the outcome-to-stage list we agree with you
1. Trigger · Talkdesk When a call is missed Nobody picked up in time
2. Action · Salesforce Create a task In Salesforce, for the contact or lead owner — A call-back nobody forgets
Salesforce field Mapped from What happens
Title Caller number+1 415 555 0142 “Call back” plus the contact or lead name, or the number if unknown
Due Your follow-up windowWithin 1 hour Set to how fast your team calls back
Assigned to Contact or lead ownerMaria Lopez Falls back to the rep who was on the line

Sample values are made up. The exact fields are agreed with you in your scope.

A one-time setup, not a monthly middleware bill

We are not a middleware. We plan the connection, set it up, test it on your calls and hand it over.

Web Repay integration setup Middleware subscription
What you pay One-time setup, from $100 (one-off) A monthly plan, often priced by tasks or operations
As call volume grows The same price, no per-task charges Costs rise with every call that syncs
Who builds and tests it We do, on your own Talkdesk calls Your team builds and maintains every step
Where it runs In your own Talkdesk and Salesforce accounts, documented Inside the middleware vendor’s platform
When something changes Additional support as needed, when you request it Your team fixes the broken steps

Where a small connector layer is the most reliable route, we say so in your written scope, set it up in your own account and choose the option with the lowest running cost.

Where Talkdesk and Salesforce setups usually go wrong

Workflow Rules are retired

Support ended on 31 December 2025, though existing rules still run. We build on Flow and tell you where call logic sits in something that will not be maintained.

Fields are finite

Enterprise allows 500 custom fields per object and Unlimited 800, with field history on only 20 fields per object without Field Audit Trail. Outcomes go into a small set of fields, not one per disposition.

Maximum wait is a silent exit

When a Studio step reaches its maximum waiting time the call leaves through an exit. We record that as a real event, because a caller who waited and gave up is worth a callback.

Locked default roles

Talkdesk’s default Agent and Supervisor roles cannot be renamed or modified, so different permissions mean a custom role. Better known before the plan assumes otherwise.

How we set it up

  1. 1

    Agree what connects

    Which flows and numbers are in scope, what the agent sees on answer, how exits are handled, and the field and Flow footprint. You get a written scope with a fixed one-time price.

  2. 2

    Access for the setup

    A Salesforce user with a profile and permission set covering the objects involved — sandbox first where you have one — and a Talkdesk role covering Studio and the numbers in scope.

  3. 3

    We connect and test

    We call in and get answered, and call in and wait past the maximum, then check the record, logged call, task and Flow in both cases.

  4. 4

    Handover

    A short document of what is connected, including the Studio steps and Salesforce fields it depends on. It runs in your own accounts, with no monthly fee from us.

Call centre agent on a headset at her desk
Test call passedEvery field in the table checked LiveWatched for the first week

What it costs

From $100 one-time setup

Starting price for connecting Talkdesk and Salesforce, built and tested. Larger mappings get a fixed quote in writing before we start.

No monthly fee from us. Additional support is available as needed, whenever you request it.

Get a written scope

Tell us what should happen in Salesforce when a call ends. We reply within 2 working days.

Questions about Talkdesk and Salesforce

Are Talkdesk calls logged in Salesforce?

Yes, on the matching contact, lead or account, with the agent, duration, disposition and a link to the recording — and the agent sees the record before they answer.

Will this work alongside our Workflow Rules?

They still run, but Salesforce ended support for Workflow Rules and Process Builder at the end of 2025. New logic goes in Flow, and we flag call automation still sitting in the retired tools.

What happens to calls that time out in a queue?

They are logged. A Studio step that reaches its maximum waiting time sends the call to an exit, and we record that on the record with a task rather than letting it vanish.

Is there a monthly fee?

No. You pay once for the setup. Unlike Zapier, Make and similar middleware subscriptions, there is no monthly or per-task charge from us. Your Salesforce and Talkdesk plans are unchanged.

Rather talk it through?

Thirty minutes on how your team uses Talkdesk and Salesforce. You leave knowing what we would build and what it would cost.

Call +91 82857 48750
Person working on a laptop by an office window
Call ended03:04 · inbound Opportunity updatedCallback booked Call-back taskAssigned to the contact owner