ABM Hub - Generate contacts in bulk for the committee of several accounts
Generate contacts searches for the people missing per role in the accounts you choose and adds them to the committee map with the suggested role. It uses only one source per run: Apollo or Lusha (it must be connected in Integrations). Only people are searched: email and phone are revealed only if yo
# ABM Hub - Generate contacts in bulk
📘 What it is
Generate contacts searches for the people missing per role in the accounts you choose and adds them to the committee map with the suggested role. It uses only one source per run: Apollo or Lusha (it must be connected in Integrations). Only people are searched: email and phone are revealed only if you turn on Enrich new contacts.
Generate contacts does not enroll anyone in campaigns or charge contact prospecting. Anyone who is already a contact of the account is not duplicated or given a new role.
📍 Where to find it
- Intelligence > ABM Hub > Target Accounts > select one or more accounts > Generate contacts button.
- Also from an account record (committee map / coverage).
Up to a maximum number of accounts are processed per run; if you exceed it, the dialog tells you ("Maximum N accounts per run. Remove some to continue."). Accounts that are not yours are skipped.
🛠️ How to do it
- Select the accounts and click Generate contacts. The title shows how many accounts will be processed.
- Choose the Source: Apollo or Lusha. If it says "(not connected)", connect it first in Integrations.
- Check the Roles to search. Per role and account, up to the chosen maximum is searched (by default, the one shown on screen), counting people who already hold that role. Only the roles that each account's ICP level expects are searched.
- Review the Titles for each role. They are proposed from the product's prospecting playbook or, if the playbook has none, from the Intelligence Engine Buyer Personas. You can type them by hand or use Suggest titles with AI (it shows the cost; you are charged only if the AI finishes successfully; without credits, AI is off).
- Optional: turn on Enrich new contacts (runs the email and phone enrichment cascade; it uses provider credits).
- Click Generate. You will see the progress ("X of Y accounts · N new contacts"). You can close the window: when you return you can Resume what is pending. Stop keeps what has already been created.
- When it finishes you will see a table with Account, New per role, Already existed, Not found, Status (Done, Partial, No results, Skipped, Error, Pending).
❓ Frequently asked questions
Does it cost Lymera credits? The generation does not charge contact prospecting. Suggest titles with AI can cost credits (shown beforehand), and enrichment uses credits from your data provider.
Why does an account show as "Skipped"? It can be "not yours", "nothing to search" (it already has the expected roles covered) or "stopped".
Will I get a notice when it finishes? Yes, there is a "«Generate contacts» finished" notice (also if it stopped because the source ran out of credits). Configure how to receive it in My profile > Notifications.
What happens if I close the window? The generation continues and you can resume what is pending when you return. If you have an unfinished one, the dialog shows "You have an unfinished generation." with Resume.
Do the new contacts enter a campaign? No. They are added to the account and to the map; enrolling them is a separate step.
🔧 If something doesn't work
- "The source ran out of credits; what was pending was skipped." Your provider (Apollo or Lusha) used up its credits. Top them up with the provider and run the pending accounts again.
- "Not found" results. The titles may be too specific; try other titles or the other source.
- I can't choose a source. It is not connected: connect it in Integrations (your Account Admin can do it).
- "Error" status or "The generation could not be completed." Try again with fewer accounts. If it persists, escalate with: company, user, accounts involved, source used, URL, time, steps and a screenshot of the results table.