Get started

Cal.com

The Cal.com connection gives a ThunderPhone agent scheduling tools it can use during a conversation. An attached agent can list event types, check availability, create a booking, and cancel a booking. This lets a caller move from a spoken scheduling request to a recorded booking without a staff member copying details between the call and the calendar system.

The connection is permission-gated and agent-specific. Connecting a Cal.com account does not give every agent access, and the account connection does nothing on calls until you attach it to an agent.

What the Cal.com connection does

Cal.com is a native app connection in ThunderPhone. You connect it under Connections → Apps with an API key. ThunderPhone validates the key before encrypting and saving it. You can connect more than one account, then choose the relevant connection for each agent.

The available operations are grouped by permission. Listing event types and checking availability are read-style operations. Creating bookings is a separate operation, while management access controls booking changes such as cancellation. An operation that is turned off is not offered to the agent as a tool during calls.

The agent decides when to use an enabled tool based on the conversation and its prompt. A precise prompt should tell it which event type to use, which caller details to collect, when to read choices aloud, and when it must ask for confirmation before creating or canceling anything.

Typical call flows

New appointment. In appointment scheduling by phone, the caller explains what they need. The agent lists the applicable event types, checks availability, offers suitable openings, confirms the selected time and required contact details, and creates the booking. It should not promise a slot before the booking tool returns a successful result.

Cancellation request. For rescheduling and cancellations, the agent identifies the relevant booking and confirms the caller's intent before canceling it. If the workflow requires a change that the enabled tools cannot perform safely, the agent should route the call to a person instead of improvising.

Front-desk coverage. A virtual front-desk receptionist can answer routine questions from its approved knowledge and use Cal.com when the caller wants to book. Requests involving exceptions, disputed policies, or unavailable event types should remain with staff.

Setup outline

  1. In Cal.com, obtain the API key for the account you want the phone agent to use.
  2. In ThunderPhone, open Connections → Apps, choose Cal.com, paste the key, and select Validate and connect.
  3. Open the saved connection and review the allowed operations. Keep change permissions off unless the call flow truly needs them.
  4. Open the agent in the builder and attach the Cal.com connection under Connected apps.
  5. Add prompt instructions for event-type selection, required caller fields, confirmation language, tool failures, and human escalation.
  6. Test availability lookup, a successful booking, no available times, a cancellation, and an invalid or unavailable booking before deploying the agent changes.

Operating limits

The integration exposes scheduling actions; it does not define your booking policy. Your prompt and Cal.com configuration remain responsible for which services callers may book and which details are required. Treat spoken dates, names, email addresses, and phone numbers as values that need confirmation before a write action.

For background on the workflow, see appointment setting. If you use the integration to support no-show reduction, keep reminder and follow-up rules separate from the live booking permissions described here.