Skip to content
EnrichLoops

USE CASESTERRITORY ROUTING

Company dataRevOps · Sales

Route accounts to the right sales team

A contact’s location can differ from the company’s headquarters. Enrich the account, then apply your territory and size rules to give new leads a consistent owner.

Get your free API key See the workflow

100 free credits / month. No card. No sales call.

Enriched data → your next action
Start withNew account → acme.example
EnrichLoops adds profile data
HQ country
Canada
HQ city
Toronto
Employees
240

Canada + mid-market segment → Canadian mid-market team

Illustrative data and rules. Your workflow controls the action.

WHEN TO USE IT

Revenue teams that assign accounts by company geography or segment and need consistent ownership across multiple contacts.

WHAT IT ENABLES

Give accounts a consistent owner based on your territory rules.

How the workflow works

Enrich the account, resolve the territory from headquarters and size, then assign ownership in your CRM.

  1. 01

    Start with the account

    Use the company domain and check for an existing account owner before assigning a new lead.

  2. 02

    Resolve the territory

    Map headquarters country, state or province, and employee count to your team’s territory table.

  3. 03

    Assign an owner

    Use your CRM workflow to assign the account, with a fallback queue for incomplete or conflicting data.

IMPLEMENTATION GUIDE

Choose the geography your rules use

Company headquarters describes the account, while a person’s location describes a contact. Decide which one drives your territory model. Use structured headquarters fields when available so your workflow does not have to parse a free-text address. Headquarters does not describe every office or service region.

Preserve existing ownership

Look up the normalized domain in your CRM before assigning an incoming lead. If an account already has an owner, attach the lead to that account according to your policy. Only use round-robin assignment inside the resolved territory, and keep a manual review path for ambiguous matches or missing geography.

Audit assignments

Store the territory rule, enrichment timestamps, and selected fields with each assignment. Test boundary cases for employee segments and confirm that webhook retries cannot assign a second owner. The enrichment result provides account context; your CRM owns assignment and notifications.

Connect the workflow

Use the API overview for request and task handling, or the Loop guide for webhook delivery.

Integration guidesConnect enriched account data to your CRM workflow.

Common questions

Can I route using a contact’s location?

People enrichment can provide a contact’s professional location. Choose deliberately between that location and company headquarters; they represent different places and may produce different routing decisions.

What if headquarters is missing?

Use an existing verified CRM value or send the account to a fallback queue. Do not infer a territory from an unavailable field.

All 22 use cases
RevOps / Sales

CRM enrichment

Fill account and contact records with current company and professional context in your CRM.

Sales / RevOps

Lead scoring

Score account fit with industry, headcount, and location alongside your own engagement signals.

Product / Sales

Signup qualification

Qualify new signups with company industry, size, and location while keeping the form simple.

Put this workflow to work

Start with 100 free credits every month. Test with your own data.

Get your free API key