Scalelist has no native dialer integration today: there is no direct connector for Aircall, Orum, Nooks, Kixie or any other dialer. You can still load Scalelist’s direct mobiles into your dialer through four routes that work now: a CSV file, the native HubSpot push, the Scalelist Zapier app, or the REST API.

This guide gives the steps for each route, the CSV rules of six common dialers from their own help centers, a field map, and fixes for the errors that stop an import.

Does Scalelist have a dialer integration?

No. Scalelist does not have a native integration with any dialer. Its only built-in CRM push is to HubSpot, and its other direct syncs are email sequencers, not dialers.

What works today is a two-step handoff. Scalelist finds the people and their mobiles, then your dialer loads them from a CSV or from HubSpot. This table shows the route each dialer supports, from its own help center.

Dialer CSV upload Reads a HubSpot list Zapier last step
Aircall Power Dialer, 1,000 numbers Chrome extension, from the open page Via HubSpot
Orum Import a new CSV HubSpot Contact Lists Via HubSpot
Nooks If an admin enables it Native HubSpot integration Via HubSpot
Kixie PowerList upload HubSpot list into a PowerList Add to Powerlist
PhoneBurner Contacts, Import Syncs HubSpot contacts Create Contact
JustCall Sales Dialer campaign Import from your CRM Via HubSpot

How to send Scalelist mobiles to your dialer

The whole job takes five steps, and only the second one uses credits.

Dialer integration flow for Scalelist: describe the buyer, reveal mobiles at 20 credits each if found, move by CSV, HubSpot, Zapier or API, load, dial
No connector sits between Scalelist and your dialer; step 3 is where you pick the route that fits the dialer you have.

1. Describe the people you want to call

Type one sentence into the Lead Finder, such as “Heads of Operations at US manufacturers with 200 to 1,000 employees”. Scalelist shows what it understood and how many people match before you spend a credit. Already have names and companies? Upload them to the Mobile Finder instead.

2. Reveal mobiles and emails

Reveal the people you will call this week. A mobile costs 20 credits and an email 1 credit, only when found; a lead added from the Lead Finder costs 1. Every email is verified before it is returned and labelled Valid or Risky.

3. Pick the route

Use a CSV for a one-off list, HubSpot if your dialer reads HubSpot lists, Zapier to add a mobile to each new contact, and the API for volume. Each route is explained below.

Illustration of a Scalelist call list with mobiles in E.164 format, email statuses Valid and Risky, and Export CSV and Push to CRM buttons
Illustration of a Scalelist list: the missing mobile cost nothing, and both buttons lead to a dialer.

4. Map the fields

Point the Scalelist mobile at the phone field your dialer dials first, and carry the name, company and title so the rep sees who answered.

5. Dial and log

Start the session in your dialer. Outcomes log to the CRM when the list came from the CRM; calls from a Nooks CSV list, for example, stay in Nooks.

Route 1: export a CSV and import it into your dialer

A CSV is the one route every dialer here accepts. Export the list from Scalelist, then upload it where your dialer takes call lists. Each dialer reads the file its own way.

Dialer CSV import rules for Aircall, Orum, Nooks, Kixie, PhoneBurner and JustCall: phone column, number format and maximum rows per file
Put the mobile first, name the column “Mobile Phone”, and use E.164: that one file satisfies all six.

Use the same column names every time so each dialer’s mapping step recognizes them:

Scalelist field Header to use What the dialer does with it
Phone (the mobile) Mobile Phone The number it dials
First name, Last name First Name, Last Name Shown when the call connects
Company, Website Company Name, Website Account context on screen
Job title Job Title Opener and routing
Email Email Address Match key and follow-up
City, Country City, Country Time zone and calling hours

Route 2: push to HubSpot, then dial from HubSpot

HubSpot is the best route when your dialer already reads HubSpot, because the calls log back to the same records. Scalelist’s HubSpot integration pushes selected leads with field mapping, and updates existing contacts by email instead of duplicating them.

  1. Map the mobile. In Scalelist’s field mapping, point Phone at HubSpot’s Mobile Phone Number if that is the property your dialer dials.
  2. Push the list. Choose Push to CRM on the list, then Push Selected or Push All Leads.
  3. Build a HubSpot list. Put the pushed contacts in a contact list your reps will call.
  4. Load it in the dialer. Open the list from your dialer, as below.

How each dialer loads a HubSpot list:

On Salesforce? Scalelist cannot push leads to Salesforce directly yet. Import a CSV, use Zapier or the API, then dial from Salesforce; the steps are in our guide to getting Scalelist data into Salesforce.

Describe the people you call in one sentence, reveal their mobiles, and push them to HubSpot for your dialer.

Get 20 credits to test it

Route 3: add a mobile to every new contact with Zapier

Zapier is the route for contacts that arrive every day. The Scalelist Zapier app has two actions, Email Finder and Mobile Finder, and no triggers, so the trigger comes from your CRM.

Zapier dialer integration: HubSpot New Contact in List trigger, Scalelist Mobile Finder at 20 credits if found, then HubSpot Update Contact
Every contact that lands on the call list gets a mobile when Scalelist finds one, and costs nothing when it does not.
  1. Trigger: HubSpot, New Contact in List. Point it at the list your reps call.
  2. Action: Scalelist, Mobile Finder. Pass the full name and company. It costs 20 credits when a mobile is found and nothing when it is not.
  3. Action: write the number where the dialer reads it. HubSpot’s Update Contact writes it to Mobile Phone Number. Kixie users can use Kixie’s “Add to Powerlist” action instead, and PhoneBurner users “Create Contact”.

