sales-calendly

name	sales-calendly
description	Calendly platform help — scheduling links, booking pages, event types, round-robin routing, workflows, routing forms, embeds, and API/webhook integration. Use when setting up Calendly booking pages or event types, Calendly round-robin not distributing meetings evenly, Calendly routing forms not qualifying leads, Calendly webhook not firing on booking events, Calendly API returning unexpected data or hitting rate limits, Calendly timezone showing wrong time to invitees, Calendly embed not loading in your app, or choosing between Calendly Standard vs Teams plan. 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 Calendly]
license	MIT
version	1.0.0
tags	["sales","scheduling","booking","calendar","platform"]
github	https://github.com/calendly

Calendly Platform Help

Step 1 — Gather context

If references/learnings.md exists, read it first for accumulated platform knowledge.

Ask the user:

1. What area of Calendly do you need help with?

   • A) Booking pages & event types — setup, customization, branding
   • B) Round-robin & team scheduling — routing, collective events
   • C) Routing forms — lead qualification before booking
   • D) API & webhooks — building integrations, syncing data
   • E) Workflows — automated reminders, follow-ups, notifications
   • F) Embeds — inline, popup widget, or popup text in your site/app
   • G) Payments — Stripe/PayPal collection on booking
   • H) Integrations — Salesforce, HubSpot, Zapier, etc.
   • I) Choosing Calendly vs Cal.com vs other tools
   • J) Something else

2. What plan are you on?

   • A) Free (1 event type, 1 calendar)
   • B) Standard ($10-12/seat/mo)
   • C) Teams ($16-20/seat/mo)
   • D) Enterprise
   • E) 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}"
• Comparing Calendly vs Cal.com → "For head-to-head comparison — run: /sales-meeting-scheduler compare Calendly vs Cal.com"

If the question is Calendly-specific, continue to Step 3.

Step 3 — Calendly platform reference

Read references/platform-guide.md for the full platform reference — capabilities, pricing, data model, integration recipes, code examples.

Answer the user's question using only the relevant section. Don't dump the full reference.

For API or webhook questions, also read references/calendly-api-reference.md for endpoint details, JSON shapes, and code examples.