Where I would route a lead that is already a customer

The question

New research about an existing customer should help the person who already owns the relationship. That is my starting point before I call anything a new lead.

A hiring post, a project announcement or a new leader can still be useful. The account owner may know that the work is already covered, that the buyer has discussed it or that a separate team owns the project. I want the research to reach someone who can interpret it with that context.

For Mach, I want the useful finding kept with the account and a clear person responsible for reviewing it.

The relationship can disappear between records

In an r/SalesOperations discussion about duplicate outreach[1], u/LauraStone3461855 asked how teams keep activity and replies in sync when one rep sends a LinkedIn message and another adds the same prospect to an email sequence. The post describes follow-ups continuing after a reply. It is a workflow question, rather than a documented existing-customer incident.

In a separate r/salesforce discussion[2], u/girlgonevegan pointed to a related record problem: “inbound activity cannot easily be attached to the correct lead record when duplicates exist.” This is one commenter’s assessment of duplicate records, rather than a measured result.

Those accounts point to the context I would want checked before a fresh introduction. They do not establish that either problem occurred in Mach or that a matching rule catches every existing customer.

A duplicate can make a familiar company look new. One record can contain the relationship while another carries the public finding. My concern is the decision a seller makes from that incomplete view.

Keep the clue useful to the account owner

Consider a fictional software-services firm. Its team finds a public hiring post for a data engineering manager. The post mentions a migration relevant to the firm’s work.

A colleague recognizes the company as a customer of another practice. The internal account uses a different name, so the person who found the post did not recognize it.

I would want the source and the migration passage passed to the relationship owner. The post may help prepare for a conversation. It may describe work already covered by the engagement. It may concern a separate business unit.

Each answer changes the next move. I would keep the evidence available while the owner resolves it. Discarding the finding because the company is known would lose the question; treating it as a fresh prospect would lose the relationship context.

Match the business we mean

A company match needs a definition of what the team considers an account. A parent and subsidiary may share a brand or website while having different buying teams. An acquired company can retain its old domain. A branch may have separate ownership.

I would compare the legal name, current website and location, then inspect the relationship history. A shared domain narrows the records to look at. It cannot settle every buying-team boundary.

Salesforce’s account-matching documentation[3] shows one approach using match keys and criteria including account name, website and location. Those are Salesforce’s rules, rather than a description of Mach’s implementation.

Where the identity is unclear, I would keep both sources and give the match to someone who can resolve it before outreach. The owner needs to know what was matched and what remains uncertain.

What Mach’s account-add path preserves

In the inspected Mach path, a matched customer or a company with an open deal receives the finding as a signal on its existing account. The code stores source details, records the timeline entry and returns before the separate person-and-lead branch.

It looks for a usable company domain and has a narrower name fallback when a website is missing. An ambiguous name lookup does not identify a single account, and shared non-company domains are filtered before matching. These rules have route-specific limits; they do not establish perfect identity coverage.

The notification has a narrower boundary. The code selects owners of open deals and skips the person making the addition. A customer with no open deal may therefore have no notification recipient in that query. The source review did not replay a customer interaction or verify a notification receipt.

That leaves a handoff I would want the team to define explicitly. My bar is that a useful customer finding has someone responsible for reviewing it, even when no open deal supplies that owner. The inspected path preserves evidence, but it does not by itself satisfy that ownership rule in every case.

The lead-agent instructions also tell the agent to exclude the seller’s named customers. A finding can still need an existing-account decision if the relationship changed after discovery or the finding arrives through another path. The software-services scenario above remains fictional.

Give the owner enough to decide

For the fictional hiring post, I would retain the URL, the passage about migration, its date and the company match. Then I would ask the owner to resolve four things:

Step 1: Is this the same organization? Check the domain, legal entity and parent or subsidiary relationship.

Step 2: What is the current relationship? Look at the engagement, recent conversations and any open deal.

Step 3: What does the source say? The role may describe planned work, work underway or maintenance of a completed project.

Step 4: Who should act? The owner may raise it at a meeting, ask a colleague for context or record it for later.

My read is that the value of this research depends on who can use it. For an existing customer, another introductory email may add little. A source-backed question in the hands of the relationship owner can inform the next decision. Whether it creates new work remains unknown.

Record what the owner decided

I would keep a short decision with the finding: who checked it, when and what happens next. “Already discussing this migration with the account team” gives the next seller context. So does “subsidiary is separate; research the buying team.”

That is the research handoff I want the product to support. The original source stays available, the relationship is visible and a person owns the next decision.

For a new account, start with whether the company has a reason to investigate the offer. If the clue is a job ad, use the guide to reading the hiring post before passing it on.

How this post was made: AI assisted the research and drafting. Quotes were checked against retrieved public records, and implementation details against a source snapshot dated 5 November 2026. The source review covered code and public writing; live searches and customer outcomes were outside its scope.

Who in your team should get the next useful finding about an existing customer?

Related reading

This post is part of our guide to MEDDPICC and qualifying a deal.

Related reading: Who is already talking to this buyer and They already use a competitor. What should we say.