Stats
Actions
Tags
From rampstack-skills
Designs meeting schedulers and booking flows that qualify leads and set up calls well, distinguishing three patterns: any-time-friction, interrogation-gate, and qualified-fast-path.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rampstack-skills:scheduler-and-booking-designThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A senior growth practitioner's playbook for designing meeting schedulers and booking experiences that qualify leads, set up calls well, and convert at higher rates than a generic booking link. Availability logic, qualification gating, prep automation, follow-up sequencing. The discipline of building a scheduler that earns the booking by earning a better call.
references/availability-logic-patterns.mdreferences/common-scheduler-failures.mdreferences/prep-automation-patterns.mdreferences/qualification-field-design.mdreferences/reminder-sequence-patterns.mdreferences/reschedule-and-no-show-handling.mdreferences/routing-patterns.mdreferences/scheduler-anti-patterns.mdreferences/scheduler-decision-criteria.mdA senior growth practitioner's playbook for designing meeting schedulers and booking experiences that qualify leads, set up calls well, and convert at higher rates than a generic booking link. Availability logic, qualification gating, prep automation, follow-up sequencing. The discipline of building a scheduler that earns the booking by earning a better call.
Most schedulers fail in one of two ways. Generic booking links produce cold demos where reps know nothing about the person they are about to talk to. Conversion stays at the rate of unqualified raw demos. Or qualification forms with 12 fields scare users off before they can book; drop-off at the form approaches 90 percent; only the leads who happen to survive the form actually convert.
The schedulers that work do something different. Just enough qualification to set up the call well (3-5 strategic fields), context-aware availability (high-fit leads see senior reps; low-fit leads route differently), prep automation that briefs the rep before the call. The booking is honest about who the audience is; the call is set up to succeed.
The voice is the senior growth practitioner who has watched schedulers double demo conversion when redesigned and watched them collapse when more qualification was added. Practical, opinionated about which fields earn their place, willing to call out when the booking flow is the wrong tool.
When to use this skill: scoping a scheduler for the first time, auditing a booking flow with poor conversion or poor downstream call quality, designing the qualification gate that produces context without producing friction, or deciding routing logic that matches leads to the right reps.
This skill spans meeting schedulers and booking experiences across acquisition and sales contexts. The growth-tooling distinctions:
multi-step-form-design is pre-signup data capture (forms before the user has access to anything). This skill is meeting-booking specifically; qualification fields exist but the goal is the call, not the data.funnel-flow-architecture is broader funnel architecture. This skill is the scheduler specifically.lead-magnet-design is different commitment level. Magnets earn an email; bookings earn time.scheduler-and-booking-design (this skill) is the qualification, availability, routing, prep automation, and follow-up sequencing for meetings.pm-spec-writing is the spec for engineers building the scheduler.The audience: growth marketers, product marketers, marketing operations leads, sales operations leads, agencies running booking optimization for SaaS clients.
Out of scope: pre-signup forms (covered by multi-step-form-design); broader funnel orchestration (covered by funnel-flow-architecture); the engineering implementation; specific Calendly/Cal.com/Chili Piper/SavvyCal platform configurations (those stay implementation-side).
Before designing the scheduler, decide whether a scheduler is the right tool.
Schedulers earn investment when:
Schedulers do NOT earn investment when:
The decision is not "should we have a scheduler"; it is "is the scheduler the right next investment for this audience and goal."
Detail in references/scheduler-decision-criteria.md.
The keystone framing.
Any-time-friction. Generic booking link with no qualification, no context capture. Reps show up to calls cold; they spend the first 10 minutes asking the same qualification questions the form should have captured. Conversion stays at the rate of unqualified raw demos. Cost: sales capacity used inefficiently; high-fit leads get the same experience as low-fit leads; downstream conversion suffers.
Interrogation-gate. Qualification form with 12 fields before the user can book. Drop-off at the form approaches 90 percent. The qualification works for the leads who survive but the system loses everyone else. Cost: high-fit leads who would have converted abandon at the form; conversion rate is poor even though the post-form leads are well-qualified.
Qualified-fast-path. Just enough qualification to set up the call well (3-5 strategic fields), context-aware availability (high-fit leads see senior reps; low-fit leads see SDRs or are routed to async), prep automation that briefs the rep before the call. Cost: design effort upfront is significant; conversion plus downstream call quality both improve meaningfully.
The litmus test. Does the rep arrive at the call already knowing the prospect's situation? Did the prospect feel respected by the booking experience? If yes to both, qualified-fast-path. If the rep starts cold, any-time-friction. If the prospect dropped at the form, interrogation-gate.
Which fields earn their place; which create friction.
The principle. Each qualification field should serve one of two purposes: route the booking to the right rep, or give the rep enough context to skip the qualification phase of the call. Fields serving neither purpose are friction.
Strong qualification fields.
Weak qualification fields.
The five-field rule. Most production schedulers work well with 3-5 qualification fields. More than 5 starts producing interrogation-gate dynamics. Less than 3 does not give the rep useful prep context.
Detail in references/qualification-field-design.md.
Round-robin, weighted by fit, calendar integration.
Pattern A: Pure round-robin. Bookings cycle through available reps in order.
When to use. Simple distribution; small teams.
Strengths. Even distribution; simple logic.
Weaknesses. Does not match high-fit leads to senior reps; does not load-balance based on capacity.
Pattern B: Weighted round-robin. Bookings cycle but weighted by rep performance, capacity, or specialty.
When to use. Teams with rep specialization; teams where capacity differs.
Pattern C: Fit-based routing. High-fit leads (large company, high urgency) route to senior reps; lower-fit leads route to SDRs or async resources.
When to use. Teams with multi-tier sales motion; clear fit signals captured.
Pattern D: Hybrid. Combines patterns. Fit-based routing for top tier; round-robin within tier.
When to use. Most production teams.
The match-to-rep discipline. The qualification fields feed routing logic. Routing fails if qualification does not capture routing-relevant data.
Detail in references/availability-logic-patterns.md.
Different reps for different lead types.
By company size. SMB to SDRs, mid-market to AEs, enterprise to senior AEs.
By use case. Different specialists for different product use cases.
By geography. Different reps for different time zones or regions.
By language. Native-language reps for non-English-primary leads.
By account ownership (B2B). If the lead's company is already a customer or prospect of an AE, route to that AE.
The unrouted lead. Some leads do not fit obvious routing. Default rule needed: round-robin or specific catchall.
Detail in references/routing-patterns.md.
Briefing the rep before the call.
The principle. The qualification data should reach the rep in a useful form before the call. Without prep automation, the data sits unused.
Prep automation patterns.
Strong prep automation. The rep arrives at the call already knowing: who the prospect is, what they are trying to accomplish, what they are using today, when they need a solution.
Weak prep automation. The rep has the qualification data but it is buried in a CRM field nobody opens. The rep starts the call cold despite the data.
Detail in references/prep-automation-patterns.md.
The communications around the booking.
Booking confirmation. Sent immediately after booking. Confirms time; restates context; sets expectations.
Pre-meeting reminder. Sent 24 hours and/or 1 hour before. Reduces no-shows.
Post-meeting follow-up. Sent within hours of the call. Recap; next steps; resources.
Reschedule and no-show flows. Different flows for different outcomes.
The reminder discipline. Reminders are useful; over-reminding is friction. Two reminders (24-hour and 1-hour) is typical.
Detail in references/reminder-sequence-patterns.md.
What happens when meetings do not go to plan.
Reschedule patterns.
No-show patterns.
The respect-the-no principle. Prospects who no-show twice often do not want the meeting. Multiple aggressive reschedule attempts feel like pressure.
Detail in references/reschedule-and-no-show-handling.md.
Rapid-fire. Diagnoses in references/common-scheduler-failures.md.
When designing or auditing a scheduler, walk these 12 considerations.
The output of the framework is a scheduler that earns the booking by earning a better call, with conversion that compounds because the calls themselves are better.
references/scheduler-decision-criteria.md - When schedulers earn the build vs when forms or sales-pipeline tools serve.references/qualification-field-design.md - Strong and weak qualification fields. The five-field rule.references/availability-logic-patterns.md - Round-robin, weighted, fit-based, hybrid. Match-to-rep discipline.references/routing-patterns.md - By size, use case, geography, language, account ownership. Unrouted-lead default.references/prep-automation-patterns.md - CRM enrichment, calendar invite, Slack brief, account research.references/reminder-sequence-patterns.md - Confirmation, 24-hour, 1-hour, post-meeting. Frequency discipline.references/reschedule-and-no-show-handling.md - Reschedule patterns, no-show patterns, respect-the-no principle.references/scheduler-anti-patterns.md - The patterns that look like schedulers but degrade conversion.references/common-scheduler-failures.md - 9+ failure patterns with diagnoses and cures.The schedulers that work as compounding assets are the ones that produce better calls. Not just more bookings. Calls where the rep arrives prepared; the prospect feels respected; the conversation moves faster because qualification was already done. Conversion compounds because the calls themselves convert better.
That is the bar. Below the bar are any-time-friction (cold demos, conversion suffers) and interrogation-gate (90 percent abandon at the form). Above the bar are qualified-fast-path schedulers where qualification, availability, routing, prep automation, and follow-up sequencing combine into a system that earns the booking and the call.
The discipline is in the design choices. The decision to use a scheduler at all. The qualification fields that earn their place. The availability logic that matches lead to rep. The routing that respects rep tier and capacity. The prep automation that delivers context to reps before the call. The reminder cadence that reduces no-shows without becoming spam. The reschedule and no-show handling that respects the prospect.
npx claudepluginhub rampstackco/claude-skills --plugin rampstack-skillsGenerates booking and calendar CRO engine with industry auto-detection, ICS download, Google Calendar integration, and revenue-boosting features. Triggers on booking, scheduling, and calendar topics.
Designs revenue operations including lead scoring, routing, handoffs, lifecycle stages, and CRM process automation. Use when marketing, sales, or CS workflows need operational alignment.
Designs revenue operations systems, lead lifecycle management, and marketing-to-sales handoff processes. Covers stage definitions, scoring, routing, and CRM automation.