How to call 200 past leads and qualify them

This page may contain affiliate links from which Blur Studio earns commissions.

An old lead list is a real asset sitting idle, not dead weight, but working through 200 of them by hand takes a day or more of someone's time, which is exactly why they usually stay untouched while newer leads get the attention. Automating the outreach is reasonable here; doing it carelessly on outbound calls is where this goes wrong.

Check your outbound calling rules first, before anything else

Outbound calling law varies by country and by list: consent requirements, do-not-call registries, and time-of-day restrictions all apply regardless of whether a human or an AI agent makes the call. This isn't optional groundwork, it's the first step, and it's worth confirming against your own jurisdiction's current rules before building anything, since the consequences of getting it wrong fall on the business making the calls. For Dubai real estate lists, see cold calling rules and tools for UAE brokers.

Your options once the compliance check is clear

• An SDR team or outsourced calling service: handles nuance and objections well, but costs real money per hour or per call, which adds up fast across 200 contacts.
• A dialer: speeds up a human caller's workflow but still needs a person on every call.
• An AI outbound voice agent: can call through a list and ask a short, consistent set of qualifying questions, flagging anyone who answers "yes, interested" for a real follow-up, at a cost that's usually a small fraction of a human SDR's time for the same volume.

Where an AI agent fits

ElevenLabs' agent platform connects an agent to phone numbers through Twilio or a verified caller ID, and can place outbound calls to a list. A purchased Twilio number supports both inbound and outbound calling through the agent; a verified caller ID (reusing a number you already own) supports outbound calls only. Pro is $99 a month with roughly 1,238 minutes of agent conversation included, Scale is $299 with about 3,738 minutes, and Business is $990 with about 12,375 minutes; usage past your included minutes runs close to $0.08 a minute, with the language model billed separately. See ElevenLabs' current plans before sizing a tier to your list. The connection steps are in connecting a Twilio number to an AI voice agent.

A worked example makes the sizing concrete. Say you're a roofing contractor sitting on 200 estimate requests from the last six months that never got a callback. If each call averages 90 seconds (a 10-second intro, a couple of questions, and a quick wrap-up for the roughly 60% that pick up or you catch live), that's about 300 minutes of actual conversation time to work the whole list once, plus whatever you spend on the voicemail path for the rest. That fits comfortably inside Pro's included minutes with room to spare, meaning the marginal cost of calling through 200 leads is close to zero beyond the subscription you're already paying for other agent work. Compare that to an SDR at, say, $25 an hour: working 200 calls at 90 seconds each plus notes and dialing time realistically takes a full day, call it $200 in wages for one pass through the list. The AI agent doesn't replace a skilled closer, but for the specific job of re-opening 200 cold contacts and sorting who's worth a real callback, the economics are lopsided in its favor.

Detecting voicemail automatically, instead of guessing

Most calls to a stale lead list hit voicemail, which means a chunk of your batch is wasted if the agent can't tell the difference between a live person picking up and a recorded greeting playing. Per ElevenLabs' own changelog, Twilio's answering machine detection is integrated into the outbound calling setup, meaning the system can flag whether a call connected to a person or a voicemail system before the agent launches into its script. Use this rather than relying on the agent to recognize a voicemail greeting mid-sentence and guess whether to keep talking; have the call flow branch cleanly, a short, pre-written voicemail message for one path, the live qualifying script for the other, rather than one script trying to handle both.

Pacing a batch of 200 calls

Don't fire all 200 calls at once even if your plan's concurrency limit technically allows a large number in parallel. A sudden burst of outbound calls from one number in a short window is also a pattern carriers and spam-detection systems watch for, and a number that gets flagged loses effectiveness on every call afterward, not just the ones in that burst. A more realistic pace is a steady trickle across a working day or two, say 20 to 40 calls an hour, which also gives you time to spot-check early transcripts and catch a script problem before it's run against the whole list. Treat the first 10 to 20 calls of any new batch as a live test, not just the ones you reviewed before launch, since a list's real responses sometimes surface issues your own test calls didn't.

