Territory Prospecting: Company Headquarters and Contact Location Are Different Filters

Company headquarters and a contact’s working location answer different territory questions. Choose the company field when the rule concerns where the account is headquartered; choose person-level evidence when it concerns where the intended contact works. If the decision depends on a regional buying operation, identify that operation separately. Do not copy headquarters into the person’s location simply to make a filter complete.

Start by writing the territory rule in plain language, then identify the record, field, source, and owner that support it. The workflow below is a proposed method for selecting and reviewing records. It does not claim that a location label establishes purchasing authority, that every employee works at headquarters, or that an unknown location can safely be inferred from a telephone number.

Which location determines the territory decision?

Separate account eligibility, contact relevance, and internal ownership. An account can belong in a market segment while a particular employee works elsewhere. A contact can work in a target region while buying decisions remain centralized. Your company’s territory policy decides which relationship matters; the data supplies evidence for applying that policy.

Before searching, record whether the rule uses headquarters, an operating office, the relevant legal entity, the person’s current working location, or a combination. Name who can resolve an exception. If the policy only says “accounts in territory,” ask the territory owner to define that phrase before translating it into an automated selection rule.

Keep these meanings visible in the list definition. A column called “Location” is insufficient when one reviewer reads it as headquarters and another reads it as the employee’s office. The problem is not solved by making both columns use the same label.

Resolve the account and buying operation first

Confirm which company record represents the intended relationship. A parent group, subsidiary, operating brand, and regional team may share names without sharing the same purchase process. Use the parent-and-subsidiary targeting guide when the company hierarchy changes which entity belongs in the outreach.

Retain the account identifier and the evidence connecting it to the relevant operation. Do not move a person between company records merely to satisfy a geographic condition. If the relationship is disputed, keep the association unresolved until the owner can establish the correct account.

Unify’s company and contact data supports finding accounts and people in one workflow. That does not turn account-level information into person-level proof. Treat the returned field according to its documented meaning and available source context, rather than inferring a stronger claim from the presence of a value.

Check the field source before applying a location filter

The filter builder documentation says available fields depend on the record type, connected data, and feature where the builder is used. Inspect the object and source shown in the picker. A Unify company attribute and a similarly named property on its connected CRM account can contain different values.

For each geographic condition, record the actual attribute, its object, and what its value represents. Check whether it is a country, region, city, free-text location, or another supported type. Use only the operators available for that field. Do not promise a specific working-location filter when the connected data exposes only company geography.

Open the stored record through record inspection when a result is unexpected. Inspect its stable ID and current attribute value. A record-level last-updated timestamp does not show that the location itself was checked then; preserve the separate source or verification evidence when it is available.

Build account and person conditions separately

The audience documentation distinguishes company conditions from people conditions and provides previews for both. Define the intended accounts under Companies, then narrow the relevant contacts under People. Review each result set before treating the combined audience as a calling or sending list.

If the territory rule concerns account headquarters, keep that condition on the account source you have validated. If it also requires contacts working within a specified region, add a separate person-level condition supported by the available data. Do not use the account condition twice and assume it has established both facts.

Check whether every condition must match or whether alternatives are allowed. A broad “or” can admit records that satisfy only one part of a combined rule. Preserve required account criteria outside a group of person alternatives when that matches your policy. Read the entire expression after changing a group; a plausible preview count does not prove the logic is correct.

Make related conditions apply to the same person

When filtering companies through their associated people, place the relevant person conditions together in the same relationship group. Unify documents that conditions inside one relationship group apply to the same related record. Separate relationship groups can match different records at the same company.

This matters when the intended contact must satisfy both a role requirement and a location requirement. The selection should establish that the person you plan to contact meets both, rather than establishing independently that the company has someone in the role and someone in the region. Inspect the actual matched contact, not just the company’s inclusion.

Use the target-account contact workflow to review the resulting people and their contact details. Enrichment can supply additional information, but a successful lookup should not substitute for checking the identity and relationship that the territory rule requires.

Treat company segments as shared account definitions

Unify’s segments documentation describes reusable company criteria, including location and supported CRM attributes. A company can match multiple segments. Selecting several segments in a company filter matches companies in any of them; additional conditions narrow the results.

A segment therefore provides a shared account definition, not automatic evidence about every associated person. Record which segment version or saved criteria you reviewed. If your intended person criteria differ from the shared account rule, keep the distinction explicit instead of changing the shared segment to accommodate one list.

Changes to a segment apply wherever it is used, including engagement policies. Review those dependencies before saving a revision. An apparently local geography correction can change which accounts a team may work. Use a separate reviewed audience variation when the objective is a narrower selection rather than a workspace-wide territory change.

Research the contact’s working location without overstating it

Use evidence that refers to the person and the relevant employment relationship. Retain the source, what it actually says, and when it was observed. A current professional profile, an appropriate company source, or information supplied in the business relationship can support a review, but the reviewer must assess whether it establishes the specific working-location claim.

A phone country code, language preference, headquarters address, or company website domain is not sufficient by itself. A city on a profile can also be ambiguous about residence, office, or responsibility. Do not quietly relabel it as a verified work location when the source does not make that distinction.

The research-agent documentation supports focused questions about a company or person, with guidance and review of supporting research. Match the research question to the correct record type. Ask for evidence about the location relationship you need, and keep a missing or contradictory answer unresolved rather than forcing a qualifying result.

Represent remote, multiple, and unknown locations honestly

Remote work does not mean “located at headquarters,” and multiple offices do not establish which office a contact uses. Preserve a remote designation or multiple supported locations when the source provides them. Do not replace that information with one convenient city merely because a downstream field expects a single value.

Define how the territory policy handles these states before automation. The available choices may include human review, routing to a named account owner, or excluding the record from this particular selection until the needed evidence exists. These are proposed operating decisions, not asserted Unify status labels.

If dedicated review attributes are useful, the custom attribute guide explains how to create appropriately typed fields. Keep observed location, evidence status, and the resulting territory decision separate. A reviewer’s decision is a policy outcome; it should not overwrite the original factual field.

Verify relevance and ownership after geographic selection

Being located in a region does not make someone responsible for the problem you solve. Use the buying-committee workflow to distinguish the operational owner, evaluator, and other participants. Keep a geographic match separate from a judgment about purchasing responsibility.

Review the account’s actual owner and effective restrictions before taking action. Engagement policies separate claiming from engagement and can use company criteria to define the accounts a team may work. A record appearing in a search result does not, by itself, establish that the current user can claim or engage it.

For ambiguous allocations, send the record to the responsible territory owner with the competing evidence and proposed decision. Do not resolve the conflict by changing the location field or assigning yourself the account. Preserve the decision rationale so another rep can understand why a geography match did or did not lead to outreach.

Check mappings and changes before releasing the list

A CRM location field can disagree with provider data because they describe different concepts or update through different paths. Review the source of truth for the field. The HubSpot field-mapping guide illustrates why read and write behavior must be inspected separately; a field being readable does not establish that it will be overwritten or reconciled.

Use the account-data maintenance workflow to review missing or conflicting values without discarding provenance. Correct an unsupported association at its source where appropriate, then inspect the value that the audience actually evaluates. A correction in one screen is not proof that a dependent preview already reflects it.

Audiences change as records meet or stop meeting their conditions. Keep the reviewed snapshot distinct from later membership. Before using an audience in a play or enrolling its people, inspect the current matches and exclusions again. If the criteria change, review the dependent actions rather than assuming that a prior approval covers the new population.

Use a blank territory review record

Keep the review compact enough to follow from policy to selected person. Fill the fields below from inspected evidence. This is a blank working template, not a completed evaluation or a claim that a particular list has passed.

• Territory basis: [policy owner, rule, effective scope, exception route].
• Account: [stable ID, company relationship, headquarters or operating-unit evidence].
• Contact: [stable ID, current employer, role, working-location evidence or unknown].
• Selection: [company conditions, person conditions, relationship grouping, field sources].
• Eligibility: [current owner, effective restrictions, unresolved conflict].
• Review: [snapshot time, inspected records, decision, reviewer, next check].

As a proposed acceptance review, inspect records that should qualify, records that should not, and records with missing or conflicting location evidence. Check the intended person and account relationship for each. Do not turn an unreviewed record into a pass because the total result count looks reasonable.

Release the list only for the decision the evidence supports. A reviewed territory selection tells the team which accounts and people fit the chosen rule. It does not establish a prospect’s interest, authorize a different owner to contact them, or determine their local calling window.

Frequently asked questions

Can I use company headquarters as every contact’s location?

No. Headquarters describes the company. Use separate person-level evidence when the rule depends on where a contact works.

Can a company belong to several Unify segments?

Yes. The documentation says companies belong to every segment whose criteria they match. Segment membership does not itself resolve an ownership conflict.

Why should role and location share a related-person group?

Conditions in one relationship group apply to the same related person. Separate groups can match different people at the company.

What should I do when working location is unknown?

Preserve the unknown state and follow the territory policy’s review route. Do not infer a location from headquarters, language, or a phone country code alone.

Does a territory match establish buying authority?

No. Geographic eligibility, account ownership, and responsibility for the buying decision require separate evidence.