How do you stop SDRs from wasting calls on the wrong accounts
I’d build focused calling lists around the ICP, decision-maker, and next step in the account plan. Enrich those lists with recent activity, then work one group per calling block. That gives the SDR a consistent problem, talk track, and set of objections to prepare for, with fewer context switches between calls.
A useful list does two jobs: it helps you choose who to call, and it reduces how much the rep has to rethink before each conversation. Social activity, email engagement, and website visits help prioritize accounts within that list.
Why does an ICP-fit list still produce wasted calls
The company is the right size. The contact has the right title. Your rep dials.
“We’ve put that project on hold.”
“I don’t handle that anymore.”
“I asked your colleague to call next quarter.”
Those answers can look like a rep-performance problem on an activity dashboard. But a better opening won’t fix a decision made from old information.
Sales trainer Josh Braun described calling a connection at Oracle through an AI dialer, then learning the company was going through layoffs. He said he probably would have held off had he known. He wanted the tool to help him recognize when another dial wasn’t the best next move.[1]
That’s the question I’d ask before increasing volume: what should change which accounts appear in today’s calling list?
Where does the usual workflow break
The information exists, but it doesn’t always reach the calling queue.
A sales leader comments about a problem on LinkedIn. Your email platform records engagement with a campaign. A company visits relevant pages on your website. Meanwhile, an SDR keeps working through last month’s export.
Four mistakes are worth checking:
- Everyone gets the same priority. An account showing relevant activity sits beside one with no current reason to call.
- Activity gets mistaken for buying intent. An email open or website visit becomes “they’re interested” without further investigation.
- New information never changes the list. A paused project or agreed follow-up date stays in a note while outreach continues.
- Every call needs a different playbook. A rep jumps from a startup founder to an enterprise finance leader, switching the problem, script, proof points, and next step each time.
The missing step is turning those separate observations into a maintained list with a clear reason behind each call.
How do siloed call lists reduce cognitive load
By siloed lists, I mean focused groups for execution, with shared account history and ownership. Each calling block has a defined audience, problem, and objective.
On a mixed list, the SDR keeps rebuilding the conversation in their head. Who am I speaking to? What do they care about? Which opening fits? What objection should I expect? What answer or example is relevant?
Laboratory research on task switching found that alternating tasks carried a time cost, which increased with rule complexity.[3] My application to calling is straightforward: group similar conversations so the rep has fewer changes of context to manage.
Within a focused block, the same problem language, opening structure, common objections, and relevant answers stay fresh. The rep can spend more attention listening to the buyer and adapting the conversation. They still personalize each call, but they don’t have to rebuild the entire approach between dials.
Why Monday’s list should look different from Tuesday’s
Different days can serve different ICPs, decision-makers, and priorities in your account-based marketing (ABM) flow. Keep each block internally consistent.
Ex.
A sales software team splits its calling blocks by buyer and account priority:
| Preparation | Monday’s list | Tuesday’s list |
|---|---|---|
| ICP and buyer | Growing B2B SaaS companies. VPs of Sales adding outbound reps. | Larger services businesses. RevOps leaders managing an established sales stack. |
| ABM priority | Tier-one accounts with relevant recent engagement. Establish whether a new opportunity exists. | Tier-two accounts with an agreed revisit date. Reopen the conversation and check what changed. |
| Talk track | How new reps get productive and learn which accounts to call. | Where the current workflow loses time and how a change would fit existing systems. |
| Objections and preparation | “We’re still hiring.” Prepare a question about their ramp plan and a relevant example. | “We already have a tool.” Prepare questions about the current process, switching effort, and evaluation criteria. |
| Next step | A discovery conversation if a relevant problem exists. | An agreed evaluation step or an updated review date. |
The calendar is a way to batch preparation. It isn’t a reason to leave a buyer waiting. Handle replies, requested callbacks, and urgent opportunities when they arrive; group the planned outbound work into focused blocks.
Monday’s rep prepares one conversation pattern. Tuesday’s rep prepares another. That is less context switching than alternating between both on every other dial.
How can you build and enrich custom calling lists manually
Start with one ICP, one decision-maker group, and one objective in the account plan. Then add the information that helps a rep decide whether a conversation makes sense.
Ex.
Sales leaders at B2B companies with outbound teams. Use recent activity to prioritize the list.
Collect the signals your team can verify
| Signal | What to collect | How I’d use it |
|---|---|---|
| Social activity | A relevant post, comment, or discussion, with the person’s name, link, and date. | Identify people discussing a problem we can help with. A comment explaining a challenge gives me more context than a like. |
| Email engagement | Recorded opens, relevant link clicks, and replies from your email platform, tied to the campaign and date. | Build a group for review. Read replies and check the content involved before deciding on outreach. |
| Website activity | Available page, visit-date, traffic-source, and identified contact or account information. | Investigate ICP-fit accounts exploring relevant content. Keep company-level activity separate from activity attributable to a named person. |
Email opens deserve less weight. Apple’s Mail Privacy Protection can prevent senders from knowing whether a message was opened.[2] I’d look for supporting context before making an open the reason an account moves up the list.
Enrich the record before assigning the call
In your CRM or spreadsheet, add the company domain, account size, contact’s current role, verified business contact details, last conversation, and account owner. Include the ICP segment, decision-maker group, ABM tier, account stage, and next agreed action.
Beside those fields, record the signal, its source, its date, and the possible business relevance.
“Engaged” tells a rep very little. “Commented about difficulty coaching new SDRs; leads a growing outbound team” gives them something specific to investigate.
Match duplicate records by company domain and contact identity. Check account ownership and active campaigns before assigning another touchpoint.
Create separate lists with clear entry rules
Use the ICP, buyer role, and account objective to define each working list. Then use activity to prioritize within it:
- Relevant social conversations: Move contacts discussing the group’s problem into the review queue.
- Email-engaged accounts: Review campaign activity alongside previous conversations before changing priority.
- Website-active accounts: Investigate relevant visits and identify the appropriate decision-maker.
- Paused accounts: Prospects with a documented reason to hold off and a date or condition for review.
You can create these as filtered CRM views or spreadsheet tabs. Label each working list with its audience, objective, owner, and calling block. Keep the rules visible so another rep can explain why an account belongs.
Prepare one playbook for each calling block
Attach the opening, discovery questions, common objections, relevant answers, approved proof points, and desired next step. Give the SDR this brief before the session starts.
After the block, review what buyers actually said. Update the objection notes and account status before the next session. That lets the team reuse what it learned while keeping the individual account history intact.
How do you decide which accounts to call, research, or pause
Review the evidence before moving an account into the active queue.
Call when the contact is relevant and there’s a credible business reason to start a conversation.
Research when activity suggests possible relevance but you’re missing something important, such as who owns the problem or whether an account change affects the project.
Pause when the buyer requested a later conversation or confirmed circumstances make outreach poorly timed. Record the reason, owner, and review date.
A positive signal shouldn’t erase a previous agreement. An email open doesn’t override “call me next quarter.”
Correct departed contacts and respect requests to stop contact separately from temporary timing pauses.
What if you don’t want to build and maintain this manually
You can build this process with your CRM, spreadsheets, enrichment tools, and a manager who owns the weekly plan. The work is maintaining it as accounts, signals, and reps change.
For a fast-growing, venture-backed business, that is a build-versus-buy decision. Your sales and operations teams have limited time to turn new headcount into useful buyer conversations. Every week spent assembling and maintaining the workflow has an opportunity cost.
Money likes speed. If you want help getting focused lists into a repeatable calling workflow, I’d evaluate Thred.
Start with your own reviewed list or ICP-fit website leads. Thred lets reps filter website leads by traffic source, account size, social signals, and enriched data, then put matching leads into their chosen workflow. Use those controls to support the account groups your team has defined. See how Thred builds calling lists.
Configure the introduction, qualification questions, touchpoints, and handoff for each group. Thred’s voice agents handle screening, contextual voicemail, and phone trees while the rep directs qualification and chooses when to take over.
Your team still owns the account strategy, signal interpretation, and review of paused accounts. Include email engagement from your existing email platform in that review. Thred gives you a way to connect the resulting lists and context to the calling workflow.
Bring your Monday and Tuesday lists to a Thred demo. We’ll walk through the two audiences, their talk tracks, and how your reps can work each block with less preparation between calls.
Sources & notes
Written by Thred’s cofounder. The recommendations are mine. Technical references are below; Thred’s capabilities are described on our product page. These sources aren’t a benchmark of Thred’s performance.
Bring the awkward calls.
The screener. The long greeting. The phone tree.
Let’s walk through your team’s workflow.