Lead Routing
Assigns each inbound lead to the right rep by territory, size and availability, then confirms in Teams.
This flow is being documented
Architecture and use case are already public. Build instructions and screenshots follow as the flow is finalised.
Use case
Leads sitting unassigned for a day lose most of their conversion probability. Routing them the moment they arrive makes first contact a matter of minutes.
Who uses it
Sales operations and account executives.
Real scenario
A web form submission for a 200-seat company in Northern Italy is assigned to the enterprise rep for that territory, who receives a Teams card within a minute.
Time saved
Before
Manual triage each morning
After
Assigned on arrival
Time saved
Hours per week, plus faster first contact
How it works
A form or webhook receives the lead, a routing table in SharePoint maps territory and size to an owner, the lead is written to the CRM list with that owner and a Teams adaptive card notifies the rep.
Step-by-step build
- 1
Capture leads from a form, website webhook or shared mailbox.
- 2
Look up the owner in a SharePoint routing table by territory and company size.
- 3
Create the lead record with the resolved owner and an SLA due date.
- 4
Notify the rep with an adaptive card containing accept and reassign actions.
- 5
Escalate to the sales manager when the SLA passes without a first contact.
Copilot prompt
Paste this into Power Automate Copilot to scaffold the flow.
Create a flow that receives inbound leads from a form or HTTP request, looks up the owning sales rep in a SharePoint routing table by territory and company size, creates the lead record with an SLA due date, sends the rep an adaptive card in Teams, and escalates to the manager if the SLA expires without contact.
Screenshots
Captures are added as each step is published.