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/reminder-sequence-patterns.md
View on GitHub# Reminder sequence patterns
Confirmation, 24-hour, 1-hour, post-meeting. Frequency discipline.
The communications around the booking. Done well, reminders reduce no-shows without becoming spam; done poorly, reminders are either insufficient (no-shows climb) or excessive (prospect resents).
---
## The reduce-no-shows-without-spam principle
Reminders matter; their volume should be calibrated.
**The win.** Confirmation immediately after booking; one reminder 24 hours before; one reminder 1 hour before. Three communications total. No-show rate drops; prospects feel reminded but not nagged.
**The fail.** Confirmation; 5-day reminder; 2-day reminder; 1-day reminder; 1-hour reminder; 15-minute reminder. Six communications. Prospects mute the channel; no-shows persist for users who muted.
The discipline. Reminders earn their place; cumulative volume should be capped.
---
## Pattern A: Booking confirmation
Sent immediately after booking.
**What it includes.**
- Confirmed time and meeting type.
- Calendar invite attached.
- Brief restate of expectations (e.g., "Looking forward to learning about your X").
- Reschedule and cancel links.
**Strengths.**
- Immediate; reduces buyer's remorse.
- Sets expectations.
- Provides reschedule path.
**Weaknesses.**
- One-touch communication.
**When to use.** Always.
---
## Pattern B: Pre-meeting reminder
Sent 24 hours and/or 1 hour before.
**24-hour reminder.**
- Useful for users who book days in advance.
- Lets them prepare or reschedule with notice.
**1-hour reminder.**
- Useful for last-minute prep.
- Catches calendar drift.
**Both useful or one only?**
- Most production teams use both.
- For very short booking windows (same-day), 1-hour is enough.
- For longer-lead bookings, 24-hour matters.
---
## Pattern C: Post-meeting follow-up
Sent within hours of the call.
**What it includes.**
- Brief recap.
- Action items (rep's commitments).
- Resources mentioned in the call.
- Next-step CTA (next meeting, document, trial).
**Strengths.**
- Captures momentum from the call.
- Documents commitments.
**Weaknesses.**
- Requires rep to populate after the call (or rep-side tooling to auto-generate).
**When to use.** Sales conversations where next steps matter.
---
## Pattern D: Reschedule prompts
When the prospect cannot make the meeting.
**What it includes.**
- Easy reschedule link.
- Brief check-in copy ("Need to reschedule? No problem.").
**Strengths.**
- Reduces no-shows; users reschedule rather than ghost.
**Weaknesses.**
- Some users use this to reschedule indefinitely.
**When to use.** Always available; not aggressive.
---
## Pattern E: No-show follow-up
When the prospect does not attend.
**What it includes.**
- Acknowledgment of missed meeting.
- Reschedule link.
- Brief context-restatement.
**Tone.** Gentle, not punitive. The prospect may have had a real reason.
**The respect-the-no-show principle.** After 1-2 reschedule attempts, accept that the prospect is not engaging.
---
## Reminder timing
When each communication fires.
**Common cadence.**
- T+0: Confirmation immediately after booking.
- T-24h: Reminder 24 hours before.
- T-1h: Reminder 1 hour before.
- T+15m: Late-arrival check (sometimes).
- T+24h: Post-meeting follow-up.
The discipline. Each communication earns its place. Drop the ones that do not.
---
## Channel choice
Which channels to use.
**Email.** Default. Reliable; familiar.
**SMS.** Higher attention; more friction. Use selectively for high-value bookings.
**In-app notification.** If the booking is for a logged-in user, in-app reminders work.
**Slack or Teams.** For B2B internal-team meetings.
**The cumulative discipline.** Multiple channels for the same reminder is excessive. Pick one channel per reminder.
---
## Reminder copy
What the reminders say.
**Strong reminder copy.**
- "Looking forward to our call tomorrow at 2 PM PT. Here's what we'll cover: [agenda]."
- "Reminder: 1 hour until our call. Join here: [link]."
- "Thanks for the call today. Here's what we discussed: [recap]."
What works. Specific; useful; brief.
**Weak reminder copy.**
- "Don't forget your meeting!"
- "Your meeting is in 1 hour."
- "Did you know..."
What fails. Generic; no value-add; just a notification.
---
## Reminder personalization
How much to personalize.
**Default personalization.** Name; meeting time; rep name.
**Strong personalization.** Brief context tied to qualification ("Looking forward to discussing your [use case] situation").
**Over-personalization.** Long personalized paragraphs that read as marketing.
The discipline. Personalize where it adds value; do not pad with personalization for its own sake.
---
## Reminder analytics
Track effectiveness.
**Metrics.**
- Open rate per reminder.
- Reschedule rate per reminder.
- No-show rate (cumulative across cadence).
- Cancellation rate.
**Diagnostic uses.**
- Low open rate: subject line weak or channel wrong.
- High reschedule rate after specific reminder: that reminder triggers reconsideration.
- High no-show despite reminders: friction at the meeting itself, not the reminder.
---
## Reminder maintenance
Reminders decay.
**What decays.**
- Templates with stale rep names or roles.
- Calendar links that broke after platform changes.
- Channel preferences that no longer fit audience.
**Maintenance cadence.** Quarterly review of reminder templates and channels.
---
## Common reminder failures
**Too many reminders.** Cumulative volume is spam; users mute.
**Too few reminders.** No-show rate climbs.
**Generic copy.** No value; users dismiss.
**Wrong channel.** SMS for an audience that prefers email.
**Stale templates.** Rep names from former employees; broken calendar links.
**No post-meeting follow-up.** Conversation momentum lost.
**Aggressive no-show follow-up.** Multiple reminder attempts after a no-show; respect non-response.
**Personalization padding.** Long personalized text that reads as marketing.
---
## Methodology-level choices that stay in the public skill
The reduce-no-shows-without-spam principle. Patterns A through E (confirmation, pre-meeting, post-meeting, reschedule, no-show). Reminder timing. Channel choice. Reminder copy discipline. Reminder personalization. Reminder analytics. Reminder maintenance. Common failures.
## Implementation choices that stay internal
Specific reminder cadences for specific teams. Specific copy in brand voice. Specific channel choices. The team's no-show baselines. 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 |