A caller already has a HubSpot contact record because they downloaded a guide. The receptionist treats them as an existing customer and discusses an account workflow they have never purchased.
Record existence, caller identity, and customer status are different facts. Resolve the relationship required by the requested action instead of using “found in CRM” as a shortcut.
Define what returning means for this workflow
A person can return to the website, call again about an enquiry, hold an open deal, or be an active customer. Each relationship may require a different route.
| Relationship evidence | What it establishes |
|---|---|
| Existing contact | The CRM knows a record, subject to matching |
| Previous call | An interaction occurred |
| Active appointment | A scheduling relationship exists |
| Verified active account | The relevant customer process recognises the relationship |
Avoid interpreting an AI-generated note as authoritative billing or account status.
Match identity without exposing unrelated history
Use the approved combination of references and contact evidence. A shared or recycled number can lead to several plausible records.
When ambiguity remains, collect a new enquiry for review rather than revealing existing customer details to help the caller choose an identity. The shared-line guide covers this situation.
Route according to the caller's purpose
A known customer may be asking about a new service. A new lead may need only general information. Do not force all returning people into support or every new contact into a sales sequence.
For a fictional maintenance business, ask what the person needs, verify the relevant relationship, and select the approved workflow. Keep any proposed identity or relationship uncertainty in structured state.
HubSpot's contact documentation describes the record interface. The business must still define which evidence constitutes a customer for its operations.
Test the overlapping categories
Use fictional records for a guide subscriber, former customer, active customer, repeated enquiry, and a shared family number. Include one caller with both an open sales discussion and an existing service account.
Inspect routing, CRM associations, outgoing messages, and any private information disclosed. The goal is an appropriate next action, not automatically reducing every caller to a binary label.
A simple staff-reviewed distinction can be suitable for a pilot when the underlying account data is incomplete. More elaborate classification is useful only when its evidence is maintained.
New-versus-returning questions
Does a contact record prove someone is a customer?
No. Verify the relevant business relationship separately.
Should returning callers always skip verification?
No. Apply the policy appropriate to their requested information or action.
What should an engineer request?
Request the relationship definitions and several ambiguous examples before building routing.