Skip to main content

Email Verification for Appointment Bookings

Add an extra layer of security to your appointment bookings with email verification. Reduce no-shows, prevent spam bookings, and ensure reliable communication with your participants.

Written by Fernando Figueiredo
Updated over 5 months ago

Email verification (also known as double opt-in) requires participants to verify their email address before completing an appointment booking. After requesting an appointment, participants receive a confirmation code via email that must be entered to finalize the booking.

Email verification is available to all Zeeg users across all plans.

Key Features

  • Verification process: Participants receive a confirmation code via email after requesting an appointment

  • Simple completion: The code must be entered to complete the booking

  • Individual control: Can be activated or deactivated for each scheduling page independently

  • Automatic workflow: Once enabled, the verification process runs automatically

Benefits

Reduce No-Shows. Only people with verified, working email addresses can book appointments. This ensures participants are reachable and more committed to attending.


Legal Compliance. Meet current legal requirements for appointment confirmations and reminders. Email verification provides greater legal certainty when communicating with your participants.


Prevent Spam Bookings. Protect your calendar from unwanted, erroneous, or malicious bookings. The verification step acts as a barrier against automated spam.


Improve GDPR Compliance. Verify that contact data is accurate and belongs to the person making the booking, helping you maintain compliance with data protection regulations.

Ensure Reliable Communication. Confirm that participants are reachable at the email address they provided, ensuring your appointment confirmations and reminders reach them.

How It Works

The verification process

  1. A participant fills out your booking form and selects a time

  2. Instead of immediately confirming the appointment, Zeeg sends a verification code to their email

  3. The participant enters the code on the booking page

  4. Once verified, the appointment is confirmed

  5. Appointment confirmations and reminders are sent as usual

For participants

The process is quick and straightforward:

  • Request appointment → Receive code via email → Enter code → Booking complete

  • The entire process takes just a few moments

How to Enable Email Verification

  1. From your Dashboard, find the scheduling page where you want to enable verification

  2. Click on the three dots and select Edit

  3. Navigate to Advanced scheduling settings

  4. Look for the option Enable email verification

  5. Toggle it on

  6. Click Save to apply your changes

Email verification will now be active for all bookings made through this scheduling page.

Individual control per scheduling page

You can choose which scheduling pages require email verification. For example:

  • Enable it for public-facing pages with high spam risk

  • Disable it for internal team scheduling or trusted client bookings

  • Use it selectively based on your specific needs

Common Use Cases

  • Public booking pages: Protect high-visibility pages from spam and fake bookings

  • High-value consultations: Ensure serious commitment for valuable time slots

  • Limited availability: Prevent wasted slots from unverified or incorrect bookings

  • Legal/Medical appointments: Meet industry compliance requirements

  • Paid services: Verify contact information before confirming paid appointments

  • Group events: Ensure all participants have valid email addresses for communications

Best Practices

  • Enable for public pages: Use verification for any scheduling page shared publicly

  • Consider your audience: For trusted or internal users, verification may not be necessary

  • Test the experience: Book a test appointment to see how the verification process works for your participants

  • Clear communication: Your booking page should indicate that email verification is required

Did this answer your question?