The problem
A new lead comes in from a company that is already your customer. They fill out a support form or request a product demo. HubSpot's default behavior assigns them to whoever is next in the rotation — not the rep who has spent the last year building the relationship. The new rep has no context. The customer is frustrated. The existing rep is blindsided.
This happens constantly in growing teams, and it erodes trust with your best accounts.
The solution
Add an Account Match node to your routing flow. When a new lead enters the flow, FlowRouter checks the lead's email domain against existing companies in your CRM. It excludes generic domains (gmail.com, yahoo.com, etc.) and supports fuzzy company name matching for cases where the domain does not match cleanly.
If a match is found, the flow routes the lead to the existing account owner. If no match is found, the lead continues down the standard routing path — round-robin, territory, or whatever logic you have in place.
A typical account matching flow looks like this:
Trigger (form submission) → Account Match (find existing company) → Matched: Assignment (existing owner) / Unmatched: Round Robin (new business pool)
The outcome
- Customer continuity. Leads from existing accounts always reach the rep who knows the relationship.
- No more "sorry, wrong rep" handoffs. The first interaction is with someone who has context.
- Clean fallback. Unmatched leads flow into your standard routing logic — nothing falls through the cracks.
- Domain intelligence. Generic email domains are automatically excluded so personal email addresses do not produce false matches.