For AI agents: the complete documentation index is available at https://docs.clickmax.dev/en/llms.txt, the full documentation bundle is available at https://docs.clickmax.dev/en/llms-full.txt, and this page is available as Markdown at https://docs.clickmax.dev/en/features/contacts/booking-link-verify-contact.md.
  • English

      • How do I require leads to verify their email or phone before booking?

      On the schedule, turn on Verify contact before booking. From then on, anyone booking through the public link gets a 6-digit code by email, SMS or WhatsApp and can only book after entering it. Meetings arrive with a contact the person actually uses — and reminders have somewhere to go.

      Before you start

      • The schedule needs its public link turned on (Commercial → Scheduling → Agendas → edit the schedule → General).
      • To send the code by email, the workspace needs a verified sender. If there is none, connect an email domain in Settings → Connections.
      • To send the code by WhatsApp, the workspace needs a connected official WhatsApp number and an Authentication template approved by Meta on that number.
      • The option is off on every schedule by default.

      1. Turn verification on

      1. Open the schedule and go to the Form tab.
      2. Turn on Verify contact before booking.
      3. In Send the code by, choose Email, SMS or WhatsApp.
      4. If you chose Email, select the Email sender. The schedule won't save without one.
      5. If you chose WhatsApp, select the WhatsApp number and then that number's Authentication template. The schedule won't save without a template.
      6. Save.

      If the number has no approved authentication template yet, click Create authentication template right there: the template is created on the chosen number, goes through Meta review and shows up in the list once approved. Until it is approved, the public page can't send the code.

      With SMS or WhatsApp, the phone number becomes required on the public form, even if you turned the field off or left it optional.

      2. What the lead sees

      1. Picks a time and fills in the form.
      2. Clicks Send code. The page shows where the code went (email or phone partially hidden).
      3. Types the code and clicks Confirm and book.

      The code is valid for 10 minutes. The lead can ask for another one with Resend code (after 1 minute) or go back with Edit details to fix the form.

      3. Where it shows up in the CRM

      • Contact history: each code sent and each verification becomes a line in the lead's timeline.
      • Meeting: when you open the meeting, the management link panel shows Contact verified by code on with the verification date and time. Meetings booked without the code don't have this mark.
      • The code is also recorded in the lead's conversation, like any other message sent to them.

      Troubleshooting

      • "This email is already registered with another phone number": the lead already exists in the CRM with a different number. SMS and WhatsApp codes only go to the phone on file — ask the person to use that number or update the lead's phone in the CRM.
      • "We couldn't send the code right now": the send was refused. Check that the email sender is still verified, that the WhatsApp authentication template is still approved and the number connected, that the lead hasn't blocked messages on that channel, and that the workspace can send emails, SMS or WhatsApp normally.
      • "Code limit reached": each lead can request up to 5 codes per hour on the same schedule. After 5 wrong codes, a new one is required.
      • A link with skipForm=1 stopped confirming on its own: with verification on, the lead always has to enter the code — the form shows up pre-filled and the booking only happens after the code.