Assignment Coverage
Eligible owner coverage, unmatched leads and dated reassignment reasons.
Put the next lead with someone who can act on it.
| Alert Number | Lead | Alert Type | Due Date | Status |
|---|---|---|---|---|
| PA-87398 | LDS-84834 | ThresholdCrossed | 28 Sep | Open |
| PA-50271 | LDS-76521 | FollowUpDue | 13 Sep | Open |
| PA-10671 | LDS-61306 | ConversionFailure | 27 Sep | Open |
| PA-40311 | LDS-10397 | ThresholdCrossed | 19 Sep | Open |
| PA-99748 | LDS-54583 | FollowUpDue | 29 Sep | Open |
| PA-86387 | LDS-77482 | ConversionFailure | 19 Sep | Open |
Set a clear priority when routing rules overlap, and maintain an eligible owner pool for each territory. Changes in coverage should leave an understandable assignment history. Keep unmatched leads visible so a failed rule does not turn into lost work.
An alert should tell its owner what changed and what needs attention. Distinguish a new priority signal from an overdue follow-up or a conversion problem. Acknowledging the alert records that it was seen; it does not complete the underlying lead work.
Route the lead. Submit new routing rules for independent Admin approval. Apply approved rules by explicit priority and deterministic ties. Choose an active eligible owner in the territory with an atomic round-robin cursor; otherwise retain an unassigned lead. Every initial assignment or reassignment appends LeadAssignments with its reason.
Work the lead. Contact only through permitted channels, record meetings with bounded start and end times and update the follow-up outcome. An acknowledged priority alert does not qualify its lead. Withdrawing a contact purpose blocks new outreach even when a list membership or previous score remains active.
Territory routing. A permitted lead receives one eligible owner and an assignment history entry. Concurrent routing cannot allocate twice or choose an inactive user.
Priority alerts. The owner receives one actionable alert for the threshold crossing. A replay cannot create another alert or silently reassign the lead.
A territory can have several available representatives. Apply the approved routing rule to the current lead and choose among eligible owners using the territory’s recorded rotation position. If two leads arrive together, advance that position atomically so concurrent assignments do not repeatedly select the same person from a stale queue.
An owner becoming unavailable does not justify sending work outside the authorized territory. Leave an unmatched lead visible for a manager to resolve, with the reason the rule could not find an eligible destination. Reassignments retain the prior owner, time and explanation, allowing the team to follow the handover without replacing its history.
| Record Number | Lead | Assigned To | Assigned From | Reason |
|---|---|---|---|---|
| LA-79194 | LDS-64199 | KT | LL | InitialRouting |
| LA-34811 | LDS-23936 | HU | TA | MQLHandoff |
| LA-72733 | LDS-92462 | EV | NM | ManualReassign |
| LA-67636 | LDS-45285 | EN | GF | StaleRecycle |
| LA-83471 | LDS-17351 | UG | YW | OutOfOffice |
| LA-60711 | LDS-42408 | VK | TH | TerritoryRealignment |
An alert should identify the lead, its reason for priority and the follow-up owner. A changed score may justify a new conversation, but repeated delivery of the same qualifying event should not create duplicate work. Keep the alert’s state connected to its actual follow-up so closing a notification does not falsely qualify the prospect.
For example, a prospect can move into a new territory after providing a corrected business address. The manager reviews the change, selects an eligible owner and records why responsibility moved. The receiving rep sees the prospect’s current context and outstanding activity. The expected result is one accountable owner with enough information to continue, while the assignment history explains the transition and the scoring evidence explains the priority.
Bring incoming prospects into a consistent qualification queue.
Explain why a lead deserves attention before the team acts.
Put the next lead with someone who can act on it.
Coordinate useful follow-up while respecting contact preferences.
Give account executives the context to accept a qualified lead.
Learn which sources and signals lead to accepted opportunities.
Eligible owner coverage, unmatched leads and dated reassignment reasons.
| Record Number | Lead | Assigned To | Assigned From | Reason |
|---|---|---|---|---|
| LA-79194 | LDS-64199 | KT | LL | InitialRouting |
| LA-34811 | LDS-23936 | HU | TA | MQLHandoff |
| LA-72733 | LDS-92462 | EV | NM | ManualReassign |
| LA-67636 | LDS-45285 | EN | GF | StaleRecycle |
| LA-83471 | LDS-17351 | UG | YW | OutOfOffice |
| LA-60711 | LDS-42408 | VK | TH | TerritoryRealignment |
Open alerts and due activities by permitted owner and territory.
| Alert Number | Lead | Alert Type | Due Date | Status |
|---|---|---|---|---|
| PA-87398 | LDS-84834 | ThresholdCrossed | 28 Sep | Open |
| PA-50271 | LDS-76521 | FollowUpDue | 13 Sep | Open |
| PA-10671 | LDS-61306 | ConversionFailure | 27 Sep | Open |
| PA-40311 | LDS-10397 | ThresholdCrossed | 19 Sep | Open |
| PA-99748 | LDS-54583 | FollowUpDue | 29 Sep | Open |
| PA-86387 | LDS-77482 | ConversionFailure | 19 Sep | Open |
Owns team routing and independent duplicate resolution.
Prepare RoutingRules for own TerritoriesManage team Leads, LeadActivities, LeadNotesReassign team ownership through LeadAssignmentsApprove independent DuplicateClusters resolutionWorks assigned prospects and submits qualified leads to the selected account executive.
Manage own Leads, LeadActivities, LeadNotesView own ScoringRuns, ScoringEvents, PriorityAlertsRead published ScoringRules and LeadSourcesAdd own ListMemberships subject to contact policyReviews assigned qualification handoffs and requests creation of downstream CRM records.
Manage own and explicitly AssignedAE Leads, LeadActivities, LeadNotesApprove assigned qualification submissions independently of the submitting repPrepare own LeadConversionsView permitted ScoringRuns and LeadAssignmentsCreate your ERP.AI account and get started with Proto.
We use essential cookies to run the site and optional cookies for features, analytics, and relevant content. See Cookie policy
We use cookies to enhance your experience, analyze site traffic, and serve relevant content. By clicking "Accept All," you agree to our use of cookies. You can customize your preferences at any time.
Learn more about how we use cookiesThese cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
These cookies enable additional features that enhance your experience, such as live chat, video playback, personalized content recommendations, and remembering user preferences.
These cookies help us understand how visitors interact with our site by collecting anonymous usage data. This allows us to measure performance, detect issues, and continuously improve the user experience.
These cookies allow us and advertising partners, including X, to deliver ads tailored to your interests. They track browsing habits across sites to provide relevant advertising and measure ad effectiveness.