Cloud-based and hosted dialer software: what to check before you buy

"Cloud dialer" is now a label on almost every calling product, from a 200-seat predictive system to a dial pad in a browser tab. The label tells you almost nothing about what you are buying. The things that change your monthly bill and your connect rate sit underneath it: where the software runs, how it bills, what it does when nobody answers, and whether texting lives in the same place as calling.

This guide is for sales and call center leads comparing hosted, web-based and "virtual" dialers. It covers deployment, uptime, setup time and cost. It also says plainly where a predictive system is still the right buy and where a lighter browser dial pad paired with SMS and local numbers does the job better. We make Ready, which includes a browser-based dialer. Its limits are spelled out below so you can rule it out quickly if it doesn't fit.

Hosted, web-based and virtual: what the words usually mean

Vendors use these terms loosely, so ask what each one means for the specific product in front of you.

• Hosted dialer. The vendor runs the dialing engine on its own servers. Reps often still install a desktop softphone or a thick client. This is common with older predictive and progressive systems that moved out of on-premise server closets.
• Web-based or browser dialer. Calls run inside the browser, usually over WebRTC, so there is nothing to install beyond a headset. Updates arrive when you reload the page.
• Virtual dialer. This is mostly a marketing term. It can mean either of the above. Ask whether anything gets installed and who maintains it.

Here is the practical test. Hand a new rep a laptop and count the steps until they can place a call. If the answer involves an IT ticket, a VPN or a client download, you are looking at a hosted system with on-premise habits.

The dialing mode matters more than the hosting

Hosting decides how you deploy. Dialing mode decides how many conversations a rep has per hour and how much legal exposure you carry. The common modes are:

For a deeper breakdown, see predictive dialer vs auto dialer. If you run cold outbound at volume with 20 or more agents, you probably want predictive or power dialing, and the call center dialer selection guide is the better starting point.

The Ready Dialer is click-to-call only. It has no queue dialing, no auto-dialing, no voicemail drop, no transfer and no barge or whisper. If those are on your must-have list, Ready isn't your dialer.

Uptime: what to ask instead of trusting a badge

Every vendor says "reliable." Ask for things you can check:

1. The SLA in writing, and what it pays out. Convert the percentage into minutes. 99.9% monthly uptime allows about 43 minutes of downtime a month. 99.5% allows about 3.6 hours. For a team that lives on the phone, that difference is real.
2. Public status page history. Look at the last 6 to 12 months of incidents and see how long each one lasted.
3. What breaks when the vendor is down versus when your network is down. Browser dialers depend on your office internet and the rep's laptop. Hosted systems with desk phones may survive a laptop crash but not a vendor outage.
4. Carrier path. Ask whether outbound calls ride registered, reputable routes. A dialer that is technically "up" but whose numbers are flagged as spam is effectively down.

That last point affects connect rates more than most uptime discussions do. Why calls from certain area codes get flagged as spam covers what local numbers do and don't change.

Setup time: count the real steps

Legacy hosted systems can take weeks. You have contracts, seat provisioning, IVR configuration, client installs and number porting. Browser dialers are usually faster, but "sign up and call" skips some steps:

• Numbers. You need local numbers bought or ported in. Porting existing numbers takes days, not minutes.
• CRM connection. A dialer that doesn't log calls to your CRM creates a second database your reps will ignore. Dialer CRM integrations covers what to test.
• Texting registration. If the dialer also texts, which most teams now want, US business texting needs A2P 10DLC registration. On Ready the charge at submit is the first month, $25. After that it is $25/mo for registration plus $2 per number. Most approvals take 2 to 7 days. An account can send up to 500 texts a month before it registers, at its normal per-text rate, so calling and light texting can start before approval.

Per-seat vs per-minute: worked math

Most hosted and cloud dialers charge per seat per month, sometimes with a minute bundle. Per-minute billing flips that model: you pay for talk time, not for licenses. Which one wins depends on how much your reps actually talk.

