Start with eligibility, then rank the eligible team.
A routing system should first remove teams that cannot responsibly own the opportunity. Market coverage, business hours, service capability, language, licensing, permissions, and customer restrictions define eligibility.
Only then should the system rank the remaining owners by capacity, specialization, response performance, account relationship, and current workload.
Design overflow before the first lead arrives.
Every primary assignment needs a visible response window and an explicit second path. Overflow can move from a person to a team, from a location to a regional desk, or from a live response to an automated Vyra Phone sequence.
The customer record should preserve each attempted owner, the timing of each handoff, and the condition that caused it.
- Primary owner and response deadline
- Ordered overflow path
- After-hours behavior
- Manual reassignment authority
- Final unresolved queue
Keep source and intent attached to the record.
A lead from Google, Meta, a Vyra Form, Zapier, or a direct webhook should not become an anonymous contact card. Campaign, page, form answers, consent, market, and prior customer history all belong in the routing decision and the team’s first response.
When a handoff occurs, the context moves with it. The customer should never have to reconstruct the journey for the next person.
Measure the quality of the handoff, not only its speed.
Median first action matters, but it is incomplete. Teams should also inspect accepted ownership, time to meaningful response, reassignment rate, unresolved age, qualification quality, and outcome by routing rule.
The purpose of reporting is to reveal where the operating model needs to change—not to reward fast but empty touches.