How Do You Stop Existing Customers Landing in Your SDR Queue?

How do you stop existing customers from landing in your SDR queue?

Check every demo request against your customer list before routing it. In HubSpot, that means associating the new contact with its company by email domain, then using a workflow branch that looks at the associated company's lifecycle stage. If the company is already a customer, route the request to the account owner instead of an SDR.

This is a routing gap worth checking in any B2B CRM. A customer's new hire fills in the demo form because it was the first button they saw. The request lands in the SDR queue, the SDR sends a discovery email meant for a stranger, and the customer's team wonders why their vendor does not know them.

It is a small problem with an outsized cost. It wastes SDR time, confuses the customer, and often hides a real expansion opportunity. The fix takes an afternoon in HubSpot, and this tutorial walks through it step by step.

What do you need before you start?

You need a HubSpot account with workflows, a demo form whose submissions create contacts in HubSpot, and permission to edit workflows. HubSpot's documentation says adding branches requires Edit permissions for workflows or Super Admin permissions, and publishing requires Publish permissions for workflows. You also need a clean definition of who counts as a customer.

The form can be a HubSpot form embedded on Webflow, or a Webflow form connected to HubSpot. Either works, as long as each submission creates or updates a contact and records the form submission. If you have not connected the two yet, do that first and test it with your own email.

The definition matters most. In most setups I use the company's lifecycle stage set to Customer. Some teams use a custom property such as a contract status from billing. Pick one property, write it down, and make sure it is accurate on every current customer company before you build anything on top of it.

Step 1: How do you make sure new contacts attach to the right company?

Turn on HubSpot's automatic company association. HubSpot's knowledge base places it under Settings, then Data Management, then Objects, then Companies, in the Automation section, as "Create and associate companies with contacts." It matches the domain in a contact's email to the Company domain name on a company record.

HubSpot's example is a contact with the email sandra@example.com being linked to the company whose Company domain name is example.com. That match is the foundation of this whole build. If the association does not happen, the branch later has nothing to check.

Read the edge cases before you rely on it. HubSpot's docs say a company record is created for each unique domain, including subdomains, so example.com and info.example.com become two companies. They also say that if several companies share the same domain, contacts are associated with only one of them, and you cannot choose which. Clean those duplicates first.

One more caution from HubSpot's own docs: if you use the HubSpot and Salesforce integration, HubSpot does not recommend enabling this setting, because it can result in duplicate company records. If that is your stack, do the matching in Salesforce or with a different method instead.

Step 2: How do you handle customers with more than one domain?

Make sure every domain a customer uses points to the right company record. HubSpot's documentation on managing the company domain name property explains how to handle companies with more than one domain, so check it against your setup. Regional domains, acquired brands, and old company names are the usual cases to look for.

Go through your customer list and look for anyone who has rebranded, been acquired, or operates under a regional domain. Those are exactly the people who will slip past the check and land in the SDR queue. A short review of this list prevents many of the misroutes you would otherwise see.

This is also a good time to look at how you match leads to accounts more generally. My piece on how to match new leads to existing accounts in HubSpot covers the wider version of this problem, including prospects who are not customers yet.

Step 3: How do you build the workflow trigger?

Create a contact-based workflow that enrolls contacts when they submit your demo form. Add a short delay as the first action, so the company association has time to complete before the workflow checks it. Then add the branch. Keep this workflow separate from your general lead routing so it is easy to read and test.

The delay is a precaution I add to any workflow that depends on an association created at the same moment as the contact. It costs a few minutes of response time and removes a whole class of "it worked when I tested it" failures. For a demo request, a few minutes is fine.

Name the workflow plainly, something like "Demo request: existing customer check." Whoever maintains your CRM after you should know what it does from the name alone.

Step 4: How do you set up the customer branch?

Add an if/then branch. In the branch filter, click "+ Add filter," open the "Filtering on" dropdown, and in the Associated object section select Company. Then choose your customer property, such as lifecycle stage is Customer. Contacts whose associated company matches go down this branch.

Those menu steps come straight from HubSpot's knowledge base. It also explains that the filter is based on "Any" associated company by default, which means the contact moves down the branch when any of its associated companies meet the criteria. For this use case, that default is what you want.

HubSpot's branch documentation adds two details worth knowing. An AND/OR branch can have up to 20 branches, and a record that does not meet any branch criteria follows the None met path. That None met path is where all your non-customers go, so it is the hand-off point to your normal routing.

Step 5: What should happen to an existing customer's request?

On the customer branch, set the contact owner to the company owner or the account's customer success manager, notify that person directly, and keep the contact out of SDR sequences. Optionally create a task with a short note: existing customer, new contact, requested a demo. That note turns a misroute into an expansion conversation.

The note matters more than it looks. A demo request from a new person at a customer account often means a new team is interested, or a new project is starting. That is expansion revenue, and it deserves a quick, informed reply from someone who already knows the account.

On the None met path, either continue into your standard routing in the same workflow or let a separate routing workflow pick the contact up. If you route by territory, my tutorial on round robin lead routing by territory in HubSpot shows that half of the build.

Step 6: What about customers who use a personal email?

Expect some to slip through. HubSpot's docs say that for freemail addresses such as gmail.com, it checks the contact's Website URL property to find a matching company, and if there is no Website URL, no association happens. Those contacts will follow the None met path, so your normal routing needs its own check.

The simplest extra step is a company name field on the demo form. Your SDR can then spot a familiar customer name before replying. Some teams also block personal email domains on demo forms altogether. I covered the trade-offs in how to block email domains on all HubSpot forms.

Do not try to make the automation catch every case. A clear rule for the common case, and a person who glances at the rest, is more reliable than a complex branch that breaks the first time a customer behaves differently.

Step 7: How do you test it before you turn it on?

Create three test contacts: one with a customer's domain, one with a prospect's domain, and one with a personal email. Submit the demo form as each, then check which branch each followed, who became the owner, and which notifications fired. Turn the workflow on only after all three behave as expected.

Use real customer domains carefully. Create the test contacts with an obvious test name, check the result, and delete them afterwards so they do not pollute reports or trigger customer-facing emails.

After launch, look at the workflow history weekly for the first month. You are watching for customers who went down the None met path. Each one is a missing domain or a stale lifecycle stage, and fixing it improves the check for everyone after them.

What should you do next?

Confirm your customer definition, turn on automatic company association if your stack allows it, map every customer domain, and build the branch with a short delay in front of it. Test with three contacts. Then route existing customers to the people who already know them, and treat each request as a possible expansion.

This is a small piece of GTM engineering, but it changes how your company feels to customers. Nobody likes being treated as a stranger by a vendor they already pay.

If you want help building this, or reviewing the rest of your HubSpot routing, let's chat. I build websites and the automations behind them for lead generation, and routing is where I usually start.