The Ready Dialer bills $0.025 per minute. Each started minute is billed as a full minute. There are no seat plans, and every answered minute bills at that one rate, starting with the first. Only answered time is billed. A ring-out or busy line costs nothing, while a call answered by voicemail counts as answered and bills like any connected call.

Worked example (assumptions stated):

• 5 reps, 22 working days a month
• 40 answered calls per rep per day, including voicemail pickups
• An average of 3 billed minutes per answered call, after rounding each call up
• Unanswered dials: not billed

Answered calls: 5 × 40 × 22 = 4,400 a month. Billed minutes: 4,400 × 3 = 13,200. Voice cost: 13,200 × $0.025 = $330 a month, or about $66 per rep.

Now add a follow-up text after every connect, written to fit one 160-character segment with no emoji. On Standard that is 4,400 × $0.0075 = $33 plus 4,400 × $0.0045 in carrier fees. Replies are billed the same way as sends.

To compare against a seat-based quote, multiply the seat price by 5 and add any overage. If that total is under about $66 per rep, a seat plan wins for this usage pattern. A team on the phone six hours a day will usually come out ahead on seats. A team that calls inbound leads and follow-ups for an hour or two a day usually won't. Run your own numbers from your phone system's real talk-time report instead of guessing.

Where a browser dial pad plus SMS beats a legacy predictive system

Predictive dialers were built for one job: burning through a large cold list as fast as possible. Many sales teams no longer do that job. Their leads come in from forms, ads and referrals, and the deciding factor is reaching the person quickly through the channel they will actually answer.

In that setup, a lighter stack often wins on cost and on conversations:

• Text and call from one place. An instant text when a lead lands, then a manual call from the dial pad, puts both channels in the first five minutes. Text-first or dial-first covers which one should go first, depending on the lead source.
• Local numbers for texting. With Local presence on, Ready texts from the account's number closest to the contact's area code. Every number still sits on your registered 10DLC campaign, so this doesn't bypass registration.
• Inbound and missed calls are handled. Inbound calls ring the open pad, and missed calls show up as a Missed call card in the contact's Inbox thread, so a returned call doesn't vanish into voicemail.
• Recording and transcripts. Ready records calls with consent and produces transcripts, which is useful for coaching without a separate tool.
• One inbox. Calls, texts and replies live with the contact record, along with CRM, pipeline and automations, rather than spread across three logins. GoHighLevel users get the dial pad and two-way message sync inside GHL.

The tradeoff is the one stated earlier. If a rep needs to dial 300 cold numbers an hour, a click-to-call pad will slow them down, and you should buy a power or predictive system.

Compliance questions every dialer buyer should ask

Automated dialing and texting both carry TCPA exposure. Vendors can lower the risk, but compliance is still the sender's responsibility. Ask each vendor:

• Does it scrub against DNC and known TCPA-litigator lists before you contact anyone? Ready's standalone scrub is $0.005 per contact and flags matches before send. That is cheap insurance against TCPA damages that run $500 to $1,500 per text.
• Does it enforce quiet hours based on the recipient's area? Ready holds texts outside permitted local hours and charges only when they send. Campaigns, drip campaigns and automations wait up to 24 hours for the window; a one-to-one or API text is held only if the window opens within 6 hours, otherwise it is not sent, and you send it again once the window opens; a one-to-one reply to someone who texted you in the last 24 hours goes out at any hour.
• Does STOP propagate everywhere, so an opted-out contact can't be texted from another campaign?
• How does it handle call recording consent in all-party-consent states?

Our stance is that cold contact happens by phone and mail, and SMS goes to leads who consented or replied. A dialer that blurs that line saves you nothing.

The short version

Choose dialing mode first and hosting second. If you need predictive or power dialing for large cold lists, buy a system built for that, and hold it to a written SLA you can check against its status history. If your team works inbound leads and follow-ups, a browser dial pad billed by answered minute, paired with texting from local numbers, usually costs less per conversation and is quicker to set up. Pull your real talk-time report, run the per-seat vs per-minute math above, and the answer usually becomes clear.

If the click-to-call model fits, you can create an account. Your first 20 one-to-one texts are free, so use them before you register. You can check current text rates on the pricing page.