Lead distribution

Routing is rule-driven. You define the assignment rules (territory, product, vertical, tier, capacity); the system applies them in priority order. When more than one partner is eligible, configurable tie-breakers (recent acceptance rate, current capacity, last assignment) decide the match, with optional channel-manager confirmation in the loop. Every decision is logged with the rule, the inputs, and the timestamp, so the logic is auditable end-to-end.

Yes. Strategic accounts can be held to named partners, locked out of automated distribution entirely, or routed through a manual approval queue. Override controls sit alongside the routing rules, so a channel manager can pull a lead out of the queue or reassign it without leaving the workflow.

Each assigned lead has an acceptance window calibrated to partner tier. If the partner doesn't act in time, the lead reassigns automatically to the next-best match and the channel manager is notified. Repeated misses can de-prioritize a partner in future routing; reliable follow-through is rewarded the same way.

Distribution and deal registration share one account and opportunity model. When a partner accepts a distributed lead, it implicitly registers against them for the standard protection window, so direct sales sees the account is partner-owned. If a competing registration arrives later, the conflict surfaces immediately with the original source, the assignment date, and the partner activity since, so program leads can resolve it transparently.

The original campaign source travels with the lead through partner pipeline stages, so marketing can see not just how many leads were distributed but how many converted and at what value. Channel managers see partner-level conversion and stage velocity. Updates flow back from partner CRM activity on a regular sync cadence, depending on the integration.

Conflict prevention starts before routing. Accounts assigned to direct sales or held for named partners are excluded from the distribution pool entirely. For accounts that qualify, routing rules and acceptance windows prevent the same account from being registered by two partners at once. When a conflict does surface, the audit trail shows who got it first and why.

Declined leads reassign automatically to the next-best match based on your routing rules. The decline is logged on both the partner record and the lead record, so patterns of refusal surface at the partner level. Repeated declines can factor into future routing weight, since a partner who doesn't accept leads is worth deprioritizing.

Yes. Each lead carries its source campaign as metadata, and routing rules can reference the source. That lets you route an inbound trial lead differently from a webinar lead differently from an SDR-qualified lead, while keeping all of them auditable in the same distribution log.

Yes. Tier is a first-class input to routing rules. Higher-tier partners can be prioritized for high-value lead segments; lower-tier partners can receive starter leads that match their readiness. The same rule engine handles tier, certification status, and capacity together, so nothing has to be maintained in parallel.

Routing runs as leads arrive in the platform. A lead that matches your rules assigns to a partner within seconds of landing in Unifyr. The acceptance window timer starts at assignment, so the partner sees the lead immediately and has their configured window to act before reassignment kicks in.