--- title: "Clay Phone Enrichment: Waterfall Order and Real Cost" description: "Clay phone enrichment, step by step: provider order by region from Clay's 9,806-number test, cost per mobile found, columns to clean, push to a dialer." url: https://skipcall.io/en/blog/clay-phone-number-waterfall language: en last_updated: 2026-11-06 --- [Ask Claude about this article](https://claude.ai/new?q=I'm%20reading%20%22Clay%20Phone%20Enrichment%3A%20Which%20Providers%20to%20Waterfall%2C%20What%20Each%20Number%20Costs%2C%20and%20How%20to%20Send%20the%20List%20to%20a%20Dialer%22%20\(https%3A%2F%2Fskipcall.io%2Fen%2Fblog%2Fclay-phone-number-waterfall\).%20Read%20the%20article%2C%20then%20answer%20my%20questions%20about%20it.) [Ask ChatGPT about this article](https://chatgpt.com/?q=I'm%20reading%20%22Clay%20Phone%20Enrichment%3A%20Which%20Providers%20to%20Waterfall%2C%20What%20Each%20Number%20Costs%2C%20and%20How%20to%20Send%20the%20List%20to%20a%20Dialer%22%20\(https%3A%2F%2Fskipcall.io%2Fen%2Fblog%2Fclay-phone-number-waterfall\).%20Read%20the%20article%2C%20then%20answer%20my%20questions%20about%20it.) LinkedIn X [Back to blog](https://skipcall.io/en/blog) Clay Published 6 November 2026 # Clay Phone Enrichment: Which Providers to Waterfall, What Each Number Costs, and How to Send the List to a Dialer A phone waterfall in Clay is only as good as its order, its cost per number found and what happens after the last column. Here is the provider order by region from Clay's own 9,806-number test, the real cost per mobile with Clay credits or your own API keys, the columns to clean, and how to push the result into a dialer. Clay makes it easy to chain phone providers: add a column, pick a provider, add another one behind it, and let the table fill. What it does not decide for you is the order of those columns, how much each mobile really costs once the cascade has run, and what happens to the list after the last column. Those three choices decide whether your reps spend the afternoon talking to buyers or listening to voicemail greetings. This guide uses the mobile phone test Clay published on May 3, 2026, the prices we checked on November 6, 2026, and the public API of a dialer to walk through each step. ## The phone waterfall in five lines If you are new to the idea, our [comparison of waterfall enrichment tools](https://skipcall.io/en/blog/best-waterfall-enrichment-tools) explains it in detail. In short, applied to phone numbers: 1. 01 #### You start from people you already chose: a first name, a last name, a company domain and ideally a LinkedIn URL. 2. 02 #### The first provider looks for a mobile: if it finds one, the row is done. 3. 03 #### The rows still empty go to the next provider: and so on down the list of columns. 4. 04 #### You only pay for results: Clay does not charge data credits for a lookup that returns nothing. 5. 05 #### The last column is quality control: format, number type and source, before anyone dials. The whole game is in steps 2 and 3: which provider comes first, and which ones follow. Clay’s interface lets you build the cascade in a few minutes. Getting the order right takes data. ## What Clay’s 9,806-number test actually measured Clay ran the test with TitanX, a company that scores phone numbers. Clay published the results on its blog on May 3, 2026, with the methodology on Clay University. The setup is worth understanding before you reuse the conclusions, because it explains both their strength and their limits. 6,000+ B2B contacts enriched across North America, EMEA and APAC 9,806 mobile numbers returned by the 10 providers tested 23% of those numbers rated P1 or Good: verified, and likely to be answered The ten providers were Forager, Bytemine, Wiza, Datagma, Leadmagic, RocketReach, People Data Labs, ContactOut, Findymail and Prospeo. Clay kept only unique pairs of a number and a full name, then had the numbers scored. In North America and EMEA, TitanX used manual cold calls plus eleven other signals over four days and sorted each number into four grades. In APAC, an offshore team called each number at least five times until it reached a clear outcome. P1 **Verified and likely to answer.** Clay’s methodology says a P1 number connects you with the intended person at least 25% of the time. P2 **Verified, less likely to answer.** Around 4 to 10% of calls reach the intended person. P3 **Unverified, rarely answered.** A connection rate usually under 1%. NA **Needs attention.** Inactive, disconnected or belonging to someone else: 0% connection. Each provider then got a quality score per region, where a P2 counts for half a P1, a P3 for a quarter, and a bad number counts against the provider. That last rule matters: a provider that returns many wrong numbers is penalized, not just ignored. ## The provider order by region Clay published its recommended waterfall for each region as images, so the table below is our reading of the figures Clay published in text: coverage leaders, accuracy leader and budget picks. “Coverage” means the number of mobiles returned in the test; “quality” means the score described above. | Region | First column: accuracy | Then: coverage | Last column: budget | What Clay’s figures say | | - | - | - | - | - | | North America | Forager | ContactOut, Findymail, RocketReach | Bytemine | ContactOut returned 1,679 mobiles, Findymail 1,620, RocketReach 1,600; Forager scored 46%; Bytemine about 5 cents per P1 or P2 number | | EMEA | Forager | Prospeo, Datagma | Leadmagic | Prospeo returned 881 mobiles, Forager 813, Datagma 730; Forager scored 38%, Prospeo 30%; Leadmagic about 22 cents per good number | | APAC | Forager | ContactOut, Datagma | Leadmagic | ContactOut returned 713 mobiles, Datagma 491, Forager 437; Forager scored 59%; Leadmagic about 18 cents per good number | ContactOut deserves a note of its own: it returned 2,878 mobiles across the three regions, close to half of the 6,000 contacts, the largest volume in the test. Clay also describes it as one of the pricier options. In a waterfall, that makes it a strong second column in North America and APAC rather than the first one. Clay also writes that Prospeo had strong APAC coverage but could not be included in the APAC scoring. Treat Prospeo as unmeasured in APAC rather than weak. > The first column of a phone waterfall is not the cheapest provider. It is the one you trust most to be right. ## The providers in the test, one by one The prices below are the entry prices Clay listed in its article, next to what we checked on the vendors’ own pages on November 6, 2026 when we had it. They are what you pay with your own account; inside Clay, you pay in Clay data credits instead, unless you connect your own key. ### Forager - **In the test** : Best quality score in all regions: 46% NAMER, 38% EMEA, 59% APAC, on 970 verified numbers - **Entry price (Clay's article)** : $675 a month for 1,000 data credits, extra 100 credits for $67.50 - **Best place in a waterfall** : First column, everywhere - **Watch out** : The most expensive per lookup: keep it on the contacts that matter ### ContactOut - **In the test** : Most mobiles worldwide (2,878), first in NAMER and APAC coverage - **Entry price (Clay's article)** : Free plan, paid plans from $49 a month - **Best place in a waterfall** : Second column in NAMER and APAC - **Watch out** : Clay calls it one of the pricier options at volume ### Prospeo - **In the test** : Most mobiles in EMEA (881), quality 30% EMEA and 26% NAMER - **Entry price** : $39 a month for 1,000 credits, 10 credits per mobile (Clay's article and our check) - **Best place in a waterfall** : Second column in EMEA - **Watch out** : Not scored in APAC ### Datagma - **In the test** : Third in EMEA (730 mobiles), second in APAC (491) - **Entry price** : $49 a month for 3,000 credits, 30 credits per mobile (checked November 6, 2026) - **Best place in a waterfall** : Volume column in EMEA and APAC - **Watch out** : One mobile costs as much as 30 emails ### Leadmagic - **In the test** : Cheapest per good number in EMEA (about 22 cents) and APAC (about 18 cents) - **Entry price** : $99 a month for 5,000 credits, 5 credits per valid mobile (checked November 6, 2026) - **Best place in a waterfall** : Last column in EMEA and APAC - **Watch out** : Clay's article lists a different plan size ($99.99 for 10,000 credits): check the current page ### Bytemine - **In the test** : Cheapest per good number in North America, about 5 cents per P1 or P2 number - **Entry price (Clay's article)** : Free trial, Pro plans from $1,000 a month for 120,000 credits - **Best place in a waterfall** : Last column in North America - **Watch out** : Focused on North America Findymail and RocketReach are North American volume players in the test (1,620 and 1,600 mobiles), Wiza and People Data Labs are also strongest in North America. Clay lists Findymail from $49 a month for 1,000 credits, RocketReach from $108 a month for email and phone, Wiza from $83 a month and People Data Labs from $98 a month for 350 records. For the full price grid of the providers you are more likely to run outside Clay (Lusha, Apollo, Kaspr, Cognism, FullEnrich and others), see our [phone enrichment pricing tool](https://skipcall.io/en/tools/phone-enrichment-pricing). ## What a number really costs in a Clay waterfall There are two ways to pay for each column, and they change the math. #### Clay data credits - **One invoice:** every provider is billed in Clay data credits, no contract to sign with each vendor. - **No result, no charge:** Clay’s documentation says a lookup that returns no data is not charged. - **Fast to test:** you can try a provider on 50 rows without opening an account with it. #### Your own API keys - **Lower unit price at volume:** you pay the provider’s own rate, often lower than the credit equivalent. - **One contract per provider:** minimums, renewals and unused credits to manage separately. - **Their billing rules, not Clay’s:** check whether each provider charges for an empty lookup. On the Clay side, the numbers we checked on November 6, 2026: phone enrichment starts on the Launch plan, which Clay’s FAQ lists at $185 a month for 2,500 data credits while its pricing page also shows $167 with 3,000 data credits; that puts a data credit at roughly 6 to 7 cents. Clay’s documentation puts a fully enriched record at 6 to 20 data credits depending on the provider, so roughly $0.45 to $1.50 per record with a phone. Unused credits can accumulate up to twice the monthly amount. The free plan does not include phone enrichment. On the direct side, here is the cost of one mobile found on the entry plans we checked, as recorded in our pricing tool: | Provider (own account) | Entry plan checked November 6, 2026 | Credits per mobile | Cost per mobile found | | - | - | - | - | | Leadmagic | $99 a month, 5,000 credits | 5 | about $0.10 | | Prospeo | $39 a month, 1,000 credits | 10 | about $0.39 | | Datagma | $49 a month, 3,000 credits | 30 | about $0.49 | | FullEnrich (itself a waterfall) | $29 for 500 credits | 10 | about $0.58 | The last line of that calculation is the one that matters. A column that is cheap per lookup but returns many wrong numbers lowers the price on the invoice and raises the price per conversation. That is exactly why Clay’s test scores providers on quality, and why the first column should be the most accurate one. To turn your own figures into a cost per conversation and per meeting, use the [phone enrichment pricing tool](https://skipcall.io/en/tools/phone-enrichment-pricing): it takes a match rate, a share of wrong numbers and a pickup rate by number type. 6 to 20 data credits for a fully enriched record in Clay, per Clay's documentation $0.10 to $0.58 cost per mobile found on the entry plans of four providers, own account 23% of returned numbers rated verified and likely to answer in Clay's test ## Before you export: the columns to normalize A Clay table after a waterfall usually holds one phone column per provider, in as many formats as there are providers. A dialer needs one clean number per contact, and your reps need to know what kind of number it is. Add these columns before anything leaves Clay. 1. 01 #### One final number, in E.164: a single column that takes the first non-empty provider column and writes it as +\[country code]\[number], with no spaces, dots or leading zero. Dialers and APIs expect this format, and it removes the “01 23” versus “+33 1 23” duplicates. 2. 02 #### The number type: mobile, direct line or switchboard. Some providers label it, most do not. A number shared by several contacts at the same company is a switchboard, whatever the label says. 3. 03 #### The source: the name of the provider that found the number. You need it to compare providers on your own results, and in Europe to tell the person where you got their number. 4. 04 #### The enrichment date: numbers decay. A date column tells you when a list needs a refresh. 5. 05 #### A do-not-call flag: a column for contacts who must not be called, filled from your CRM, your suppression list and the national registers that apply. If you prefer to clean outside Clay, export the table and run it through our free tools: the [phone number validator](https://skipcall.io/en/tools/phone-number-validator) for E.164 format and invalid numbers, the [direct dial checker](https://skipcall.io/en/tools/direct-dial-checker) to sort mobiles, direct lines and switchboards, and the [CSV cleaner](https://skipcall.io/en/tools/csv-cleaner) for broken files from Excel. If your numbers come from several exports rather than one Clay table, the [waterfall enrichment merger](https://skipcall.io/en/tools/waterfall-enrichment-merger) joins them, keeps the best number per contact and shows what each provider really added. ## Sending the list from Clay to a dialer Two routes, depending on how often you run the table. A **CSV export.** Export the table, keep only the clean columns, import the file into the dialer. Simple, no setup, and the right choice for a weekly list. The risk is human: someone exports the wrong view or forgets the do-not-call column. B **HTTP API column.** Add an HTTP API enrichment at the end of the table, method POST, the dialer’s endpoint as URL, the row’s fields in a JSON body and your API key in an Authorization header. Each row is sent on its own as soon as it is ready. The right choice for a table that fills every day. Clay’s HTTP API column shows the response status in each cell, so a failed row is visible and can be re-run. Integration guides written for Clay add two practical warnings: requests can be retried, so the receiving system should cope with duplicates, and a shared secret in the Authorization header is the usual way to authenticate, since Clay does not sign requests by itself. ### Example with Skipcall’s public API Skipcall’s public API is documented at [docs.skipcall.app](https://docs.skipcall.app). Two endpoints are enough for a Clay table, as documented on November 6, 2026: 1. 01 #### Create the contact: `POST https://api-public.skipcall.app/v1/contacts` with a Bearer API key. Required fields: `firstName`, `lastName` and `phoneNumbers`, a list of numbers in E.164 format. Optional fields include `email`, `company`, `country`, `role`, `linkedinUrl` and custom fields. A multi-workspace key adds an `x-workspace-id` header to choose the workspace. 2. 02 #### Add it to an existing sequence: `POST /v1/sequences/{id}/contacts` with up to 100 contact IDs per call. Contacts are assigned round-robin among the sequence’s assignees unless you name one, and contacts already in the sequence are ignored. 3. 03 #### Call from Skipcall: reps work the sequence from the power dialer or the parallel dialer. The API does not place calls; it puts the right contacts in front of the right reps. A minimal body for the first call looks like this, with Clay column names inserted where the values go: ``` { "firstName" : "Jane" , "lastName" : "Doe" , "company" : "Acme Inc." , "country" : "United States" , "role" : "VP Sales" , "phoneNumbers" : [ "+14155550123" ] } ``` API access is included on the Starter, Intermédiaire, Expert and VoIP plans, with a rate limit of 100 requests a minute (1,000 on Expert). A Clay table that sends a few hundred rows at once should therefore pace its requests or send them in batches. For other automation patterns around a phone system, see our guide to [telephony APIs and automation](https://skipcall.io/en/blog/telephony-api-automation) and the [Clay integration page](https://skipcall.io/en/integrations/clay). **Best for:** teams that refresh a Clay table every day and want new contacts to land in a calling sequence without a weekly export. ## One table, three regions: conditional columns Most teams do not call a single region. The tempting shortcut is one waterfall for everyone, ordered by a global ranking. Clay’s figures show why that wastes money: the provider that leads North American coverage is not the one that leads in EMEA, and the cheapest good number comes from Bytemine in one region and Leadmagic in the other two. A single order means some of your contacts always start with a provider that is weak where they live. The fix fits in one table. Clay lets you set a run condition on each enrichment column, so a column only runs when a formula is true. Normalize the country first, in a column that holds a region code (NAMER, EMEA or APAC), then give each provider column a condition on that code and on the final phone column still being empty. NA **North America rows.** Forager, then ContactOut, then Findymail or RocketReach, then Bytemine on what is left. EU **EMEA rows.** Forager, then Prospeo, then Datagma, then Leadmagic on what is left. AP **APAC rows.** Forager, then ContactOut, then Datagma, then Leadmagic on what is left. Two more conditions save credits. The first is a **seniority or account filter** on the expensive columns: keep Forager for the accounts and roles you would call by hand, and let the volume providers handle the long tail. The second is a **stop rule**: once a row holds a mobile, no later column runs, even if a cheaper provider might return a second number. Two mobiles for the same person rarely double your chances; they mostly double the bill and confuse the rep who has to pick one. Last point on regions: Clay’s test grouped Europe, the Middle East and Africa into one score, but coverage inside that block varies a lot from one country to the next. If you call mostly Germany, France or the Nordics, look at country-level evidence before trusting an EMEA average; our [B2B phone data coverage map](https://skipcall.io/en/tools/b2b-phone-data-coverage-by-country) sorts what is published by country and by provider, and says where nothing is published. ## Mistakes that make a Clay phone waterfall expensive 1. 01 #### Putting the cheapest provider first: it fills rows with wrong numbers, and the waterfall never asks the better providers for those contacts. 2. 02 #### Using the same order for every country: Clay’s own figures show different leaders in North America, EMEA and APAC. Split the table by region, or add a condition on the country before each column. 3. 03 #### Judging providers on fill rate: a filled cell is not a working number. Call a sample and count the numbers that reach the right person. 4. 04 #### Re-enriching contacts you already have: if an Apollo or CRM export already holds a mobile, run the waterfall only on the empty rows, or you pay twice for the same person. 5. 05 #### Keeping one phone column per provider in the export: reps then call the first number they see, often a switchboard. Export one final number and its type. 6. 06 #### Forgetting the source column: without it, you cannot compare providers on your own results, and in Europe you cannot tell a prospect where their number came from. 7. 07 #### Never refreshing: people change jobs and numbers. Our [B2B data decay calculator](https://skipcall.io/en/tools/b2b-data-decay-calculator) estimates how much of a list has gone bad and when to refresh it. ## Improving Apollo phone data with Clay It is one of the questions that comes back most often in Clay’s community: “I have Apollo, can Clay make the phone numbers better?” Yes, if you treat Apollo as the first column you already paid for, not as a source to replace. 1. 01 #### Import the Apollo export into a Clay table: keep Apollo’s mobile, direct and corporate phone columns as they are. 2. 02 #### Flag the rows to complete: no mobile, or a number shared by several contacts at the same company. 3. 03 #### Run the waterfall on those rows only: with a condition on the flag, so the providers never see the contacts Apollo already covered. 4. 04 #### Merge into one final number: the Apollo mobile when there is one, otherwise the first mobile from the waterfall. The same logic works for numbers coming from your CRM, from Lusha or from any other export. If you only need to compare and merge several exports you already own, our [waterfall enrichment merger](https://skipcall.io/en/tools/waterfall-enrichment-merger) does it in the browser without a Clay table. And if you use Apollo’s own calling, our review of [Apollo’s dialer and its limits](https://skipcall.io/en/blog/apollo-dialer-limits) covers what it includes and when a dedicated dialer helps. ## Test your own waterfall in one afternoon Clay’s test is a starting point. Your market, your roles and your countries are what count. A short test tells you more than any benchmark, including Clay’s. 1. 01 #### Take 100 real prospects: the roles and countries you actually call, not only well-known executives. 2. 02 #### Run them through three providers in parallel, not in a waterfall: so each provider sees all 100 names and you can compare like for like. 3. 03 #### Call every number returned, within the same week: same time slots, same caller ID. 4. 04 #### Count per provider: numbers returned, mobiles among them, numbers that reached the right person, and the cost. 5. 05 #### Build the order from those counts: the most accurate first, the one that adds the most new good numbers second, the cheapest last. > A benchmark tells you where to start. Your own hundred calls tell you where to stop. ## The rules do not change because the number came from Clay The provider that found a number does not change what you may do with it. In the United States, manual business calls are generally allowed, but the TCPA restricts autodialed and prerecorded calls to cell phones without prior consent, and you must honor do-not-call requests. In the European Union, calling a business contact usually rests on legitimate interest under article 6 of the GDPR, and article 14 requires you to tell the person where you got their data. In the United Kingdom, screen numbers against the TPS and the CTPS before you dial. Our [cold calling compliance checker](https://skipcall.io/en/tools/cold-calling-compliance-checker) lists the rules country by country, and our guide to [cold calling cell phones](https://skipcall.io/en/blog/cold-calling-cell-phones) covers the US mobile rules in detail. This is general information, not legal advice. ## How Skipcall fits this workflow Skipcall is a business phone and outbound calling platform, not a contact database: it does not sell lists and does not build them. Your Clay table stays the place where you find numbers; Skipcall is where you call them, with a power dialer or a parallel dialer on up to four lines, call recording and transcription when recording is on, and sync with HubSpot, Pipedrive, Salesforce and Attio. Contacts arrive by CSV or through the public API described above, and Skipcall’s built-in enrichment can complete the contacts you already have, on credits. ## Clay waterfall checklist | Step | What to check | Tool | | - | - | - | | Order | Most accurate provider first for each region | Clay’s published test, then your own 100-call test | | Cost | Cost per good number, not per lookup | [Phone enrichment pricing tool](https://skipcall.io/en/tools/phone-enrichment-pricing) | | Format | One final number in E.164 | [Phone number validator](https://skipcall.io/en/tools/phone-number-validator) | | Type | Mobile, direct line or switchboard | [Direct dial checker](https://skipcall.io/en/tools/direct-dial-checker) | | Source | Provider name kept per number | A Clay formula column | | Freshness | Enrichment date and refresh plan | [B2B data decay calculator](https://skipcall.io/en/tools/b2b-data-decay-calculator) | | Delivery | CSV import or HTTP API column | [Skipcall API docs](https://docs.skipcall.app) | | Rules | Consent, do-not-call lists, calling hours | [Compliance checker](https://skipcall.io/en/tools/cold-calling-compliance-checker) | Author [Charles Baldet](https://skipcall.io/en/author/charles-baldet) [Charles Baldet on LinkedIn](https://www.linkedin.com/in/charlesbaldet/) CEO & Co-Founder, Skipcall Charles is the CEO and co-founder of Skipcall. A sales commando with over 10 years of experience in B2B SaaS and complex strategic accounts, he has closed major deals with Stellantis, SNCF, RATP and Natixis. A specialist in the PUCCKA and MEDDIC methodologies, Charles regularly teaches sales at HEC's incubator and the Sorbonne. He was ranked among Les Echos' top 10 business angels under 35 in 2020. He also co-founded Getalead (B2B sales agency) and Getlab (SalesTech studio). [See all their articles](https://skipcall.io/en/author/charles-baldet) FAQ ## Frequently asked questions **What is the best mobile phone provider in Clay?** There is no single winner. In the test Clay published on May 3, 2026 (about 6,000 contacts, 10 providers, 9,806 mobile numbers), Forager had the best quality scores in every region, ContactOut returned the most numbers worldwide, Prospeo led coverage in EMEA, and Bytemine and Leadmagic were the cheapest per good number. The best first column depends on the region you call. **How is a phone waterfall billed in Clay?** Each provider column costs Clay data credits when it returns a result, and Clay's documentation says a lookup that returns no data is not charged. A waterfall stops at the first provider that finds a number, so later columns only run on the contacts still empty. If you connect your own API key for a provider, you pay that provider directly instead of spending Clay data credits on that step. **How many Clay credits does a phone number cost?** It depends on the provider you put in the column. Clay's documentation puts a fully enriched record at 6 to 20 data credits. On the Launch plan, checked on November 6, 2026, a data credit is worth about 6 to 7 cents, so a record with a phone number lands roughly between $0.45 and $1.50. **Can Clay improve the phone numbers I got from Apollo?** Yes, and it is one of the most common uses. Import your Apollo export into a Clay table, keep the Apollo number in its own column, then run a waterfall only on the rows with no mobile or with a number that several contacts share. You avoid paying twice for the contacts Apollo already covered. **How many good numbers should I expect from a phone waterfall?** Fewer than the fill rate suggests. In Clay's own test, only 23% of the 9,806 mobile numbers returned were rated as verified numbers of people likely to answer. Count the numbers that reach the right person when you call, not the cells that are filled. **How do I send Clay contacts to a dialer?** Either export a CSV and import it into the dialer, or add an HTTP API column in Clay that sends each row to the dialer's API. With Skipcall, the public API creates a contact with a first name, a last name and at least one number in E.164 format, then can add it to an existing sequence. **Should I validate numbers before sending them to the dialer?** Yes. Put every number in E.164 format, drop the invalid ones, mark which ones are mobiles and which ones look like switchboards, and keep a column with the provider that found the number. It takes minutes and saves your reps hours of dead calls. ## A calendar full of meetings starts with a call. [Get started now](https://app.skipcall.io/signup) [Book a demo](https://skipcall.io/en/demo) **No commitment** · Number live in 2 minutes Keep reading ## Related articles [View all articles](https://skipcall.io/en/blog) 01 Sales tools ### [Best Waterfall Enrichment Tools in 2026: 7 Options Compared](https://skipcall.io/en/blog/best-waterfall-enrichment-tools) A waterfall enrichment tool can search dozens of data providers and still leave your SDRs with missing phone numbers, outdated contacts, or wasted credits. We compared seven tools on data coverage, verification, pricing, integrations, and their fit for different B2B sales workflows. 12 Oct 2026 02 Cold calling ### [Direct Dial, Mobile or Switchboard: What Each Number Type Really Connects](https://skipcall.io/en/blog/direct-dial-vs-mobile-vs-switchboard) What a direct dial, a mobile, a switchboard and a VoIP number are, how to spot each one in an Apollo, Lusha or ZoomInfo export, and the connect rates published for each type, with their sources and their limits. 6 Nov 2026 03 Software ### [Telephony APIs: Automating Your Calls and Wiring Up Your Sales Stack](https://skipcall.io/en/blog/telephony-api-automation) What a telephony API actually enables, the difference between REST and webhooks, the five automations that pay off, choosing between code and no-code, and the architecture mistakes that lose data silently. 2 Sept 2026 ## Ready to multiply your productivity? Join the sales teams that have transformed their prospecting. [Request a demo](https://skipcall.io/en/demo) Personalized demo • No commitment