Cal.com Buyer's Checklist: 11 Decisions to Settle Before You Pay

Plan fit and seats: answer these first

Work through this checklist in order, because the first answers decide which later checks matter. Cal.com sells four plans: Free for one user, Teams at $12 per user a month on yearly billing or $16 monthly, Organizations at $28 or $37, and Enterprise by quote ^[1]. The plan follows from two questions. How many people host bookings, and do they need to work as one team or several? Write your answers down before the trial starts. Teams and Organizations each come with a 14-day trial, and a written list turns those two weeks into a test of specific things rather than a tour of the product. If more than four checks fail, compare alternatives before you buy.

• Count hosts, not employees. List everyone who will host or attend team bookings. That list, not the org chart, sizes the plan.
• Ask which seat-billing method applies. Cal.com bills either by the peak member count in the cycle or by active users who hosted or attended a booking, with a minimum commitment. The help center says it depends on the plan.
• Plan for peaks. Under peak billing, a team that grows from 10 to 15 members and drops to 12 pays for 15 seats. Remove departed members before the cycle closes.
• Choose the billing term last. Yearly billing saves a quarter on Teams, but paid plans bill in advance, renew automatically and are non-refundable except as the Terms state.

Routing and team scheduling

Team features are the main reason to pay. Teams adds one team with shared availability, round robin, collective and managed event types, recurring events and routing forms. Round robin assigns bookings by weights, priorities or least recently booked, and admins can add restriction schedules that clip team event types to a time window. Organizations adds unlimited sub-teams and routing by attributes such as region or company size, which the help center says is available only on Organizations and Enterprise. Before you test anything, write down how leads or candidates should reach people today. Most teams skip this step. Then check that the rules can be expressed in Cal.com without workarounds.

• One team or many? Teams includes a single team. Separate sales, support and hiring teams with their own admins point to Organizations.
• Distribution logic. Test weighted round robin, fixed hosts with rotating teammates, and round-robin groups that put one person from each host group on the call.
• Routing forms. Build one real form with your qualifying questions, embed it on a test page and check where each answer lands.
• Reassignment. Confirm that booked meetings can be moved to another member when someone is out.
• Insights. Check that the analytics show what your manager reviews each week: completed, rescheduled and cancelled bookings, no-show rates and routing drop-off.

Messaging and credits

Reminders by email are included on every plan, but texts, WhatsApp messages and the Cal.ai phone agent run on credits. One credit is worth $0.01. Teams includes 750 credits per member a month, Organizations 1,000, Enterprise unlimited, and Free none, though Free users can buy them. Messages are priced at the Twilio regional rate plus an 80% processing fee, per segment, and Cal.ai calls cost 29 credits a minute. Estimate monthly volume before you pick a plan. Volume decides the bill. A team that sends one text reminder per booking will rarely notice credits, while a team that lets an AI agent call leads all day can burn through its allowance quickly.

• Custom workflows. Free is limited to the default reminder email. Custom email and SMS workflows need a paid plan.
• Segment length. A text with an emoji is cut into 70-character segments instead of 160, so keep reminders plain.
• Fallback behavior. When credits run out, texts stop and Cal.com sends email instead. Decide who watches the balance; low-balance warnings go to team admins.
• Phone numbers. Cal.com sells only US numbers for Cal.ai, at $5 a month. Elsewhere you import a Twilio number.
• Test calls cost credits. Budget for testing the agent, not only for live calls.

Compliance and the BAA

Healthcare buyers should settle this section before any other. A signed business associate agreement is free on Enterprise and on Organizations with 15 or more users, and costs $300 a month on Teams or on Organizations with fewer than 15 users ^[2]. Some older Cal.com pages tie HIPAA to Enterprise alone; the HIPAA page carries the current rule. The Terms say protected health information may not be submitted without a signed BAA. Cal.com also makes the customer responsible for checking that third-party integrations handling patient data are HIPAA compliant. Beyond HIPAA, Cal.com states SOC 2 Type II, ISO 27001, GDPR and CCPA compliance and offers its reports for download.

