assign-target-to-sdr

name	assign-target-to-sdr
description	Route SDR ownership by rules; never guess identity.
metadata	{"short-description":"Route targets using explicit ownership rules"}

Assign Target to SDR

Outcome

A deterministic, auditable routing recommendation with conflicts and fallback handling.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Target record, current owner and history, territory and segment rules, named-account lists, parent relationships, active opportunities, user availability, capacity, and routing exceptions.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Resolve the target and candidate SDR identities unambiguously.
2. Apply hard exclusions and named ownership before weighted or round-robin rules.
3. Check parent-account, duplicate, active-opportunity, customer, partner, suppression, and recent-owner conflicts.
4. Show the decisive rules and use an explicit queue or human-review fallback when no rule resolves the target.

Required output

• Target and current state
• Recommended SDR or queue
• Applied rules
• Conflicts and exceptions
• Service-level next step

Actions and boundaries

Ask for confirmation before changing owner or creating a handoff task, then report the exact record and result.