Time of day matters as much as pace. Calling a residential lead list at 8am or after 7pm local time invites complaints and, in some jurisdictions, is itself a compliance problem separate from consent. Mid-morning and mid-afternoon on weekdays tend to get the best pickup rates for most consumer lists, and B2B lists generally do better avoiding the first and last hour of the business day, when people are either just arriving or already trying to leave. If your 200 leads span multiple time zones, segment the batch by zone rather than firing on your own local clock, since a 2pm call from your office can land at 11am or 5pm for the person receiving it.

Step by step

1. Confirm consent and do-not-call status for your list before calling anyone on it.
2. Write a short, specific script in ElevenLabs' agent builder: a brief intro, 2 to 3 qualifying questions, and a clear next step for anyone who says yes.
3. Test the script yourself with a handful of real calls, listening for anywhere it sounds robotic or confused by an unexpected answer.
4. Run a small batch first, 10 to 20 calls, and review the transcripts before scaling to the full list.
5. Route every "yes, interested" response to a real person immediately, not into a queue that sits for days.

Practical tips

• A short script outperforms a clever one. People hang up fast on outbound calls that don't get to the point. Two or three direct qualifying questions work better than an attempt to build rapport first.
• Plan for voicemail, since most calls to an old list hit it. Decide explicitly whether the agent leaves a message, and if so, keep it short and give a clear way to call back. Varying the message is covered in not leaving the same voicemail every time.
• Watch your concurrency limit if you want this done quickly. How many calls your agent can run at the exact same moment depends on which ElevenLabs plan you're on, from a handful on lower tiers up to around 30 on Scale and Business. Calling 200 leads one at a time versus many in parallel changes how long the whole batch takes.

A recent outage worth planning around

ElevenLabs had a roughly 90-minute incident in late September 2026 that caused agent conversation failures and speech-to-text errors across its platform. For a one-off reminder call, that's a minor inconvenience you'd simply retry later. For a 200-call outbound batch, it means a chunk of your list could fail mid-run for reasons that have nothing to do with your script or your data. Build your batch process so it logs which numbers were actually reached versus which failed to connect, and plan to re-run the failed ones rather than treating a partial batch as complete.

Common mistakes that waste a good list

• Calling the whole list on day one with no dedupe pass. Old lead lists accumulate duplicates, people who already converted elsewhere, and numbers that have changed hands. Run the list against your CRM first and strip anyone already in an active conversation, already a customer, or marked do-not-contact, before the agent touches a single call.
• Writing a script that assumes the lead remembers the original inquiry. Six months is a long time. Open by reminding them specifically what they asked about and when, not a generic "following up on your interest," which reads as a cold call to someone who's forgotten they ever reached out.
• Letting "yes" sit in a transcript instead of routing it immediately. The whole value of this exercise collapses if a qualified lead waits three days for a callback because nobody was watching the call log. Wire the "interested" outcome straight into a notification or a CRM task the moment it happens.
• Treating every "no" the same way. A flat no, a "call back in three months," and a "I bought elsewhere" are three different outcomes that call for three different next steps (remove, snooze, or move to a win-back list), not one bucket.

What I'd tell someone sitting on an old list

The math usually favors trying this: a stale lead list converting even a small percentage back into real conversations is often worth more than the cost of calling through it. What I'd push back on is skipping the compliance check because the list is "just old leads, not cold outreach." The rules that apply to outbound calling don't care how the contact originated; they care about consent and the current do-not-call status of the number you're calling. Get that right first, then let the agent do the repetitive part. Screening leads before a person picks them up is covered in qualifying a lead before it reaches your team.

How I'd approach this

Setting up the agent and script is something you can do on ElevenLabs' own dashboard. Where I usually get pulled in is connecting the "yes, interested" outcome directly into a CRM so a qualified lead lands on a salesperson's desk within minutes instead of sitting in a call log, and building the list-management side so leads that were already contacted, or that opted out, never get called again by mistake.