| name | sales-calcom |
| description | Cal.com platform help — open-source scheduling infrastructure with REST API v2, webhooks, embeddable atoms, self-hosting, round-robin routing, and booking page workflows. Use when setting up Cal.com booking pages or event types, Cal.com API not returning expected data, Cal.com webhooks not firing on booking events, Cal.com round-robin not distributing meetings evenly, Cal.com self-hosted instance has calendar sync issues, choosing between Cal.com cloud and self-hosted, or Cal.com routing forms not qualifying leads correctly. Do NOT use for general scheduling strategy across tools (use /sales-meeting-scheduler), or calendar-based CRM automation patterns (use /sales-integration). |
| argument-hint | [describe what you need help with in Cal.com] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","scheduling","booking","calendar","open-source","platform"] |
| github | https://github.com/calcom |
Cal.com Platform Help
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask the user:
-
What area of Cal.com do you need help with?
- A) Booking pages & event types — setup, customization, branding
- B) Round-robin & team scheduling — routing, collective events, managed events
- C) Routing forms — lead qualification before booking
- D) API & webhooks — building integrations, automation
- E) Self-hosting — Docker setup, calendar sync, Outlook issues
- F) Workflows — automated reminders, notifications, follow-ups
- G) Embeddable atoms — embedding Cal.com in your app
- H) Payments — Stripe/PayPal collection on booking
- I) Choosing Cal.com vs Calendly vs other tools
- J) Something else
-
Are you on cloud or self-hosted?
- A) Cal.com cloud (cal.com)
- B) Self-hosted (Docker/custom)
- C) Not sure yet / evaluating
-
What plan are you on?
- A) Free
- B) Teams ($12/user/mo)
- C) Organizations ($28/user/mo)
- D) Enterprise
- E) Self-hosted (no plan)
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 — Cal.com platform reference
Read references/platform-guide.md for the full platform reference — capabilities, pricing, data model, API quick-starts, webhook payloads, integration recipes.
Answer the user's question using only the relevant section. Don't dump the full reference.
Step 4 — Actionable guidance
