Skip to main content
At Cal.com, you can send SMS and WhatsApp messages, use our AI-powered phone agent cal.ai, and run AI agent interactions — all powered by credits. While these services can be funded through various methods (e.g., organization-level billing), credits are one of the available ways to manage usage — especially for teams and smaller accounts.

​
Overview of credits

Credits are used as a flexible payment method for:
  • SMS messages (booking confirmations, reminders, updates)
  • WhatsApp messages (booking alerts, confirmations)
  • Cal.ai (AI-powered phone agent)
  • AI agents (automated scheduling interactions via the Platform API)
While many organization-level accounts may fund messaging centrally or directly via integrations like Twilio, credits serve as a prepaid way to power messaging and AI services, especially on smaller plans.

​
Credit Allocation by Plan Type

The number of messaging credits available to your account depends on your plan type:

​
Organizations (Enterprise)

  • 1000 credits per team member per month
  • Messaging costs are typically covered through your organization’s billing method
  • SMS/Whatsapp sending consumes credits (like on any other plan) and you can purchase more in your Organization billing settings.

​
Team plan

  • 750 credits per team member per month
  • Credits reset at the start of each billing cycle
  • You can purchase more credits from Team Settings as needed.

​
Free Users

  • No free credits included
  • You can purchase credits manually from your Billing Settings

​
Behavior when credit balance is exhausted

  • Low credit alerts: We’ll send email warnings when your balance gets low (all admins are notified for teams)
  • Exhaustion fallback:
    • If credits run out, SMS/WhatsApp messages will automatically stop
    • Cal.com will fall back to email delivery only for affected messages
This ensures bookings still go through, but real-time alerts may be delayed if recipients rely on SMS/WhatsApp.
Credits are not the only way SMS/WhatsApp are funded — they’re just the default mechanism for smaller accounts and teams

​
Messaging credits

​
Credit-based messaging costs

The cost depends on the recipient’s location and the delivery method:

​
🇺🇸 United States & 🇨🇦 Canada

  • SMS and WhatsApp messages are free on the Teams Plan in these regions
  • Credits are not deducted

​
🌍 Other Countries

  • One credit = $0.01 USD
  • The total credit cost per message is based on:
    • Twilio’s region-specific SMS rates
    • A standard 80% processing fee
📌 Example: If Twilio charges $0.05 per SMS to India, your effective cost is: 
0.05 + (0.05 * 0.8) = $0.09 = 9 credits
You can check up-to-date Twilio pricing here: Twilio SMS Pricing

​
Segment-based billing

Credits are charged per segment, not per message. Most SMS messages are broken into segments based on character count:
  • Standard segment: up to 160 characters
  • Messages with emojis or special characters: up to 70 characters per segment
Each segment is treated as a separate message, and credits are then calculated based on the information above. 📎 Want to check how many segments your message will use?
Use Twilio’s Segment Calculator to estimate credit usage before sending.

​
Cal.ai

Cal.ai pricing is based on credits, with each call consuming a set number of credits based on its length. The cost is 29 credits per minute, which equals $0.29 per minute.

​
AI agents

AI agents built on the Cal.com Platform API can consume credits for automated scheduling interactions. If you are building integrations using the Platform API, your AI agent activity is charged against your team or organization’s credit balance. Credits for AI agents are managed through the Platform API with two endpoints:
  • Check available credits — query your current balance before performing actions
  • Charge credits — deduct credits for AI agent usage, with optional idempotency support to prevent duplicate charges
AI agent credit usage is separate from Cal.ai phone call credits. Both draw from the same credit balance, but they are tracked as distinct usage types.