Who do I reach out to, and when? Today the answer is a hunt. Auto-Sourced ICP Contacts answers both from the signal you already have.
Website de-anonymization tells you the account is in market. It does not always tell you the person. The gap between "the account is warm" and "here is who to email" is where intent goes to die.
An account is clearly in market, the rep opens it, and the Contacts tab is empty. So they go digging through LinkedIn, or the signal just dies on the vine.
Sourcing fires only when an account goes Warm or Hot and Abmatic AI has the company but has not de-anonymized a contact on it. Quiet accounts stay quiet.
Decision makers only, matched to the ICP you define at both account level and contact level, in the prioritized persona order you set.
Nothing runs until an account earns it. This is a triggered sourcing motion attached to accounts that are already showing intent, not a bulk list pull.
An account crosses into Warm or Hot. Abmatic AI has the company but has not de-anonymized a contact on it, so the Contacts tab is empty.
Abmatic AI matches decision makers against the account-level and contact-level ICP you defined, in your persona priority order. Tech-stack signals are read as part of account fit, and an account running a rival product counts as a strong signal.
A qualifying account produces 2 to 3 good contact matches, with work email and LinkedIn on every contact and a phone number on 88%.
The contacts drop into the Auto-Sourced ICP Contacts group, carry Source = Abmatic AI and Sub Source = auto_source, and arrive in Slack, your CRM on the normal sync, and in the app.
Every sourced contact arrives with a work email and a LinkedIn profile. A phone number comes with 88% of them.
On every sourced contact. Nothing to fill in afterwards and no waterfall tool to run on the side.
On every sourced contact, so a rep can read the person before the first touch.
On 88% of sourced contacts. We publish that number rather than rounding it to every.
A qualifying account produces 2 to 3 good contact matches, not a scraped list of everyone carrying a title.
Matched to the ICP you define at account level and contact level, in the priority order you set for your personas.
Every sourced contact lands in a group called Auto-Sourced ICP Contacts, ready to target, exclude, or report on.
That distinction is not a footnote. It decides what your sequence copy is allowed to say, so we put it on the record itself.
A customer raised this before their rollout. They run outbound sequences whose copy says "you visited our site", and a sourced contact has not personally visited anything. They are a matched decision maker at an account that showed intent, which is a different motion and deserves different words.
So every auto-sourced contact carries its own provenance. Nothing else in Abmatic AI writes that value, which makes it a clean filter: exclude auto-sourced contacts from personally-visited messaging, route them into their own sequence, or report on them separately. The choice stays yours because the data tells you which is which.
These behave exactly like any other contact Abmatic AI reveals. No new inbox, no export step, no separate tab to remember.
Sourced contacts appear in Slack alerts the same way every other contact Abmatic AI reveals does.
They flow into your CRM on the normal sync. The Sub Source value maps to a CRM property through the HubSpot integration Sub Source field mapping.
They sit on the account in Abmatic AI, inside the Auto-Sourced ICP Contacts group, and behave like any other contact from there on.
You supply the account-level and contact-level ICP definitions in priority order. Abmatic AI runs the rest on its own from there.
Forward looking by design. Auto-Sourced ICP Contacts runs on accounts that heat up from turn-on onwards. It deliberately does not backfill a big batch across your existing accounts, so what lands in your CRM stays tied to a live signal. Abmatic AI starts at $36,000 per year.
A de-anonymization vendor for the account signal, a contact-data vendor for the people, an enrichment or waterfall tool to fill the gaps, and an ops person or a workflow tool to join all of it on a trigger. Four bills, four support queues, and a join that someone owns.
Abmatic AI does the signal, the sourcing, the ICP match, the grouping, the CRM write, and the alert first-party. Plenty of tools can source a contact. The difference is that this is one system on one trigger with one provenance flag, not four tools wired together.
Abmatic AI already de-anonymizes website visitors at account and contact level, scores accounts, and runs campaigns. Auto-Sourced ICP Contacts closes the last gap in that loop: when the score says Warm or Hot and the contact record is empty, the platform fills it itself instead of handing the rep a dead end. One platform, one identity graph, no second vendor and no manual LinkedIn hunt in between.
Auto-Sourced ICP Contacts is an Abmatic AI capability that sources the real ICP decision makers at your Warm and Hot accounts, every day, with no work from your side. It fires only when an account goes Warm or Hot and Abmatic AI has the company but has not de-anonymized a contact on it, then matches decision makers to the ICP you defined and delivers them to Slack, your CRM, and the app.
Only when the account goes Warm or Hot and Abmatic AI has the company but has not de-anonymized a contact on it. It is signal-triggered, not a bulk list pull, so accounts that are not showing intent are left alone.
No. The account showed intent. The person is a decision maker matched to your ICP at that account, and they have not personally visited your site. This matters for sequence copy, which is why every auto-sourced contact carries a provenance flag you can filter on.
A work email address on every contact and a LinkedIn profile on every contact, plus a phone number on 88% of them. A qualifying account typically produces 2 to 3 good contact matches. Abmatic AI does not publish an email-accuracy percentage.
On the contact record, Source is set to Abmatic AI and Sub Source is set to auto_source, displayed in the grid as Auto Source. Nothing else writes that value, so it is a clean filter. It also maps to a CRM property through the HubSpot integration Sub Source field mapping, and every sourced contact lands in a group called Auto-Sourced ICP Contacts.
Yes, and that is exactly why the flag exists. A customer running sequences whose copy references a site visit asked for it before rollout. Filter on Sub Source = auto_source, or on the Auto-Sourced ICP Contacts group, to exclude these contacts from personally-visited messaging and treat them as the different motion they are.
Decision makers only, matched to the ICP the customer defines at both account level and contact level, in a prioritized persona order the customer sets. Tech-stack signals are read as part of account fit, and an account running a rival product counts as a strong signal.
In Slack alerts, in your CRM on the normal sync, and in the Abmatic AI app on the account. They behave exactly like any other contact Abmatic AI reveals.
No. It is forward-looking only. It runs on accounts that heat up from turn-on onwards and deliberately does not backfill a big batch across accounts you already have.
Once, about five minutes. You supply the account-level and contact-level ICP definitions in priority order, and Abmatic AI runs it from there with no ongoing work.
Not in general. It is a triggered, ICP-matched sourcing motion attached to accounts that are already showing intent, rather than a general-purpose contact database you query whenever you like.
Abmatic AI starts at $36,000 per year. No separate price is published for Auto-Sourced ICP Contacts. Book a demo and we will walk through the trigger and what lands on a contact record.
Book a demo and we will walk through the trigger, your ICP and persona order, and exactly what lands on a contact record.