| name | sales-savvycal |
| description | SavvyCal platform help — personalized scheduling with calendar overlay, booking links, meeting polls, team scheduling (collective/round-robin/group), workflows, webhooks, REST API, and embeddable scheduling. Use when setting up SavvyCal booking links or event types, SavvyCal calendar overlay not showing for recipients, SavvyCal webhooks not firing on booking events, SavvyCal round-robin not distributing meetings evenly, SavvyCal embed not rendering on website, choosing between SavvyCal and Calendly or Cal.com, SavvyCal Zapier triggers not working, SavvyCal API returning errors, or SavvyCal paid bookings via Stripe not collecting payment. Do NOT use for general scheduling strategy across tools (use /sales-meeting-scheduler), calendar-based CRM automation patterns (use /sales-integration), or cadence/sequence design (use /sales-cadence). |
| argument-hint | [describe what you need help with in SavvyCal] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","scheduling","booking","calendar","platform"] |
| github | https://github.com/svycal |
SavvyCal Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask the user:
-
What area of SavvyCal do you need help with?
- A) Scheduling links — setup, customization, branding, calendar overlay
- B) Team scheduling — collective, round-robin, group modes
- C) Meeting polls — group availability coordination
- D) API & webhooks — building integrations, automation
- E) Embedding — inline, popover, floating widget on your website
- F) Workflows — reminders, notifications, follow-ups
- G) Payments — Stripe paid bookings (Premium)
- H) Integrations — HubSpot, Close, Zapier, Slack, conferencing
- I) Choosing SavvyCal vs Calendly vs Cal.com
- J) Something else
-
What plan are you on?
- A) Basic ($10/user/mo)
- B) Premium ($17/user/mo)
- C) Not sure yet / evaluating
If the user's request already provides most of this context, skip directly to Step 2. Lead with your best-effort answer using reasonable assumptions (stated explicitly), then ask only the most critical 1-2 clarifying questions at the end.
Step 2 — Route or answer directly
If the request maps to a specialized skill, route:
- General scheduling strategy → "This is a scheduling strategy question — run:
/sales-meeting-scheduler {user's question}"
- CRM integration patterns → "This is a tool integration question — run:
/sales-integration {user's question}"
- No-show recovery or reminder design → "This is a scheduling optimization question — run:
/sales-meeting-scheduler {user's question}"
Otherwise, answer directly from platform knowledge.
Step 3 — SavvyCal platform reference
Read references/platform-guide.md for the full platform reference — capabilities, pricing, data model, API quick-starts, webhook payloads, embed recipes.
Answer the user's question using only the relevant section. Don't dump the full reference.
Step 4 — Actionable guidance
You no longer need the platform guide — focus on the user's specific situation.
- Step-by-step instructions for their goal in SavvyCal
- Configuration recommendations — specific settings, with navigation paths