The Zap has three steps, so it needs a paid Zapier plan: the Free plan runs two-step Zaps only. Professional starts at 19.99 USD a month billed yearly, for 750 tasks.

Route 4: send lists through the Scalelist API

The API route suits scheduled jobs and backfills, such as adding mobiles to every open contact before a calling week. Send up to 100 people per request to the bulk phone endpoint, with your key in the X-Api-Key header.

POST https://api.scalelist.com/api/v1/phone/bulk {"requests": [{"full_name": "Dana Whitfield", "company_domain": "northwindfab.com",   "custom": {"crm_id": "0031"}}], "webhook_url": "https://example.com/scalelist"} 

Scalelist answers at once with a task ID, then posts the results to your webhook, echoing each custom object so every mobile maps back to the right record. An Idempotency-Key header makes a retry within 24 hours replay the original task with no extra credit. Endpoints and errors are in the Scalelist API docs.

What it costs

Every route uses the same Scalelist credits: 20 per mobile found, 1 per email or lead found, and 0 for a miss. Moving the list to your dialer costs no extra credits.

For example, 250 mobiles use 5,000 credits, which is the Scaler 5K plan at 199 USD a month, or about 0.80 USD per mobile. The prospects Scalelist finds no mobile for cost nothing. Plans run from 29 USD to 649 USD a month; see Scalelist plans and credits.

Troubleshooting a dialer import

Most failed imports come from five problems: number format, duplicates, Do Not Call numbers, an empty phone field, and calls that do not log.

Numbers are rejected or dial the wrong country

Use E.164: a plus sign, the country code, then the number with no spaces or punctuation, such as +16145550142. Aircall rejects anything else, and Nooks recommends it.

E.164 format for a dialer CSV import: +16145550142 works, while numbers without a country code, a stripped plus sign or an extension break
Check the phone column after every resave: spreadsheet apps drop the leading plus sign without warning.

Spreadsheet apps often drop the leading plus sign when you open and resave a CSV. Check the phone column before you upload, or format it as text. PhoneBurner does not dial extensions automatically, so keep extensions out of the mobile column.

The same person appears twice

Each dialer deduplicates differently. Aircall rejects duplicate numbers; JustCall keeps only the first contact per phone number. PhoneBurner asks at import whether to import, skip or merge duplicates, and warns that contacts imported by hand before connecting HubSpot can end up duplicated. Scalelist’s own HubSpot push updates a contact when the email matches.

Do Not Call numbers are on the list

Do the Do Not Call screening in the dialer, where it can block the call. PhoneBurner scrubs against DNC.com in real time, through a separate DNC.com subscription. Kixie sells a DNC Algorithm add-on on its Professional plan that blocks or warns before a call. Orum and Nooks let you add a prospect or number to a Do Not Call list from a call outcome.

The FTC exempts most sales calls to businesses from its Do Not Call rules, but protection follows personal numbers, so a buyer’s personal mobile is a grey area. This is not legal advice; see our guide to B2B cold calling laws.

The mobile is missing in the dialer

The field mapping sent it to a property the dialer does not read. Check which HubSpot phone property your dialer dials first, remap Scalelist’s Phone field to it, and push again. In Kixie, tick the Phone box on custom phone properties when you import CRM properties.

Calls do not show up in the CRM

The list came from a file, not from the CRM. Nooks says CSV calls “will not log back to HubSpot” and suggests uploading the CSV to the CRM first. Load the list through HubSpot when you need the call history on the record.

For the dialers themselves, see our power dialer comparison, the guide to how parallel dialers work, and the best cold calling software. Every Scalelist connector is on the integrations page, and the calling playbook is in the complete guide to cold calling.

Build a call list with direct mobiles and load it into the dialer you already use.

Describe your buyer in one sentence

FAQ

Does Scalelist integrate with Aircall, Orum, Nooks or Kixie?

Not directly. Scalelist has no native dialer integration today. You load its mobiles into these dialers with a CSV export, by pushing leads to HubSpot and dialing the HubSpot list, with the Zapier Mobile Finder action, or through the REST API. Each mobile costs 20 credits when Scalelist finds it and nothing when it does not.

What is the best dialer integration route for a small team?

A CSV for a one-off list, or the HubSpot push if your dialer reads HubSpot. The CSV route needs no setup: export, then upload to your dialer’s import screen. The HubSpot route needs a one-time setup, and every call then logs to the same HubSpot record your reps already use.

What phone format do dialers need?

E.164: a plus sign, the country code and the number with no spaces, such as +16145550142. Aircall’s Power Dialer requires it and JustCall’s CSV template asks for it. Nooks recommends it, Orum asks for the country code, and Kixie standardizes any format on upload. Scalelist shows mobiles in this format.

Can I send Scalelist mobiles to Salesforce and dial from there?

Yes, but not through a native push, which exists only for HubSpot. Import a Scalelist CSV into Salesforce, use a Zap with the Scalelist Mobile Finder action, or call the REST API, then dial from Salesforce in a dialer such as Orum, Nooks or PhoneBurner that reads Salesforce records.

Does moving leads to my dialer use credits?

No. Credits pay for what Scalelist finds: 20 per mobile, 1 per email, 1 per lead added from the Lead Finder, and 0 when nothing is found. Exporting a CSV or pushing leads to HubSpot adds no credit cost. Zapier tasks and your dialer’s own seats are billed by those tools.

Who scrubs Do Not Call numbers: Scalelist or the dialer?

The dialer. Scalelist returns contact data; the dialer decides what gets called. PhoneBurner scrubs through a DNC.com subscription, Kixie sells a DNC Algorithm add-on, and Orum and Nooks keep Do Not Call lists fed by call outcomes. Rules for business calls differ by country; this is not legal advice.

Sources