Cal.com review

Cal.com is scheduling software built around booking links: you share a page, and invitees choose from your available times. It also handles team scheduling, reminders, lead routing, and booking through website embeds or an API. That makes it more than a personal calendar link tool, particularly if you need to direct incoming requests to different people.

Teams can use forms and round-robin scheduling to route leads, while workflows send reminders and follow-ups. Cal Video is available for meetings, and developers can connect booking flows through API v2. Cal.com also supports AI agents that check availability and book through its API; that does not mean every agent setup will automatically handle changes to existing bookings. One Reddit discussion about an agent integration describes trouble with rescheduling and cancellations, with a commenter pointing to the need to look up the existing booking first.

The main draw is range. Cal.com covers personal booking links, team availability, routing, reminders, embeds, and API-based booking in one product. That gives small teams room to build a more involved intake flow without treating every booking as a separate tool or process.

The free Individuals plan is unusually clear on the basics: the pricing page lists one user, unlimited links and calendars, email and SMS notifications, 100+ app integrations, and no usage limits. That is enough to make Cal.com a credible option for a solo operator who wants to publish booking links without paying per month.

For teams, the listed features include:

• Round-robin scheduling and one team with shared availability on Teams.
• Routing forms and booking analytics on Teams.
• Unlimited sub-teams and role-based permissions on Organizations.
• SAML SSO and SCIM, plus listed SOC 2, HIPAA, and ISO 27001 compliance, on Organizations.

API access and embeds also make Cal.com more adaptable than a basic booking page when a company wants to put scheduling into its own site or workflow.

The biggest price catch is that the pricing page shows Teams at $12 per user per month and Organizations at $28 per user per month only with yearly billing. It does not publish monthly-billing prices. Teams includes one team with shared availability; companies needing unlimited sub-teams, SAML SSO, or SCIM have to look at Organizations. Enterprise pricing is custom and annual, with no public figure to compare.

The free plan is limited to one user, so it is not a free team tier. The page lists a 14-day free trial, but the published pricing details do not specify which plan or features it covers. Check the terms before treating it as a way to evaluate paid team functionality.

There is also an open-source question for buyers who self-host or value an open codebase. Reddit threads criticize Cal.com’s reported move to close parts of the product and question its licensing and security rationale. Those are user discussions, not independent confirmation of the claims, but they are worth weighing if open-source status is part of your reason for choosing Cal.com.

Cal.com’s Individuals plan is free and includes one user, unlimited booking links and calendars, email and SMS notifications, and 100+ app integrations. The pricing page also lists a 14-day free trial.

Teams costs $12 per user per month with yearly billing. It includes one team, shared availability, round-robin scheduling, routing forms, booking analytics, and custom APIs. Organizations is $28 per user per month with yearly billing—a $16-per-user jump from Teams—and adds unlimited sub-teams, SAML SSO and SCIM, compliance certifications, role-based permissions, and additional APIs. Monthly-billing prices for either paid plan are not published.

Enterprise has custom annual pricing; the page lists dedicated support, an SLA, and a dedicated database, but no price. The published pricing details list no separate add-on prices. Budget by seat: the $12 and $28 figures are per-user monthly equivalents on annual billing, not published month-to-month rates.

The published materials don’t specify migration tools, import formats, or data-export options, so we can’t give a reliable estimate of the work involved or promise that bookings and settings transfer cleanly. Before switching, ask Cal.com what can be exported and imported, and check whether your current scheduler’s links, event types, routing rules, and workflows need to be recreated.

Cal.com lists booking links, routing forms, workflows, embeds, and API v2, so replacing those connections may add work if your booking process depends on them. Its API and embeds may also matter when leaving: confirm what data and integrations you can take with you rather than assuming portability. The published material includes no Reddit posts or comments, so we can’t responsibly report a user-reported pattern about why people leave. Open-source assurances are flagged as a concern in the review brief, but it provides no detail on licensing or the implications for a move.