Skip to content

Add customizable legal links/footer text directly above the booking confirmation button #30324

Description

@ekammerman

Is your proposal related to a problem?

Yes.

When using Cal.com as the booking/opt-in flow for SMS messaging, there is currently no apparent way to add custom text and hyperlinks immediately adjacent to the final booking/confirmation button.

This creates a compliance issue for businesses using their booking form as part of an A2P 10DLC registration. Twilio's A2P 10DLC requirements state that Terms of Service and Privacy Policy links must be clearly visible within or immediately adjacent to the opt-in/CTA.

Currently, these links can be included elsewhere on the booking page, such as in the event description, but that does not provide the same proximity to the final CTA and may result in the campaign being rejected during registration.

Describe the solution you'd like

Add an optional customizable text/footer area that appears immediately above or below the final "Confirm Booking" / submission button.

This area should support basic text formatting and hyperlinks so organizers can add disclosures such as:

"By submitting this form, you agree to our Privacy Policy and Terms of Service."

For example:

Privacy Policy | Terms of Service

Each link should be independently configurable.

Ideally, this would be configurable at the Event Type level so different booking forms can have different disclosures when necessary.

Describe alternatives you've considered

I considered placing the Privacy Policy and Terms of Service links in the Event Description, but this places them farther away from the final booking/confirmation CTA.

I also looked for a Footer, Custom Instructions, or similar setting within the current Event Type configuration, but I could not find a way to place custom content directly adjacent to the final booking button.

I also considered adding another checkbox at the very bottom (which might have to be what I do in the meantime), but requiring the user to checkmark one more box adds unnecessary friction. It just needs to be present, it doesn't need to be checkmarked.

Additional context

This is not simply a cosmetic or nice-to-have feature.

For businesses using Cal.com as part of an SMS opt-in flow, A2P 10DLC registration requirements require accessible Terms of Service and Privacy Policy links as part of the opt-in/CTA flow. Twilio specifically states that these links must be placed within or immediately adjacent to the opt-in/CTA and can cause registration to be rejected when they are located elsewhere on the page.

Having a simple configurable legal/disclaimer area near the final booking button would make Cal.com much easier to use for compliant SMS opt-in flows.

This feature would also be useful for other disclosures that need to appear immediately before a booking is submitted, such as cancellation policies, consent notices, or other terms.

Requirement/Document

Twilio A2P 10DLC documentation:

https://www.twilio.com/docs/api/errors/30564

https://www.twilio.com/docs/api/errors/30549

https://www.twilio.com/docs/api/errors/30550

Twilio's A2P 10DLC Campaign Onboarding Guide:

https://help.twilio.com/articles/11847054539547-A2P-10DLC-Campaign-Approval-Best-Practices

Activity

  1. added
    ✨ featureNew feature or request
    🚨 needs approvalThis feature request has not been reviewed yet by the Product Team and needs approval beforehand
    on Oct 8, 2026
  2. gracysinngh commented on Oct 9, 2026

    @gracysinngh

    Hi! I’d love to work on issue #30324. I plan to explore the existing Event Type settings and booking flow, then implement customizable legal text and links using existing components and patterns. I’d prioritize a simple, maintainable solution while keeping the booking experience unchanged. I’m happy to take ownership of this and would appreciate the opportunity. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    ✨ featureNew feature or request🚨 needs approvalThis feature request has not been reviewed yet by the Product Team and needs approval beforehand

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions