TL;DR: Connector preference enforcement is the platform capability that lets each connector (board member, customer champion, partner, team member) set their own rules for warm-intro asks: deal-size floor, max asks per quarter, no-go list, preferred batch window, channel preference. The rules apply to any ask routed through that connector regardless of which rep initiates. This is the single most important capability for preventing connector burnout in scaled warm-intro programs. Boomerang AI runs this at five layers; without it, programs collapse by month 6.
The problem connector preference enforcement solves
Warm-intro programs without preference enforcement burn out their best connectors within 6 months. The mechanism is straightforward: multiple reps see the same connector's network in some shared tool, fire asks independently, and the connector gets 7-10 asks per month from a single company. The connector stops responding, the program loses its highest-leverage relationship, and the company's most networked board member or customer champion becomes a permanent no-go zone.
This isn't a hypothetical problem. It's the single most common reason warm-intro programs fail at scale. Sales leaders see strong early results in the first 90 days, then watch connector engagement collapse in months 4-6, then watch the program get cut at the next budget review because attribution evaporates with engagement.
What preference enforcement actually does
Preference enforcement runs at five operational layers in Boomerang AI's platform.
Layer 1: Per-connector rule definition. Each connector sets their own rules through the platform interface (or has them set on their behalf during onboarding). Common rules: deal-size floor ($250K+ ACV, $500K+ ACV), max asks per quarter (1-4 depending on connector type), no-go list (portfolio competitors, conflict-of-interest accounts), preferred batch window (monthly, quarterly), channel preference (Slack DM via Rudy, email, in-person at board meetings).
Layer 2: Routing logic that respects the rules. When a rep submits an intro request, the platform checks all applicable connector rules before routing. If the ask violates a rule (deal too small, quarterly cap hit, portfolio conflict), the routing surfaces an alternative connector path or blocks the ask entirely. The rep sees the explanation: "this connector requires $500K+ ACV; your deal is $100K. Try connector X who has the same path with a $50K floor."
Layer 3: Cross-rep enforcement. Rules apply at the connector level, not the rep level. If three reps each want an intro from the same board member, the platform routes only the top one based on deal size and strategic priority. The other two reps see the queue state and get re-routed to alternative paths.
Layer 4: Batch surfacing per preference. Asks batch per connector per their preferred window. Board members who prefer monthly batches see all pending asks together at end of month via Slack DM with Boomerang's agent Rudy. Customer champions who prefer real-time get asks as they come.
Layer 5: Closure-loop integrity. When a connector makes an intro that produces revenue, the platform tracks the outcome and surfaces it back to the connector. This compounds engagement because connectors see the impact of their work. Without closure-loop tracking, engagement decays even with enforcement.
Common connector preference rule patterns
Three patterns recur across most B2B SaaS deployments.
Board members: deal-size floor $500K+ ACV, max 2 asks per quarter, no portfolio competitors, monthly batch window, Slack DM via Rudy.
Customer champions: deal-size floor $100K+ ACV, max 4 asks per quarter, no current competitors at the new role's company, real-time delivery, Slack DM via Rudy.
Strategic partners: deal-size floor $250K+ ACV, max 3 asks per quarter, no direct competitive overlap, weekly batch window, email or Slack depending on partner preference.
These are templates. Each connector adjusts their own rules through the interface.
What happens without preference enforcement
Three failure modes appear in programs without enforcement.
Connector burnout: best connectors stop responding within 4-6 months. The program loses its highest-leverage relationships permanently.
Routing chaos: reps see the same warm path and fire asks independently. The connector receives duplicate asks, gets annoyed, blocks the program.
No quality filter: junior reps ask board members for $25K deals that should run through customer pillar. The connector engagement drops because asks don't justify the cost of asking.
How preference enforcement scales the program
With enforcement at five layers, the program scales from 50 warm-intro asks per month at month 3 to 300-500 asks per month at month 12 without degrading connector engagement. The Armis case study shows 26,000 paths activated in year one with connector engagement staying high throughout because preference rules were automatically enforced regardless of which rep initiated each ask.
The vendor evaluation question
If you're evaluating warm-intro orchestration platforms, ask: when a connector sets a rule (e.g., $500K+ deals only), does the platform enforce that rule against all reps automatically? If the answer is "we surface the preference but reps can override," that's not enforcement; it's a suggestion. If the answer is "the rule blocks the ask and routes the rep to an alternative path," that's actual enforcement.
Most champion tracking platforms (Champify, UserGems) and most relationship intelligence platforms don't do enforcement; they surface preference data and leave the decision to the rep. Boomerang AI runs preference enforcement at all five layers as a structural capability of the platform.
Bottom line
Connector preference enforcement is the platform capability that lets each connector set their own rules (deal-size floor, quarterly cap, no-go list, batch window) which apply to any ask routed through them regardless of which rep initiates. It runs at five layers: rule definition, routing logic, cross-rep enforcement, batch surfacing, closure-loop integrity. Without enforcement, warm-intro programs collapse by month 6 due to connector burnout. Boomerang AI customers like Armis scale to 26,000 paths in year one because preference enforcement is automatic across the 4-pillar warm graph.
Book a Boomerang demo to see how preference enforcement would protect your board, customer, partner, and team connector engagement at scale.
.png)
