The short answer
- Consider hosted Cal.com when scheduling links, team availability and routing forms fit the workflow.
- The yearly pricing view lists Teams at $12 per user per month and Organizations at $28; Organizations adds routing by custom variables.
- Distinguish hosted plans, Platform and the self-hosted community edition before making deployment or support assumptions.
Choose the hosted plan
Cal.com pricing lists a free individual plan, Teams at $12 per user per month on yearly billing, and Organizations at $28 per user per month on yearly billing. Teams includes round robin and routing forms; Organizations adds routing by custom variables and multiple sub-teams.
Count hosts and map each route to the required plan. Ask for Platform pricing and terms if embedding scheduling in your own product: a hosted Teams subscription is not a substitute for confirming the appropriate Platform agreement.
Seat billing guidance counts the owner and pending invites as seats. High-water-mark billing can charge for the peak count in the billing period; active-user billing and minimum commitments depend on the plan. Confirm the billing model and any minimum before estimating costs.
The pricing page lists routing forms with Teams, while Cal.com’s FAQ also lists routing forms for free users. The sources do not settle the difference; verify the exact individual or team routing capability and any form or submission limits for your account.
Test the route and Salesforce owner
Cal.com’s Salesforce guide documents a setting to book directly with the attendee’s Salesforce owner on round-robin event types. It also describes record creation settings and a routing trace where trace data exists. Confirm your integration and plan entitlement.
Use synthetic new and existing contacts, an account with multiple possible matches, and an owner outside the eligible hosts. Inspect the chosen host, routing trace and CRM record. The guide describes fallback to standard round robin when account-owner host filtering leaves no candidates in the documented account-resolution path; test your own path rather than assuming every fallback behaves the same way.
Distinguish deployment and support
Cal.diy documentation describes a community-maintained self-hosted edition intended for personal, non-production use, with a different feature set from commercial Cal.com. It directs commercial users to hosted Cal.com or enterprise on-prem access. Verify the current license, deployment rights, upgrade responsibilities and support directly before choosing a deployment.
Treat hosted individual, Teams and Organizations subscriptions, Platform for embedded use, and self-hosted editions as separate offerings. Ask which product and contract cover your use, integrations and support expectations.
Cal.com’s engineering note says the Cal.diy community fork removed the routing forms package and team features. Do not assume that a hosted Teams workflow or its support transfers to a self-hosted edition.
For hosted access, Cal.com’s Organizations page lists SAML SSO and SCIM. Confirm the identity provider, plan and provisioning behavior for your account; Cal.diy is a separate self-hosted edition.
Verify downstream changes
Cal.com webhooks document booking and host-reassignment events. If your team sends these events into a CRM, inspect the receiver as well as the scheduling page. Test a booking, reschedule, cancellation and host change and reconcile the resulting record.
Assign a person to monitor failures and decide how duplicate or missing events are handled. Confirm webhook fields and recovery behavior in your own integration.
The calendar setup guide calls for calendar authorization and selection of conflict and destination calendars. Cal.com’s privacy policy says data is processed in the US and some subprocessors work elsewhere. Review requested permissions, connected apps and transfer terms for the information your forms collect.
Compare the same routing cases
Calendly combines scheduling with qualification and plan-dependent CRM lookup. Chili Piper emphasizes a broader inbound and ownership workflow at a platform minimum. Compare actual host count and the same new-lead, existing-owner and fallback tests.
Common questions
Does Cal.com Teams include routing forms?
Cal.com pricing lists routing forms and round-robin scheduling on Teams.
Is Cal.diy the same as hosted Cal.com?
Cal.diy documentation describes a separate community-maintained edition intended for personal, non-production use, with different features and support.
Sources and scope
We read the linked vendor pricing and documentation on November 5, 2026.
This is a documentation-only assessment. We have not tested scheduling, routing, CRM integrations or support. Confirm current terms and behavior in your own environment.
Inclusion and corrections are free; sponsorship does not determine our conclusions.
Sponsorship never changes this page. How we research.
Sources
- Cal.com pricing
Checked 2026-11-05. Hosted individual, Teams and Organizations plans and routing features.
- Cal.com Salesforce integration
Checked 2026-11-05. Salesforce matching, owner routing and routing trace.
- Cal.diy self-hosting
Checked 2026-11-05. Community edition, intended use and feature differences.
- Cal.com webhooks
Checked 2026-11-05. Booking and reassignment events.
- Cal.com: seat billing
Checked 2026-11-05. Seat counting and billing models.
- Cal.com: FAQs
Checked 2026-11-05. Free-plan routing-form statement alongside pricing-page discrepancy.
- Cal.com: Cal.diy technical changes
Checked 2026-11-05. Community edition changes and removed routing features.
- Cal.com: privacy policy
Checked 2026-11-05. Processing locations and connected-app data handling.
- Cal.com: connect your calendar
Checked 2026-11-05. Calendar authorization and conflict and destination calendars.
- Cal.com: Organizations
Checked 2026-11-05. Hosted Organizations plan, SAML SSO and SCIM.