What "parallel dialing in Salesforce" actually involves
A parallel dialer calls several numbers at once for one rep and connects the first live person who answers; the other lines drop. Salesforce does not do this natively. Its built-in Sales Dialer is a click-to-call tool, and Salesforce's own help pages say it is scheduled for retirement with no new features (Salesforce Help).
So the setup always has three parts, and it helps to keep them separate in your head:
| Part | Lives in | Owned by | What can go wrong |
|---|---|---|---|
| The list: who to call, in what order | Salesforce Report or Campaign | Sales ops or the SDR manager | Stale filters, missing phone numbers, no do-not-call suppression |
| The dialing: lines, caller ID, connecting the human | The dialer | The dialer vendor and admin | Slow handoff (dead air after "hello"), spam-labeled numbers |
| The record: what happened on each call | Salesforce activity, written by the dialer | RevOps | Calls on the wrong record, outcomes no report can group |
Most failed rollouts fail on the first or third row, not the dialer itself. That is why this guide spends more time on lists and dispositions than on clicking Connect. If you are still choosing a tool, start with our comparison of the best Salesforce dialers.
Prerequisites: the checklist before you connect anything
Work through this with your Salesforce admin. Each item takes minutes now and saves a support ticket later.
| Check | Why it matters | How to verify |
|---|---|---|
| API access on your edition | Connected dialers read and write through the Salesforce API. Nooks, for example, lists Enterprise, Unlimited, Developer and Performance as API editions, with Professional needing API as an add-on (Nooks). | Setup > Company Information shows your edition; ask your account rep if you are on Professional |
| Connected app policy | Since September 2025, Salesforce restricts which OAuth apps users can connect on their own, so first-time connections can fail with an OAuth error until an admin approves the app (Nooks documents this). | Setup > Connected Apps OAuth Usage; plan to have an admin connect first |
| Record visibility | OAuth-connected dialers inherit each user's Salesforce permissions. A rep who cannot see a report folder or a record in Salesforce will not see it in the dialer either. | Log in as a pilot rep and open the report you plan to dial |
| Clean phone fields | Inconsistent formats and old numbers waste lines. Decide which fields count (Phone, MobilePhone) and in which order. | Run a report of records with a blank or malformed phone |
| Do-not-call handling | Records marked do-not-call must never reach the dialer. | Confirm the Do Not Call checkbox on Leads and Contacts is used, and filter on it |
| Agreed dispositions | Every outcome needs a home in Salesforce before reps start clicking. | A one-page list signed off by the SDR manager and RevOps (see below) |
Build the dial list from a Salesforce Report or Campaign
The list is where parallel dialing is won or lost. Because the dialer works through numbers several at a time, a weak list gets exposed in minutes instead of days.
Report or Campaign: which to use
| Use a Report when | Use a Campaign when |
|---|---|
| You want a rolling, rule-based list ("my Leads in New, no activity in 14 days") | You want a fixed audience tied to a program (an event, a webinar follow-up, an ABM tier) |
| Each rep should see only their own records (filter on owner) | Marketing and sales need shared reporting on one initiative |
| Records should drop out automatically when status changes | You want member status to record progress (Sent, Called, Responded) |
A dialable report, field by field
- Pick the report typeUse Leads for net-new prospecting, or Contacts & Accounts for named-account outbound. Mixing both is possible with two reports; keep one report per session so reps know what they are calling.
- Scope to the repFilter Owner equals the current user ("My leads" or "My contacts"). One shared report for the whole team works, but per-rep scoping avoids two reps calling the same person.
- Require a numberFilter Phone not equal to blank, or MobilePhone not equal to blank. A report full of records with no number wastes the first minutes of every session.
- SuppressExclude Do Not Call equals true, unqualified or disqualified statuses, current customers and open opportunities that an AE owns.
- Add a recency ruleFilter last activity older than a few days so the same prospect is not called twice in one afternoon. Your sales cadence decides the exact gap.
- Sort for prioritySort by a priority field, score or time zone so the best records are dialed first, while you are fresh and before the list thins out.
- Save it in a shared folderPut the report in a folder the pilot reps can see. Name it for the session ("SDR East, net-new, morning block") so reports and dial lists stay readable.
Size the list for the block
Parallel dialing consumes records faster than reps expect. Here is a simple model with illustrative assumptions, not benchmarks: a rep runs a 2-hour block and the dialer works through about 150 numbers an hour across its lines. Each record gets one attempt per block.
| Input | Value |
|---|---|
| Numbers dialed per hour (assumed) | 150 |
| Block length | 2 hours |
| Records needed per block | 150 x 2 = 300 |
| Records needed per day with two blocks | 600 |
| Reps on the team | 4 |
| Fresh records the team needs per day | 2,400 |
Plug your own numbers into the dials-to-meetings calculator, and see how to build a cold call list for where those records come from. The practical rule: if a rep's report has fewer records than one block needs, the dialer will run out before the block ends.
Connect the dialer and start the first session
Each vendor's screens differ, but the pattern is the same. With TwinsAI it looks like this:
- Open Settings > IntegrationsIn TwinsAI, an admin goes to Settings > Integrations and chooses Salesforce.
- Sign in to SalesforceConnect by signing in with your Salesforce account. If your org restricts connected apps, your Salesforce admin may need to approve the connection first.
- Pick a Report or CampaignChoose the Salesforce Report or Campaign you built above as the dial list.
- DialStart the session. TwinsAI dials up to 8 lines at once and bridges the first live human to the rep in under 450ms.
- Check what loggedAfter the first calls, open a few records in Salesforce. Outcomes, notes and transcripts are logged back to Salesforce, so confirm they landed where your reports expect them.
Other dialers follow similar steps. Nooks, for instance, documents an admin connecting first from Settings > Integrations > Connect Salesforce, then each user connecting their own account (Nooks). Tools that install as an AppExchange package with an embedded softphone add steps in Salesforce Setup, such as assigning permission sets.
Map dispositions so every outcome lands somewhere useful
A disposition is the outcome a rep (or the dialer) assigns to a call. In parallel dialing, many outcomes happen on lines the rep never hears, so the list has to cover machine outcomes as well as conversations. Keep it short: if reps have to scroll, they pick the first option.
| Disposition | Meaning | Suggested next step in Salesforce |
|---|---|---|
| No answer | Rang out | Nothing; record stays in the report for the next block |
| Voicemail | Reached voicemail (left a message or not) | Counts as an attempt in your cadence |
| Bad number | Disconnected, wrong person, fax | Flag the phone field for data cleanup and remove from the report |
| Gatekeeper | Reached a switchboard or assistant | Note the path in; try a direct line next |
| Connected, not interested | Conversation, clear no | Update Lead Status; set a long recycle date |
| Connected, call back | Asked for a later call | Create a follow-up task with the date the prospect gave |
| Meeting booked | Meeting agreed on the call | Update status and create the event; hand off to the AE |
| Do not call | Prospect asked not to be called | Tick Do Not Call so the report excludes them immediately |
Two rules make these reportable. First, store the outcome in a field, not only in free text: dialers vary here, from Task subject tags (Orum's own help center shows a disposition report built by filtering Tasks whose subject contains "[Orum]", Orum support) to mapped fields (Kixie recommends a custom Call Disposition field on Task, Kixie). Second, let Salesforce Flow do the follow-up: a "Meeting booked" outcome can update Lead Status and notify the AE without the rep touching another screen.
If you use TwinsAI, screened calls also log as one of three outcomes: hung up, went to voicemail, or human patched to the rep. Add them to your report so you can see how much of your mobile list sits behind AI call screeners.
What gets logged, and the three reports to build on day one
With TwinsAI, calls, notes, transcriptions and outcomes are logged back to Salesforce. Whatever dialer you use, build these three reports before the pilot starts so you can judge it on data, not feel.
- Outcome mix by rep, this week. Activities grouped by disposition and owner. A rep with lots of "Bad number" has a list problem; one with lots of connects and few meetings has a talk-track problem.
- Connect rate by list. Connected outcomes divided by dials, grouped by the report or campaign dialed. This tells you which lists deserve more time. See connect rate for the definition and the connect rate guide for fixes.
- Meetings from dialing. Meetings booked from dialer sessions, by rep and week. This is the number your VP cares about, so make sure it reconciles with the calendar.
Roll it out to the team in three weeks
| When | Who | What | Done when |
|---|---|---|---|
| Week 1 | Admin plus 2 pilot reps | Prerequisites, one report per rep, dispositions, first sessions | 50 calls audited with no logging errors |
| Week 2 | Pilot reps plus manager | Daily call blocks; tune filters and the opener for faster pickups | Reports show outcome mix and connect rate by list |
| Week 3 | Whole team | Every rep connects their account, gets their own report, joins shared call blocks | Every rep has completed a full block with clean logging |
Coach the first five seconds
Parallel dialing changes the start of the call: the rep joins a conversation that has just begun, with the record popping up as they hear "hello". Train reps to glance at name and company and open immediately. Our guide to cold call openers has word-for-word options.
Prospect:Hello?
Rep:Hi Dana, it's Sam from Acme. I know I'm calling out of the blue. Can I take 30 seconds to tell you why, and you can tell me if it's worth a longer chat?
Protect the blocks once you are live. Parallel dialing pays off in focused, uninterrupted sessions; a rep who dials for ten minutes between meetings gets little out of it. For a sample day, see the SDR daily schedule.
Troubleshooting: common problems and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| A rep cannot see the report in the dialer | Report saved in a private folder, or the rep lacks access to the records | Move it to a shared folder; check the rep's profile and sharing |
| OAuth error on first connection | Org restricts self-authorized connected apps | Have a Salesforce admin connect first and approve the app in Connected Apps OAuth Usage |
| Calls log to the wrong person | Duplicate phone numbers across Leads and Contacts | Merge duplicates; dial Contacts and Leads from separate reports |
| The dialer runs out of numbers mid-block | Report too small, or filters too tight | Size the report for the block (see the model above); add a second report as backup |
| Outcomes do not change Lead Status | No automation on the disposition | Build a Flow on the logged activity's outcome field |
| Connect rate drops week over week | Numbers labeled as spam, or a list going stale | Check caller ID health (spam likely) and refresh the list source |
Frequently asked questions
Can Salesforce do parallel dialing natively?
No. Salesforce's native Sales Dialer supports click-to-call and call logging, not parallel dialing, and Salesforce's help pages say it is scheduled for retirement. To dial several numbers at once from Salesforce data, you connect a third-party parallel dialer.
Should I dial from a Salesforce Report or a Campaign?
Use a Report for rolling, rule-based lists such as "my Leads with no activity in 14 days", because records drop out as their status changes. Use a Campaign when the list belongs to a specific program and you want member status and shared reporting across marketing and sales.
What gets logged to Salesforce when you parallel dial?
It depends on the dialer. With TwinsAI, calls, notes, transcriptions and outcomes are logged back to Salesforce. Other dialers write completed Tasks, map outcomes to the Call Result field, or use their own custom objects, so check that your reports read the object your dialer writes.
Which Salesforce edition do I need for a parallel dialer?
Usually one with API access, because connected dialers read and write through the Salesforce API. Enterprise, Unlimited and Performance include it; Professional often needs API access added. Confirm with your dialer vendor before you buy.
How many lines should a Salesforce parallel dialer use?
Enough to keep the rep busy without burning the list. Low-connect cold lists benefit from more lines; small, high-value account lists are often better on a single-line power dialer. TwinsAI dials up to 8 lines; model your list in the connect-rate calculator.
- 1.Salesforce, Dialer Prerequisites: Sales Dialer is scheduled for retirement, checked 2026-10-22 (2026)
- 2.Nooks, Getting Started with Salesforce (editions with API access, OAuth app change, permissions), checked 2026-10-22 (2026)
- 3.Orum, Salesforce Integration: Call Disposition Report Using Subject Line (2024)
- 4.Kixie, How to Automate Call Logging in Salesforce (custom disposition field) (2026)
- 5.FCC, Stop Unwanted Robocalls and Texts (consent rules, calling hours) (2026)
Spend your reps' day on conversations, not ringing phones.
TwinsAI parallel-dials up to 8 lines at once, validates every number with the carrier before it rings, and bridges a live prospect to your rep in under 450ms. It works inside HubSpot, Salesforce, Close, Attio, Outreach, Zoho and HighLevel, with no seat minimum.