Getting started · 2026

How to make cold calls from your computer, with nothing to install

Last updated September 3, 2026

The top results for this search are either consumer "call from your browser" apps built for the occasional international call, or dialer vendors telling you their app is the answer. Neither says what a call from a laptop actually costs, why the audio sounds thin, or why a whole team can be dialling from Chromebooks in an afternoon. This is the beginner version, with the Twilio prices it runs on, checked September 2026.

What you need

• A wired USB headset. Any $30 to $60 call-centre headset with a boom mic. Not the laptop mic, not Bluetooth earbuds; more on why below.
• Chrome or Edge. Firefox and Safari work with Twilio's SDK too, but Chrome and Edge get the least device trouble. A Chromebook is fine.
• A Twilio account with a number. Twilio is the wholesale carrier: the number is ~$1.15/month, US outbound is ~$0.014/min. The trial account cannot cold call, so you add a card at signup; see why the trial cannot dial strangers.
• A browser dialer that connects to your Twilio. DialSheet is one; free for one person. The alternative is to build one on the Voice SDK, which is a weekend if you code.
• A list. A spreadsheet with a phone column is enough; here is how to turn one into a call list.

How a browser call works, in one paragraph

Your browser already contains a real-time voice stack called WebRTC; it is what Google Meet uses. Twilio wraps it in the Voice JavaScript SDK, which the dialer page loads. When you press dial, the SDK asks for the microphone, opens an encrypted audio stream to Twilio's nearest media server, and Twilio places a normal phone call from your number to the prospect and bridges the two. That is why the bill has two lines: the phone leg at ~$0.014/min for US outbound, and the browser leg at $0.004 a minute, which Twilio charges at the same rate anywhere in the world (US Voice pricing page, checked September 2026). The browser leg is metered while your browser is connected to Twilio, so it can run a little longer than the phone leg; call it 1.8¢ per connected minute and you will not be surprised. Recording, if you turn it on, is a further $0.0025 a minute, stored in your own Twilio account.

Dialing in fifteen minutes

1. Twilio signup (5 min). twilio.com, email, verify your own mobile. Then Billing → add a card and load $20. Until you do, the account is a trial that can only call numbers you have verified.
2. Buy a number (1 min). Phone Numbers → Buy a number → pick a local area code in the territory you call, with Voice capability. ~$1.15/month. Copy the Account SID and Auth Token from the console home page.
3. Connect the dialer (2 min). Create your DialSheet account (no card), open Settings → Twilio, paste the SID and token, pick the number. DialSheet creates the TwiML app Twilio needs for browser calls; you never touch it.
4. Import the list (2 min). Upload the CSV; the phone column is the only required one, names and companies map automatically.
5. Headset and permissions (2 min). Plug in the headset before opening the dialer page. When Chrome asks for the microphone, allow. In the dialer's audio settings, choose the headset for both input and output.
6. Test call (2 min). Dial your own mobile. Check the caller ID shows your new number, talk for twenty seconds, and if recording is on, play it back and listen to yourself.
7. Dial. Start the power dialer; it advances to the next lead when you disposition the last one. Keep the first day under a hundred dials on a new number, for the reasons on the warm-up page.

Audio quality: the five things that actually matter

An r/sales thread this year asked for headset recommendations after a rep tested their own call audio by phoning their spouse and was shocked how bad it was. That test is the right one. The fixes, in order of how often they are the cause:

• Wired USB headset with a boom mic. Laptop mics pick up the room and the fan; Bluetooth adds a noticeable delay and, on most laptops, switches the headset into a low-bandwidth call profile that makes both sides sound like 1998. USB avoids both.
• No VPN, no aggressive firewall. WebRTC wants a direct UDP path to Twilio. A VPN or a corporate firewall that blocks it forces the audio through a relay (Twilio's Network Traversal service, billed by data), which adds latency and sometimes drops the call. Turn the VPN off for calls or ask IT to allow it.
• Wired internet or strong Wi-Fi. Voice needs little bandwidth but hates packet loss. A cable, or a desk near the router, beats a fast connection two rooms away.
• Microphone permission and device selection. If the address bar shows a crossed-out mic, the call connects silently. Allow it, then pick the headset explicitly; Chrome sometimes keeps the internal mic selected after you plug in.
• One app on the mic. Zoom, Meet or Teams left running in another tab will grab the microphone or fight over the device. Close them while dialling.

What it costs: browser dialer vs softphone app vs VoIP seat

Own-Twilio rows are 600 minutes at 1.8¢ (both legs) plus one ~$1.15/month number, plus $0 or $29 of software. Competitor figures are published list prices as of August and September 2026, per user, before their minutes or number fees where those are extra. The gap is not the software price; it is that the seat products charge for a phone system you do not need to cold call, and the consumer tools do not dial lists at all. The power dialer cost page runs the same comparison at team sizes.

A worked month for one rep

100 dials a day, 21 working days, 30% of dials reaching a voicemail greeting (one billed minute each), 10% reaching a person for about three minutes. That is 1,260 billed minutes a month: 630 of conversation and 630 of voicemail, from 210 connects. Twilio charges $17.64 for the phone leg, $5.04 for the browser leg and $1.15 for the number: $24 all in, with $0 to the dialer on the free plan. The minutes page explains why the voicemail line is the one every other calculator forgets.

Why "no download" matters once there are three of you

For one person it is a convenience. For a team it changes the onboarding: a new rep or an overseas contractor gets a login link and a headset in the post, and is dialling on whatever machine they have, including a Chromebook or a laptop where IT does not allow installs. There is no version to keep in sync, no extension that breaks when Chrome updates, and the manager sees every call in the same place because the dialer and the CRM are the same page. The trade-off is that you are dependent on the browser and the network at each desk, so the audio checklist above becomes the team's first-day checklist.

When is a softphone the better tool? When the job is answering and transferring, not dialling out: a reception desk, a support queue, a company directory with extensions. Those are phone-system features and RingCentral or Dialpad sell them well. For outbound, the list on the screen is the feature, and that is what a browser dialer is.

Questions people actually ask