Warmly Visitor Intelligence
What Warmly tells you
Warmly identifies anonymous website visitors by IP-to-company reverse lookup, third-party data overlays, and (where consented) contact-level deanonymization. For an MSP or B2B sales team, the practical outputs are:
- Which companies are on the site right now (or were in the recent window)
- Which identified people from those companies showed up, with title and contact info when available
- How deeply they engaged — pages viewed, time on page, return visits
That is the raw material for prioritizing outreach: warm > cold, deep engagement > a single bounce, target ICP > unrelated traffic.
Anti-triggers
- Connection, OAuth, org-scoping, or session errors — use
warmly-api-patterns.
- Anyone who is already a CRM record — Warmly reports website traffic, not
relationships; contacts, companies, and pipeline are
hubspot-contacts,
hubspot-companies, and hubspot-deals.
- Actually contacting the visitor — Warmly is read-only and sends nothing;
the outreach happens in the CRM or sequencer.
Tool selection
| Task |
Tool |
| "Who visited the site today?" |
list_warm_visitors |
| "Which companies are showing pipeline-grade engagement this week?" |
list_warm_accounts |
| "Are we about to run out of identifications?" |
get_credits_remaining |
list_warm_visitors is the right starting point when you want contact-level signal (a named person you can email/call). list_warm_accounts is right when you want to triage at the account level (which companies are worth a salesperson's time at all).
Common workflows
Triage warm accounts for the morning outreach list
list_warm_accounts to pull current account-level engagement.- Filter by ICP fit (industry, employee count, geography — fields are on every account).
- Sort by an engagement signal that matches your sales motion: returning visitors, pricing-page hits, or session duration depending on what you're optimizing for.
- For the top N accounts,
list_warm_visitors filtered to those companies to pull individual contact-level signal.
Cross-reference with CRM before reaching out
Each visitor/account in Warmly's response includes intersection flags indicating whether the company or contact already exists in your CRM. Use this to route:
- Known contact, recent activity → hand to the AE who owns it; don't re-outreach
- Known account, new contact → enrich the existing account; queue the new contact for AE review
- Net-new account, ICP-matched → SDR outbound, with the visit as the warming signal
Pair the Warmly tools with the HubSpot, ConnectWise, or Autotask plugins to do the lookups in-place.
Engagement-depth scoring
The raw payload exposes pageviews and session timing — derive a simple score (pageviews * recency_weight + session_minutes) rather than asking Claude to eyeball "high engagement." Surface only the top decile to outreach queues so SDR attention isn't diluted.
Credit-burn check before a campaign
Before launching a workflow that depends on Warmly identifications scaling up (e.g. "enrich every visitor for the next 30 days"), call get_credits_remaining and confirm the balance covers expected volume. Identifications silently stop when the credit budget is exhausted — already-identified visitors stay visible, but new ones don't appear.
What Warmly does NOT tell you
- Confirmed buyer intent. A page visit, even from a named contact, is not a qualified opportunity. Warmly is a top-of-funnel signal, not a closing one.
- Intent across other channels. Warmly only sees your site. Cross-reference with intent platforms (G2, 6sense, Bombora) for a fuller picture.
- Outbound delivery. Warmly identifies; sending is your CRM/sequencer's job. Use the HubSpot or sequencing tools to actually contact the people Warmly surfaces.
Tying it to MSP sales motions
For an MSP-specific motion, the practical combinations are:
- Audit-page interest →
list_warm_accounts filtered to visits on the security/M365/Azure audit pages → SDR sequence offering a free audit assessment.
- Pricing-page visits without an active deal → cross-reference HubSpot deals; if no open opportunity, route to the AE for outbound.
- Returning visitor from a closed-lost account → re-engagement play; the AE who lost the deal originally is best-placed to re-open.
Run these as repeatable workflows rather than one-off lookups — the value of visitor identification compounds when it consistently feeds the outreach engine.
1---2name: warmly-visitor-intelligence3description: Acting on Warmly's identified website visitors and account-level engagement: choosing between list_warm_visitors, list_warm_accounts, and get_credits_remaining; ICP filtering, engagement-depth scoring, CRM-intersection routing, credit-burn checks, MSP-specific outreach plays, and the limits of visitor identification as an intent signal.4---56# Warmly Visitor Intelligence78## What Warmly tells you910Warmly identifies anonymous website visitors by IP-to-company reverse lookup, third-party data overlays, and (where consented) contact-level deanonymization. For an MSP or B2B sales team, the practical outputs are:1112- **Which companies are on the site right now** (or were in the recent window)13- **Which identified people from those companies** showed up, with title and contact info when available14- **How deeply they engaged** — pages viewed, time on page, return visits1516That is the raw material for prioritizing outreach: warm > cold, deep engagement > a single bounce, target ICP > unrelated traffic.1718## Anti-triggers1920- **Connection, OAuth, org-scoping, or session errors** — use21 `warmly-api-patterns`.22- **Anyone who is already a CRM record** — Warmly reports website traffic, not23 relationships; contacts, companies, and pipeline are `hubspot-contacts`,24 `hubspot-companies`, and `hubspot-deals`.25- **Actually contacting the visitor** — Warmly is read-only and sends nothing;26 the outreach happens in the CRM or sequencer.2728## Tool selection2930| Task | Tool |31|---|---|32| "Who visited the site today?" | `list_warm_visitors` |33| "Which companies are showing pipeline-grade engagement this week?" | `list_warm_accounts` |34| "Are we about to run out of identifications?" | `get_credits_remaining` |3536`list_warm_visitors` is the right starting point when you want contact-level signal (a named person you can email/call). `list_warm_accounts` is right when you want to triage at the account level (which companies are worth a salesperson's time at all).3738## Common workflows3940### Triage warm accounts for the morning outreach list41421. `list_warm_accounts` to pull current account-level engagement.432. Filter by ICP fit (industry, employee count, geography — fields are on every account).443. Sort by an engagement signal that matches your sales motion: returning visitors, pricing-page hits, or session duration depending on what you're optimizing for.454. For the top N accounts, `list_warm_visitors` filtered to those companies to pull individual contact-level signal.4647### Cross-reference with CRM before reaching out4849Each visitor/account in Warmly's response includes intersection flags indicating whether the company or contact already exists in your CRM. Use this to route:5051- **Known contact, recent activity** → hand to the AE who owns it; don't re-outreach52- **Known account, new contact** → enrich the existing account; queue the new contact for AE review53- **Net-new account, ICP-matched** → SDR outbound, with the visit as the warming signal5455Pair the Warmly tools with the HubSpot, ConnectWise, or Autotask plugins to do the lookups in-place.5657### Engagement-depth scoring5859The raw payload exposes pageviews and session timing — derive a simple score (`pageviews * recency_weight + session_minutes`) rather than asking Claude to eyeball "high engagement." Surface only the top decile to outreach queues so SDR attention isn't diluted.6061### Credit-burn check before a campaign6263Before launching a workflow that depends on Warmly identifications scaling up (e.g. "enrich every visitor for the next 30 days"), call `get_credits_remaining` and confirm the balance covers expected volume. Identifications silently stop when the credit budget is exhausted — already-identified visitors stay visible, but new ones don't appear.6465## What Warmly does NOT tell you6667- **Confirmed buyer intent.** A page visit, even from a named contact, is not a qualified opportunity. Warmly is a top-of-funnel signal, not a closing one.68- **Intent across other channels.** Warmly only sees your site. Cross-reference with intent platforms (G2, 6sense, Bombora) for a fuller picture.69- **Outbound delivery.** Warmly identifies; sending is your CRM/sequencer's job. Use the HubSpot or sequencing tools to actually contact the people Warmly surfaces.7071## Tying it to MSP sales motions7273For an MSP-specific motion, the practical combinations are:7475- **Audit-page interest** → `list_warm_accounts` filtered to visits on the security/M365/Azure audit pages → SDR sequence offering a free audit assessment.76- **Pricing-page visits without an active deal** → cross-reference HubSpot deals; if no open opportunity, route to the AE for outbound.77- **Returning visitor from a closed-lost account** → re-engagement play; the AE who lost the deal originally is best-placed to re-open.7879Run these as repeatable workflows rather than one-off lookups — the value of visitor identification compounds when it consistently feeds the outreach engine.
WYRE-AI