• Price both routes. Compare Teams plus the BAA fee against Organizations at 15 seats. For ten or more clinicians, Organizations is often the cheaper way to get a free BAA.
• Ask about empty seats. The HIPAA page does not say whether seats you pay for but leave empty count toward the 15-user threshold. Get it in writing.
• Audit every connected app. Calendars, video tools, CRMs and payment apps each need their own HIPAA position.
• Identity controls. SAML SSO, SCIM provisioning and domain enforcement sit on Organizations and above.
• Download the reports. The security page offers the SOC 2 report, ISO certificate, penetration test report and DPA.

Data residency

Where data lives is a contract question. It is not a setting. Cal.com's privacy policy says data is processed in the United States, with some subprocessors elsewhere, and that EU residency is arranged by request. The separate Cal.eu service stores and processes data within EU borders, but it requires a minimum of 50 users and is in early access through a waitlist opened in waves ^[3]. Customers can choose a region when creating an account and migrate existing accounts to EU servers. For a European team below 50 users, the realistic path is the US-hosted service under Cal.com's data processing terms. Confirm residency before you sign.

• Check your user count against the minimum. Fewer than 50 users means Cal.eu is not available on today's terms.
• Ask about the waitlist. Early access opens in waves, so get a date if EU hosting is a requirement.
• Read the DPA. For bookings, Cal.com acts as a processor under a DPA that forms part of the Terms for every account.
• Review subprocessors. Some process data outside the US. Check the list against your own policies.
• Plan for account closure. After closure there is an export window of at least 30 days, then deletion, normally within 90 days.

Integrations and CRM

Most teams buy Cal.com to feed a CRM, so test the integration with real records. Free already includes two-way Salesforce and HubSpot sync, which is unusual at that price. The deeper routing features come later. Round robin events can book straight with the Salesforce or HubSpot owner of a contact when the email is passed in the link, a waterfall of tiebreaker rules settles cases where several accounts match, and a routing trace shows why a booking went where it did. Close.com is also supported for owner-based assignment. Attio works only indirectly, through a calendar connected to both tools. Calendars cover Google, Outlook, Apple, Zoho, Exchange, CalDAV (in beta) and ICS feeds.

• Owner lookup. Pass a known contact's email into a round-robin link and confirm the meeting lands with the record owner. Then test an unknown email.
• Field write-back. Check which booking fields reach the CRM. Values can come from booking questions, routing form fields or UTM parameters.
• Cancellation behavior. By default the Salesforce event is deleted when a booking is cancelled. Change that if reports need the history.
• No-show sync. Marking a no-show in Cal.com can set a checkbox on the Salesforce event. Confirm your reports use it.
• Automation tools. Zapier, Make and more than 100 other direct integrations are listed. Confirm the exact trigger you need exists.

API and developer needs

Developers should check the current platform, not the one in older blog posts. API v2 is the REST API, and API v1 was shut down on April 8, 2026. API keys allow 120 requests a minute by default, which can be raised on request. OAuth clients need approval from Cal.com, and their access tokens last 30 minutes with scoped permissions. Webhooks offer more than 20 triggers, use HTTPS on the cloud and sign payloads with HMAC SHA256. A hosted MCP server lets AI assistants act on a calendar. One door has closed. The legacy Platform for managed users and white-label products takes no new sign-ups, and Atoms are in maintenance mode.

• Rate limits. Estimate peak calls per minute and ask for a higher limit before launch if 120 is tight.
• Authentication. Decide between API keys and OAuth, and leave time for Cal.com's OAuth approval.
• Webhook security. Verify signatures on every payload. Cloud endpoints must use HTTPS.
• Embeds. Event links, profile pages and routing forms can be embedded inline, as a pop-up or as a floating button.
• White label. If you planned to build a product on managed users, check with sales first; the Platform no longer accepts new customers.

Self-hosting versus cloud

