Loading...
Loading...
Found 11 Skills
Design the assignment logic that routes inbound leads to sales reps - rule precedence and waterfall ordering, lead-to-account matching, territory assignment rules (geography, segment, industry, named accounts), round-robin variants (straight, weighted, capacity-based, availability-aware), fallback catch-all queues, SLA escalation and reassignment, and safe rollout of routing changes. Use whenever the user mentions lead routing, lead assignment, territory assignment, round-robin, lead distribution, "who gets this lead", a lopsided round-robin, or leads sitting unworked in a CRM queue - even if they never say "routing". Covers B2B account-based and B2C/PLG high-volume routing. Do NOT use for designing the lead score itself - use mbfinotti/revops-skills@lead-scoring instead.
Intelligent lead assignment and routing - AI-powered scoring, territory mapping, round-robin distribution, and workload balancing
Design and implement lead routing and assignment rules — round-robin, territory-based, score-based, and account-based models. Use when designing how leads get assigned to reps, building routing rules in your CRM, optimizing speed-to-lead, setting up territory assignments, configuring lead queues, or scaling assignment as your team grows. Do NOT use for lead scoring model design (use /sales-lead-score), CRM platform configuration (use /sales-apollo or /sales-salesloft), or marketing-to-sales handoff process (use /revops).
Design, validate, and recalibrate a lead scoring model - fit and engagement signals, weighting, negative scoring and exclusions, decay, MQL/PQL threshold and tier setting, backtesting against closed-won/closed-lost outcomes, and governance; also diagnoses an existing broken model. Use whenever the user mentions lead scoring, an MQL threshold, fit vs engagement scoring, product-qualified leads, score decay, "score my leads", "our lead scores are wrong", "sales rejects our MQLs", or "too many junk MQLs" - even if they never say "scoring model". Covers B2B sales-led and B2C/PLG, rules-based design and predictive readiness. Do NOT use for assigning scored leads to reps - use mbfinotti/revops-skills@lead-routing instead.
Schedule sales meetings efficiently — booking pages, round-robin routing, calendar integration, reminders, no-show recovery, and meeting page conversion. Use when setting up booking links, configuring round-robin scheduling, reducing no-shows, optimizing meeting pages, choosing a scheduling tool, Mixmax scheduling, or Mixmax meetings. For Yesware-specific help, use /sales-yesware. Do NOT use for lead routing rules (use /sales-lead-routing), cadence design (use /sales-cadence), or calendar-based CRM automation (use /sales-integration).
When the user wants to build or improve a sales bot's ability to integrate with calendars and schedule meetings autonomously. Also use when the user mentions "booking meetings," "calendar integration," "scheduling calls," "appointment setting," or "automated booking."
Methodology for defining product-qualified lead (PQL) signals, scoring, and routing.
When the user wants to build or improve a sales bot's ability to ask the right questions to score and route leads automatically. Also use when the user mentions "bot qualification," "automated lead scoring," "qualification questions," "lead routing," or "qualification flow."
Use when defining or adjusting marketing-to-sales assignment rules.
Analyze inbound leads (form fills, demo requests) and score based on ICP fit, intent, and urgency. Auto-generates qualification questions, routes to right rep, and suggests personalized first touch. Use for qualifying and routing inbound leads at scale.
Decide who owns an unrouted lead or opportunity and manage the handoff - deterministic routing by the org's own rules, a routing card the human router accepts or overrides, and drafted handoff notes. Use when the user says "route this lead", "who should own [lead/opp]", "work the routing queue", "assign [company] to a rep", or on a scheduled intake sweep.