If your sales team is burning time calling numbers that go straight to voicemail — or worse, dead lines — there’s a good chance your HubSpot contact data has a phone quality problem. HLR lookup is the most reliable fix. This guide covers everything: what HLR is, how it integrates with HubSpot, workflow patterns that actually hold up in production, and how to build a phone data quality programme around it.

What Is HLR Lookup?

HLR stands for Home Location Register — the network database that tracks whether a mobile number is currently active and reachable. An HLR lookup is a live query to that database that tells you, in real time:

• Whether a number exists and is active on a mobile network
• Whether the number is currently reachable (not switched off, not out of coverage)
• The network the number is registered on
• Whether the number has been ported from another carrier

This is fundamentally different from format checking. Format checks verify that a number looks valid — correct country code, right number of digits, no illegal characters. HLR lookup verifies that the number is valid in the real world, right now.

Why HLR Lookup Matters for HubSpot Teams

HubSpot stores phone numbers for every contact, but it does almost nothing to verify them. Numbers enter your CRM from:

• Form submissions (where anyone can type anything)
• List imports (where quality varies wildly)
• Enrichment tools (which pull from databases of variable freshness)
• Manual entry (always a risk)

Over time, contacts change numbers, disconnect lines, or port to a new carrier. Without active checks, your HubSpot data degrades — and your team’s dial efficiency goes with it.

HLR lookup gives you a verified, real-time signal you can store as a HubSpot property, use as a workflow filter, and act on automatically.

The Core HLR Properties to Add to HubSpot

Before you build any workflows, create these contact properties:

Property	Type	Purpose
HLR Status	Dropdown	active, inactive, unknown
HLR Last Checked	Date	Timestamp of the most recent lookup
Network	Single-line text	Carrier returned by the lookup
Ported	Checkbox	Whether the number has been ported

These four properties give you the foundation for filtering, reporting, and workflow logic across your entire CRM.

Workflow Patterns That Work in Production

Pattern 1: Check on Form Submission

The cleanest approach is to validate at the point of entry. Set up an enrollment trigger on new contact creation where Phone number is known. The workflow calls Clean Dial, writes the result to HLR Status, and then branches:

• If HLR Status = active → continue standard lead flow
• If HLR Status = inactive → add to a nurture list, flag for ops review

This keeps bad numbers out of your active sequences from day one.

Pattern 2: Batch Backfill for Existing Records

If you have thousands of contacts with unverified phone numbers, run a batch workflow. Create an active list filtered by:

• Phone number is known
• HLR Last Checked is unknown

Enrol from this list, run the lookup, write results. This gives you a baseline quality score for your entire database.

Pattern 3: Periodic Re-Verification

Mobile numbers go inactive over time. A contact who was reachable six months ago may have changed numbers or cancelled their plan. Set up a re-check workflow that runs monthly for any contact where:

• HLR Status = active
• HLR Last Checked is more than 30 days ago

This keeps your active contacts genuinely active.

Pattern 4: Pre-Sequence Gate

Before enroling a contact in a sales sequence or calling task queue, check HLR status. If the number hasn’t been checked recently, trigger a lookup first, then conditionally enrol. This prevents your sequence tools from burning credits on dead numbers.

Common Mistakes to Avoid

Checking every number every day. HLR lookups have a cost per query. Over-checking is expensive and unnecessary. For most teams, checking on entry and re-checking monthly is more than sufficient.

Ignoring the unknown state. Not all lookups return a clean active or inactive response. Some networks don’t participate in HLR queries, or the number is on a VoIP platform that doesn’t expose status. Don’t treat unknown as active — treat it as a prompt for manual review.

Deleting contacts with inactive numbers. The right response to an inactive number is to suppress it from outreach — not to delete the contact. The contact may have other valid information (email, company, deal history) that you need.

Not logging the lookup timestamp. If you don’t record when you last checked, you can’t build re-verification logic or report on data freshness.

Reporting on Phone Data Quality

Once you’re writing HLR results to properties, you can build a simple contact dashboard in HubSpot that shows:

• Total contacts with known phone numbers
• % with HLR Status = active
• % with HLR Status = inactive
• % with no HLR check yet
• Trend over time as backfill runs

This gives your ops lead visibility into CRM health without running manual audits.

How Clean Dial Fits In

Clean Dial is a HubSpot app built specifically for this workflow. It connects directly to HubSpot’s workflow engine, handles the HLR query, and writes results back to your contact properties automatically. You don’t need to manage an external API integration or build custom middleware.

It also handles edge cases — rate limits, lookup failures, partial responses — so your workflows stay reliable even at scale.

Install Clean Dial — or learn more about how it works.