Many buyers still expect a free self-hosted Cal.com. That option has changed. Since April 2026 the commercial product is closed source, and the free community edition is Cal.diy under the MIT license. Cal.diy keeps the scheduling engine, the app store framework, API v2, webhooks and CRM apps, but it leaves out teams, round robin, collective and managed events, organizations, routing forms, workflows, Insights, SAML SSO, SCIM and audit logs. Cal.com says Cal.diy is strictly for personal, non-production use and makes no security guarantees for it ^[4]. Commercial self-hosting is sold as an enterprise on-premises deal through sales.

• Do you need more than one host? If yes, Cal.diy is the wrong starting point.
• Do you have the skills? Cal.diy needs Node 18 or newer and PostgreSQL 13 or newer, plus real server and security administration.
• Is this production? Running Cal.diy in production goes against the vendor's own guidance.
• Read the history. Older pages that describe Cal.com as open source predate April 2026. Our Cal.com open source guide explains the split.

Apps for staff on the move

Hosts who live on their phones need to know what works away from a desk. Cal.com's Companion apps cover iOS and Android, browser extensions for Chrome, Firefox, Safari and Edge, and desktop apps for macOS, Windows and Linux. All are free and included on every plan, and each needs a Cal.com account. An older FAQ line says there is no mobile app. It is out of date. The FAQ does warn that the desktop app does not give the same experience as the browser and is updated less often. Test on the devices your team actually carries. Sales reps, recruiters and clinicians often check their schedule between meetings, not at a desk.

• Mobile workflow. Have two hosts check, reschedule and cancel a booking from a phone during the trial.
• Browser extension. Check that the extension runs in the browsers your reps use every day.
• Email embed. Test inserting available slots into a composed email, a quick way to offer times without leaving the inbox.

Support and SLA

Support depends heavily on the plan. The Terms list email and the help center as support channels, and they say an SLA applies only when written into an Order Form or another signed agreement. Organizations lists priority support among its features. Enterprise adds dedicated onboarding, engineering support, priority Slack support and an uptime SLA of 99.9%, with a 99.99% option. Smaller teams should judge support by the help center, which is detailed on routing, CRM and billing topics. If your bookings drive revenue every hour, a written SLA is the only real guarantee. Ask what applies to your plan.

• Read the help center first. Search it for your three most likely problems before you buy.
• Get the SLA in writing. No signed agreement means no SLA, whatever a sales page says.
• Check the billing owner. The FAQ says the person paying must be the team owner, which matters for finance teams.
• Note the security scope. Vulnerability reports go through Bugcrowd, with only the QA environment in scope.

Migration from Calendly

Switching from Calendly is the most common route into Cal.com, and the vendor courts it directly. Free includes a one-click import of Calendly events, and Cal.com advertises an offer to credit the full value of a current Calendly contract toward the first year, with terms attached. Enterprise teams of 30 or more users get a dedicated migration team, typically over one to two weeks, priced by quote. Two Calendly facts matter. Calendly does not currently comply with HIPAA, so clinics leaving it gain an option, and its fees are non-refundable under its Customer Terms. For plan-by-plan detail, see Cal.com vs Calendly.

• Import, then inspect. Run the importer and check every event type's durations, buffers, questions and limits against the original.
• Rebuild routing by hand. Plan time to recreate routing forms and round-robin rules, then test them with real cases.
• Reconnect calendars and CRM. Each host reconnects calendars, and admins reconnect Salesforce or HubSpot with the right ownership rules.
• Time the cutover. Ask about the contract credit before cancelling Calendly, and switch links on embeds, signatures and email templates on one day.

The bottom line

Cal.com rewards buyers who arrive with answers. Count the people who host bookings, decide whether you need one team or several, estimate your text and AI call volume, and settle HIPAA and data residency before the trial clock starts. Most teams will land on Teams; companies with several teams, SSO needs or ten or more clinicians should price Organizations. Treat Cal.diy as a personal tool, not a free version of the cloud product. For the full cost picture, read our Cal.com pricing guide.