Automated Lusha Territory Contact Routing
When a rep finds a strong contact through Lusha for an account outside their own territory, WebRun logs the handoff with the contact's role and company, holds an intro call slot on the correct territory owner's Google Calendar, and texts the new owner on WhatsApp with the contact details, so a good find never sits with the wrong rep.
How do I route a Lusha contact to the right territory owner?
When a rep finds a strong contact through Lusha for an account outside their territory, WebRun logs the handoff and holds a tentative intro call slot on the correct owner's Google Calendar. It texts the new owner on WhatsApp with the contact's details, so a good find gets routed to the rep who actually owns that territory instead of sitting idle.
- Good contacts reach the right owner instead of sitting with the wrong rep
- A tentative call slot is already held by the time the new owner is notified
- Territory rules are respected automatically on every handoff
Built for field sales teams · enterprise sales · sales operations · territory managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
dashboard.lusha.comin a real browser with your saved login - no setup, no API keys. -
1
Lusha - flag a contact for a different territory owner
lusha.com
WebRun opens Lusha to flag a contact for a different territory owner. - Open Lusha and review contacts found by reps recently
- Check whether the contact's company falls outside the finding rep's territory
- Note the correct territory owner for each flagged contact
Done when Every out of territory contact find has been matched to its correct owner.
-
2
Google Calendar - hold an intro call slot
calendar.google.com
WebRun opens Google Calendar to hold an intro call slot. - Hold a tentative intro call slot on the new owner's calendar
- Set it for the next available working slot
- Note the contact's name, role, and company in the event description
Done when A tentative intro call slot is held for every routed contact.
-
3
WhatsApp - text the new owner
whatsapp.com
WebRun opens WhatsApp to text the new owner. - Text the new owner with the contact's name, role, and company
- Note which rep originally found the contact
- Ask them to confirm the held call slot works
Done when The new owner has been texted about the routed contact.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it reach out to the contact itself?
No. WebRun only routes the contact to the correct owner and holds a tentative slot. The new owner decides how and when to actually reach out.
How does it know the correct territory owner?
It reads your existing territory assignment, so a contact is only routed to the rep who already owns that account or region, not a random reassignment.
What if the finding rep wanted to keep the contact?
Routing follows your territory rules, so if a contact falls outside a rep's assigned territory it gets handed off. Territory exceptions are managed the normal way your team already handles them.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.