rampstackco/claude-skills / skills/scheduler-and-booking-design
scheduler-and-booking-design
VerifiedDesigning meeting schedulers and booking experiences that qualify leads, set up calls well, and convert at higher rates than a generic Calendly link. Availability logic, qualification gating, prep automation, follow-up sequencing. Honest about any-time-friction (no qualification, just a booking link), interrogation-gate (so much qualification it scares users off), and qualified-fast-path (just enough qualification to set up the call well) patterns. Triggers on scheduler design, meeting booking, demo scheduling, sales call scheduling, calendar tool, booking page, qualification flow. Also triggers when sales team complains about cold demos, when booking conversion is poor, or when scheduler is being scoped for the first time.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 369 B |
| SKILL.md | skill md | 17.3 KB |
| references/availability-logic-patterns.md | markdown | 7.2 KB |
| references/common-scheduler-failures.md | markdown | 5.6 KB |
| references/prep-automation-patterns.md | markdown | 7.0 KB |
| references/qualification-field-design.md | markdown | 7.0 KB |
| references/reminder-sequence-patterns.md | markdown | 6.4 KB |
| references/reschedule-and-no-show-handling.md | markdown | 6.7 KB |
| references/routing-patterns.md | markdown | 5.9 KB |
| references/scheduler-anti-patterns.md | markdown | 5.7 KB |
| references/scheduler-decision-criteria.md | markdown | 6.9 KB |
references/scheduler-anti-patterns.md
View on GitHub# Scheduler anti-patterns
The patterns that look like schedulers but degrade conversion. Anti-patterns are easy to ship; the cost shows up in booking conversion, downstream call quality, and brand reputation.
---
## The any-time-friction scheduler
The pattern. Generic booking link with no qualification.
The signal. Reps show up cold; downstream demo-to-sale conversion poor.
The cost. Sales capacity used inefficiently; call quality suffers.
The cure. Add 3-5 qualification fields; route to right rep tier; deliver prep to reps.
---
## The interrogation-gate scheduler
The pattern. 12-field qualification form before booking.
The signal. 90 percent drop-off at the form.
The cost. Lose conversions from would-be buyers; only the most committed survive the form.
The cure. Cut to 3-5 fields; defer additional questions to in-call or post-meeting.
---
## The wrong-rep-tier scheduler
The pattern. Round-robin routing for tiered team.
The signal. Enterprise leads land on SDRs; SDRs unprepared; conversion drops.
The cost. High-value leads get junior reps; senior reps underutilized.
The cure. Fit-based routing tied to qualification.
---
## The no-prep-automation scheduler
The pattern. Qualification captured but not delivered to reps.
The signal. Reps start calls cold despite qualification data existing.
The cost. Qualification work wasted; cold-call dynamics return.
The cure. CRM enrichment, calendar invite enrichment, Slack briefs.
---
## The no-buffer scheduler
The pattern. Back-to-back meetings without buffer time.
The signal. Reps run late; calls feel rushed; quality drops.
The cost. Reps stressed; calls poorer; conversion suffers.
The cure. 10-15 minute buffer between meetings.
---
## The no-capacity-cap scheduler
The pattern. Reps booked solid all day every day.
The signal. Quality drops; rep burnout.
The cost. Calls that book are lower quality; reps eventually leave.
The cure. Cap meetings per day per rep (3-5 typical).
---
## The time-zone-confused scheduler
The pattern. Times shown in rep's time zone; prospect has to convert mentally.
The signal. Wrong-time bookings; no-shows from time zone errors.
The cost. Prospects miss meetings; assume their fault.
The cure. Auto-detect prospect time zone; display explicitly.
---
## The aggressive-reminder scheduler
The pattern. Multiple reminders per booking (5+ touchpoints).
The signal. Prospects mute or unsubscribe; reminder effectiveness drops.
The cost. Reminders trained to be ignored; no-shows persist.
The cure. Two reminders typical (24-hour, 1-hour). Cap cumulative volume.
---
## The aggressive-no-show-recovery scheduler
The pattern. Multiple reschedule attempts over short period.
The signal. Brand earns harassment reputation; recovery rate drops.
The cure. One-to-two reschedule attempts max; respect non-response.
---
## The aggressive-cancellation-prevention scheduler
The pattern. Cancellation requires multi-step or contact with sales.
The signal. Public complaints; trust damage.
The cost. Reputation harm; sometimes regulatory issues.
The cure. Self-serve cancellation; one click.
---
## The unmaintained scheduler
The pattern. Routing rules from years ago; team changed; rules did not.
The signal. Leads route to absent reps; bookings sit unread.
The cure. Quarterly maintenance. Team transitions trigger routing updates.
---
## The mobile-broken scheduler
The pattern. Booking flow works on desktop; breaks on mobile.
The signal. Mobile conversion half of desktop.
The cost. Mobile audience underserved.
The cure. Mobile-first design and testing.
---
## The double-booking scheduler
The pattern. Calendar integration broken; multiple bookings for same time.
The signal. Reps and prospects both arrive; one waits or leaves.
The cost. Rep frustration; prospect confusion; brand damage.
The cure. Calendar integration tested. Buffer time. Conflict detection.
---
## The shared-link bypass scheduler
The pattern. Reps share generic booking links alongside structured flow.
The signal. Routing logic bypassed; cold demos return.
The cost. Investment in qualification and routing partially undone.
The cure. Disable generic links. Train reps to use structured links.
---
## The integration-brittle scheduler
The pattern. Calendar, CRM, or video integration breaks frequently.
The signal. Reps complain about manual workarounds.
The cost. Operational friction; data inconsistency.
The cure. Stable integrations; monitoring; rollback plans.
---
## How to detect anti-patterns
Audit cadence. Quarterly review of scheduler portfolio.
**Audit questions.**
- Is qualification calibrated (anti-pattern check: any-time-friction, interrogation-gate)?
- Does routing match team tier (anti-pattern check: wrong-rep-tier)?
- Does prep automation deliver (anti-pattern check: no-prep-automation)?
- Is calendar logic sound (anti-pattern check: no-buffer, no-capacity-cap, double-booking)?
- Are reminders calibrated (anti-pattern check: aggressive-reminder)?
- Is no-show recovery respectful (anti-pattern check: aggressive-no-show-recovery)?
- Is cancellation easy (anti-pattern check: aggressive-cancellation-prevention)?
- Does the system work on mobile (anti-pattern check: mobile-broken)?
- Are integrations stable (anti-pattern check: integration-brittle)?
**The retire decision.** Anti-pattern schedulers warrant redesign or retirement.
---
## Methodology-level choices that stay in the public skill
The catalog of anti-patterns. Signal-pattern-cost framing. Cures matched. Audit cadence and questions. The retire decision.
## Implementation choices that stay internal
Specific anti-patterns the team has shipped historically and lessons learned. Specific portfolio audit results. The team's audit calendar. These vary by team.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |