The problem this solves
Email lists become calling lists on the day a team decides to pick up the phone, and that is when everyone discovers there are no numbers. A company switchboard is on the website; the direct line or the mobile of the person you want is in none of the places a rep has time to look. The calling block turns into a research block.
Numbers are also a different kind of data from emails. They come in types - direct office line, mobile, main line - and the type dictates how a rep uses them. The list should say which type each number is, keep the rows without a number visible so nobody assumes coverage, and hand the caller a file that contains only the rows worth dialing.
How the mission runs
- Load the contacts on list <name>. The Enrichment Agent reads each contact with their company and any existing phone fields, so numbers already on the list are kept rather than replaced.
- Find direct and mobile numbers. The phone finder searches for a direct office line and a mobile per person, recording the type of every number found and the confidence attached to it. Where only a company main line exists, it is stored as such.
- Update the list with typed numbers. Numbers and their types are written onto list <name> in separate columns, so a later mission can prefer mobiles for one use and direct lines for another.
- Export the calling CSV to Drive. A CSV containing only the rows that now have a direct or mobile number is placed in Google Drive, ordered by fit score if the list has one and by company otherwise, with the number type beside each entry.
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 direct and mobile numbers and their types for every contact where one could be found, plus a calling CSV in Google Drive limited to the rows with a number, ordered for a calling block. The report gives the coverage rate for direct lines and mobiles separately, and lists the contacts for whom only a main line was available.
Make it yours
- Validate the numbers afterwards with the phone validation playbook to drop disconnected lines before a big calling day.
- Ask for mobiles only when the campaign includes SMS.
- Write the numbers to HubSpot or Pipedrive contact records so dialers read them from the CRM.
- Add each contact's local calling window based on timezone so the CSV can be sorted by when to dial.
Frequently asked questions
What coverage should I expect?
It varies with seniority, region and industry, so the agent reports the rate it achieved rather than promising one. Senior contacts in North America and Europe tend to have the best direct-line coverage.
Are the numbers compliant to call?
The data reflects publicly available business numbers; your own calling rules and local regulations still apply, and the number type helps you apply them.
Does the calling CSV include emails?
Yes, as a fallback column, along with the contact's timezone derived from location.
Can it prioritize mobiles over desk lines?
Yes. State the preference and the calling CSV puts the mobile first where both exist, with the desk line as a secondary column.
Does it find numbers for people outside North America?
Coverage varies by country and by local rules on published business numbers; the report breaks coverage down by country so you can plan calling blocks by region.
Are numbers refreshed on later runs?
Only gaps are filled by default; ask for a re-check and numbers older than a year are validated again and replaced where a fresher one is found.