Check whether a new account is routed to the right rep
Images on this page are for illustrative purposes only. Example outputs are based on Lusha data, with personal details masked or abbreviated for privacy.
This Claude prompt validates a new account against the assigned rep’s territory rules before any outreach goes out. Lusha confirms current firmographics, checks the contact seniority, and surfaces any signal worth knowing before the first touch. Returns one of three verdicts: ROUTE CONFIRMED, RE-ROUTE, or ROUTE WITH CAVEAT — with the specific reason and correct assignment where needed.
Tools: Claude, Lusha, territory rules (pasted)
The prompt
This prompt may contain placeholders — look for [BRACKETS] and fill them in.
<context>
I want to check whether a new account that just entered our system is routed to the right rep before outreach begins. I need to confirm the account fits the rep's territory criteria, that the right contact has been identified, and that there's no reason to re-route before anyone reaches out.
The account:
- Company: [COMPANY NAME]
- How it came in: [INBOUND / OUTBOUND PROSPECTING / REFERRAL / EVENT]
- Assigned to: [REP NAME, TEAM]
- Territory rules for this rep: [ICP CRITERIA FOR THIS REP'S TERRITORY]
- Contact identified so far: [NAME AND TITLE — or "none yet"]
</context>
<task>
1. Use Lusha to pull verified firmographic data for the company:
- Current headcount and industry
- HQ location and geography
- Headcount in the function the rep sells into
- Any signals: funding, exec hire, M&A
2. Check the account against the assigned rep's territory rules:
- Does the company's industry match the rep's ICP?
- Does the headcount fall within the rep's size band?
- Is the geography correct for this rep's territory?
- If any criterion doesn't match: flag which rule is violated and which rep or team it should go to instead
3. Validate the identified contact (if any) via Lusha:
- Confirm their current title and that they're still at the company
- Is their seniority appropriate for this rep's deal motion?
- If no contact identified: return the best first contact for this rep's typical entry point
4. Return a routing verdict:
- ROUTE CONFIRMED: account fits the rep's territory, contact validated or identified
- RE-ROUTE: account doesn't fit this rep's territory — return the correct rep or team and why
- ROUTE WITH CAVEAT: fits the territory but a flag worth knowing (M&A, exec change, existing customer)
5. If ROUTE CONFIRMED: return verified contact details and one signal worth leading with.
If RE-ROUTE: return the specific territory rule violated and the correct assignment.
</task>
<constraints>
- Check against the actual territory rules provided, not general ICP.
- If the company is an existing customer, flag it immediately.
- RE-ROUTE is a clean and useful output. A misrouted account worked by the wrong rep is harder to fix than routing correctly upfront.
- If no territory rules are provided, flag that routing can't be verified without them.
</constraints>What you'll get back
Three examples — one per verdict type.
Example A: ROUTE CONFIRMED
Account: Halcyon Ventures — assigned to mid-market AE, J.R. Territory rules: SaaS or FinTech, 150–500 employees, North America, selling into Sales and RevOps
Lusha firmographics: 310 employees · SaaS · Austin, TX · Sales team: 42 reps
Verdict: ROUTE CONFIRMED
Halcyon Ventures fits J.R.’s territory on all criteria. SaaS ✓ · 310 employees (within 150–500 band) ✓ · North America ✓
Contact identified: No contact submitted. Lusha returns J.K., Chief Revenue Officer — 18 days in role.
- Verified email: j.k@[halcyon].com ✓ · Mobile available
- Seniority: Decision-maker — correct entry point for J.R.’s deal motion
Signal worth leading with: New CRO 18 days in role — audit window open. Lead with the exec hire, not the company size.
Example B: RE-ROUTE
Account: Brightfield Co — assigned to SMB AE, D.P. Territory rules for D.P.: All industries, 50–150 employees, North America
Lusha firmographics: 420 employees · SaaS · San Francisco · Series B
Verdict: RE-ROUTE
Brightfield Co fails D.P.’s territory on headcount. 420 employees is above the 150-employee ceiling for the SMB segment.
Territory rule violated: Company size — 420 employees exceeds SMB ceiling of 150. Correct assignment: Mid-market AE team (150–600 employees). Assign to J.R. or the next available mid-market rep.
Note: Brightfield also has a live Series B signal and 28% headcount growth in the sales team — this is a strong mid-market lead. Don’t let it sit in D.P.’s queue.
Example C: ROUTE WITH CAVEAT
Account: Cartway Technologies — assigned to mid-market AE, S.K. Territory rules: SaaS or FinTech, 150–600 employees, North America
Lusha firmographics: Acquired as target entity 9 weeks ago · Previously 380 employees · Integration ongoing
Verdict: ROUTE WITH CAVEAT
Cartway fits S.K.’s territory criteria on industry and geography. However Lusha detects an active acquisition — Cartway is the acquired party. Contracts at acquired entities are frequently frozen or re-routed during integration.
Caveat: Do not send a standard outbound sequence. S.K. should open with a direct question about whether the acquisition affects vendor decisions before pitching. If procurement is frozen, park the account and monitor for integration completion.
All data validated via Lusha connector, May 19. Details masked for privacy.
Why use Lusha in Claude
Routing errors compound. An account worked by the wrong rep for two weeks before someone notices isn’t just two weeks wasted — it’s a relationship started by the wrong person, a first impression set in the wrong context, and sometimes a deal that’s harder to recover when it moves to the right rep. Lusha in Claude checks the current verified firmographics against the rep’s actual territory rules in 90 seconds. The RE-ROUTE output is the one that saves the most time — catching a 420-employee account in an SMB rep’s queue before they make the first call is worth significantly more than 90 seconds.
Data drawn from 300M+ verified contacts under GDPR, CCPA, SOC 2, ISO 27701, ISO 31700, and TRUSTe.
FAQ
Can I run this for batches of new accounts?
Run it per account for the routing verdict — the territory rule check needs to be specific to one rep’s criteria. For batch validation across a full territory, the flag misrouted accounts in your territory prompt is the right tool.
What if territory rules aren't written down anywhere?
That’s the prerequisite. The routing check works only if you can define the territory rules clearly. If they’re informal (“J.R. takes the bigger deals”), document them before running this — even rough criteria (size band, industry, geography) are enough for the prompt to work.
What does ROUTE WITH CAVEAT mean in practice?
It means route the account to the assigned rep but brief them before outreach. The caveat is something Lusha surfaced — an acquisition, an exec change, an existing customer flag — that changes how the rep should approach the first touch. It’s not a re-route, it’s a heads-up.
How is this different from the territory coverage gaps prompt?
The territory coverage gaps prompt scans a full territory to find all accounts that are misrouted, unassigned, or have grown out of their tier. This prompt checks one specific account at the moment it enters the system. Use this one as a real-time routing gate, the territory gaps prompt as a quarterly audit.
Ready to build this?
Get started with Lusha and set up this play in minutes.
