Call Block
Your prospect book ranked by awareness so you dial the warmest first, each tagged with its buying stage.
Included with bdrcron . A seat without it sees an upsell here instead of the page.
Overview
Call Block answers the BDR's first question of the day: who do I dial first. It scores every prospect 0 to 100 for awareness, ranks the book warmest first, and tags each prospect with its buying stage from Identified to Selecting. This is the bdrcron dial-list view: the same awareness engine that powers the ranked target brief, rendered as an ordered call block you work top to bottom.
What it is for, on the page. Under the headline, this page says what it produces, what makes it run, and where the output lands. Every Work page reads that line from one registry, so the three answers cannot drift from the page.
How the awareness score works
The score is deterministic: the same prospect data always produces the same number and the same dial order, so the list is defensible and repeatable. It rises with third-party intent, website visit frequency, content and email engagement, and trigger events like a recent job change or funding round, with recent signals weighted more heavily than stale ones. A prospect with no signal is Identified, not warm, so the top of the block is where the intent actually is rather than a padded list.
The buying stage and the dial order
Each prospect carries a buying stage read off its awareness band: Identified, Aware, Interested, Considering, or Selecting. The stat tiles summarize the book, how many are warm (Interested or hotter), how many are already Selecting, and how many are still just Identified, so you can see the shape of the day before you dial. The dial order is the awareness rank, one being the first call.
Where the prospects come from
The block reads your prospects from your connected CRM and stored records. If you have not connected a CRM yet, the list is empty rather than filled with placeholders, connect your tools in Settings and your book appears here on the next sync. Call Block ranks the book and records how each call went; turning a call into a governed follow-up sequence stays with the bdrcron drafting skills.
How a CRM-synced book gets ranked. Your CRM sync brings in name, email, title and account. The five awareness inputs come from the signals the platform already holds for that person and their account: site visits, replies, meetings and calls your connected tools filed on the account, intent rows and intent scores for the contact or account, job changes and funding rounds the signal router caught, and engagement with your content. Visits, engagement and intent count from the last 30 days; job changes and funding from the last 90. A value a record already carries is kept as is. A prospect with none of this evidence still scores 0 and reads as Identified. When no prospect in the book has any signal, the footer under the list says so, and the order is your book order rather than a warmth ranking. Until 2026-11-02 a CRM-sourced book always scored 0, because these sources were not read for it.
When a load fails
If the page cannot load, every panel on it says so. Painting the failure into only one card used to leave its neighbours on "Loading…" indefinitely, which reads as still-working rather than failed.
Calling and logging an outcome
Each row shows the prospect's phone number as a link. Tap or click it and your device's phone app (or whatever handles phone links on your computer) dials it. Sales as Code does not place the call itself: no dialer integration offers a click-to-call path here yet, so the link hands the number off. A row with no number says "No phone on file" and stays in the list, so you can see who needs a number.
The number comes from your CRM sync: Phone (or Mobile) on a Salesforce contact, phone or mobilephone on a HubSpot contact, the primary phone on a Pipedrive person, and the first phone number on an Attio person. A CSV contact import reads a Phone, Mobile, Direct phone or Work phone column. Numbers already synced before 2026-11-02 fill in on the next sync of that contact.
After the call, pick an outcome in the row (Connected, Meeting booked, Voicemail, No answer, Not interested or Wrong number), add a note if you want one, and press Log. The latest outcome, when you logged it and how many calls you have logged for that prospect show in the row and stay there when you reload. Each logged outcome also goes into your activity, filed against the prospect's email, so the brain and the account's history see it alongside your other touches.
What is not shown
The design mockup sketched a full call-block runner: live-dialer tiles (dials today, connect rate, parallel lines), an active-contact prep card (timezone, a generated one-line opener, fast facts), and a call timer. Those stay out. They need a live parallel dialer (Nooks, which is partner-gated) and generated call content this page does not store or compute, so rendering them would mean inventing the numbers. Each row shows the prospect, title, company, phone, the top awareness driver behind the score, the awareness score with its buying stage, and your latest logged outcome.