Quick answer
Calendly's own SMS notifications (booking confirmations, reminders) are sent on Calendly's infrastructure under its registrations, with the invitee's notification opt-in. The moment your business texts those same numbers for marketing, follow-ups, or rebooking outside Calendly, you need your own 10DLC campaign and separate documented marketing consent.
Calendly made scheduling self-service, and its text reminders meaningfully cut no-shows. Businesses then look at that pile of phone numbers and think: re-engagement campaigns.
That thought is where compliance lines get crossed. A reminder about an appointment the person booked is one consent universe; a promo about your spring offer is another. The Calendly checkbox covers the first and says nothing about the second.
How SMS Works With Calendly
When an invitee books and opts into text notifications, Calendly sends the confirmation and reminder messages itself; you do not register anything for that traffic.
Any texting your business initiates outside Calendly's notifications, from a CRM, an SMS platform, or a synced workflow, rides on your own 10DLC registration and your own consent capture. Calendly's booking data flowing into your stack via integrations is a phone-number source, not a consent source.
How to Set Up 10DLC for Calendly
- 1
Use Calendly notifications for what they are
Booking confirmations and reminders inside Calendly need no registration from you. Keep that traffic inside Calendly's own sending.
- 2
Register your own campaign for outreach
Follow-ups, rebooking nudges, and promotions sent from your tools require a 10DLC brand and campaign with your SMS provider, with a use case matching that traffic.
- 3
Add marketing consent at or after booking
Add a custom booking question or a post-booking consent page with an unchecked marketing-SMS checkbox and full disclosure. Notification opt-in does not transfer.
- 4
Separate the audiences in your CRM
Tag contacts by consent scope: booking-notification-only versus marketing-consented. Workflows must only text the second group.
Where Calendly Setups Fail TCPA Review
Carrier approval is step one. These are the consent gaps that turn into demand letters.
Invitee phone numbers sync into CRMs where nothing marks them as notification-only
Calendly's SMS opt-in covers its event notifications, not your marketing program
Custom booking questions rarely include disclosure language even when they ask about texting
No evidence exists of what the invitee agreed to beyond Calendly's own records
How OptInFix Closes the Gaps on Calendly
Post-booking consent step
Send invitees to an OptInFix consent page from your confirmation flow to convert notification contacts into provably marketing-consented contacts.
Consent-scoped syncing
Only contacts who completed the marketing opt-in flow into your texting audience, with the evidence vaulted per contact.
Proof when a no-show complains
If a past invitee claims your rebooking text was unsolicited, you produce the session-recorded consent or you confirm they were correctly excluded.
10DLC for Calendly: Frequently Asked Questions
Do I need 10DLC for Calendly's text reminders?
No. Calendly sends its booking notifications on its own infrastructure and registrations. Your obligations start when your business sends texts outside Calendly's notification system.
Can I market to phone numbers collected through Calendly bookings?
Not without separate marketing consent. The invitee's notification opt-in covers appointment messages about that booking, not promotional outreach from your business.
How do I add marketing consent to a Calendly flow?
Use a custom booking question with proper disclosure, or route invitees to a dedicated consent page after booking. Either way, keep evidence of the specific marketing consent.
Are appointment reminder texts from my own system exempt from 10DLC?
No. Reminders you send from your own tools are A2P traffic requiring a registered campaign, typically under a Customer Care or Account Notifications use case.