The problem this solves
A calling block is measured in conversations, and every dead number costs a minute and a little morale. Numbers collected over years from business cards, forms and old enrichments come in every format - local, international, with extensions, with typos - and a meaningful share ring to nowhere. A rep who hits three disconnected lines in a row starts to distrust the whole sheet, and the block ends early.
Validation before the block is cheap and changes the day. Normalizing formats makes the dialer work; checking line type tells the rep whether a mobile, a landline or a switchboard will answer; checking connection status removes the numbers that no longer exist. What remains is shorter and every entry is worth the dial. The Lead Verification Agent runs this as a pass over the list and hands the caller a sheet made only of numbers that pass.
The dropped numbers are reported too, because a disconnected direct line often means the contact has moved, which is a signal for the enrichment playbooks rather than a dead end.
How the mission runs
- Read the numbers on list <name>. The Lead Verification Agent loads every phone field on the list - direct, mobile, main line - keeping the original values so nothing typed by a rep is lost, and detects the country from the number and the contact's location.
- Normalize the format. Each number is rewritten in international format with the correct country code, extensions separated into their own column, and obvious typos - a missing digit, a swapped area code - flagged rather than silently corrected.
- Check line type and status. Phone validation identifies whether each number is a mobile, a fixed line or a switchboard, and whether it is currently connected. Disconnected and invalid numbers are marked with the reason and removed from the calling set.
- Update the list and export the calling sheet. The normalized numbers, line types and statuses are written back onto list <name>, and Google Sheets receives only the rows with a connected number, ordered by fit score where one exists, with the line type beside each entry and the contact's timezone.
The prompt
This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.
What comes back
List <name> updated with normalized phone numbers, line types and validation status per contact, and a Google Sheet calling list containing only the connected numbers, each with its type, the contact's timezone and the fallback email. The report gives the pass rate, the count dropped by reason - disconnected, invalid, duplicate - and the contacts whose direct line failed, which the enrichment playbooks can re-find.
Make it yours
- Send the contacts whose numbers failed to the direct-dial enrichment playbook to find a replacement number in the same run.
- Keep switchboard numbers in the sheet marked as such when reps are willing to ask for the person by name.
- Write the validated numbers back to HubSpot or Pipedrive so dialers read clean data from the CRM.
- Run it monthly so the calling sheet never accumulates dead numbers.
Frequently asked questions
Does validation place a call to the number?
No. Line type and connection status come from carrier and numbering data; nothing rings on the prospect's phone during validation.
What happens to numbers with extensions?
The base number is validated and the extension is kept in its own column, so the dialer can use both and the validation reflects the line that actually connects.
How does it treat duplicates across contacts?
The same number on two contacts is flagged - often a shared main line - so the sheet does not send two reps to the same switchboard.
Is the pass rate typically high?
It depends on the age and source of the numbers; the report states the rate achieved on your list rather than promising one, and old lists tend to lose a noticeable share.