Britixo CRMBritixo CRM Enterprise Help Centre
Appointments & Scheduling · How-to guide

Enable reCAPTCHA on the public booking form

Reduce automated submissions by activating the module's reCAPTCHA check with the CRM's configured Google keys.

Audience: Staff who manage appointmentsFeature: reCAPTCHAModule v1.3.6
Feature pathAppointments > Booking Form / Settings and Setup > Google
Before you beginThis guide follows the supplied Britixo Appointments & Scheduling module version 1.3.6. The relevant access is Appointments: View. A menu, button, provider, time slot or client action can remain hidden when the signed-in user lacks the required permission, the module setting is disabled, the related record is in an ineligible state, or availability validation rejects the request.

What this feature does

Reduce automated submissions by activating the module's reCAPTCHA check with the CRM's configured Google keys. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.

How the module flow works

The public view renders reCAPTCHA only when the module option is enabled and the CRM has valid site and secret keys.

The public controller verifies the submitted token before creating an appointment.

Missing or invalid keys can block legitimate bookings or leave the challenge absent.

Step-by-step workflow

  1. Configure the CRM reCAPTCHA site and secret keys.
  2. Enable reCAPTCHA in Appointments booking settings.
  3. Save.
  4. Open the form signed out and complete the challenge.
  5. Test rejection with an incomplete or invalid challenge.

Important fields and decisions

Site keyPublic key rendered in the booking form.
Secret keyServer-side verification credential.
Module optionEnables reCAPTCHA for appointment booking.
Verification responseToken validated before record creation.

What happens after completion

After this workflow completes, Britixo keeps the appointment and its supported relationships connected. Reopen the appointment and verify the saved status, date, timezone, customer or lead, service, provider, attendees, reminder state, calendar or meeting reference, invoice reference and history that apply to this feature. External email, SMS, Google, Microsoft or payment outcomes must be checked separately from the Britixo database save.

  • Open the saved appointment and confirm the final status and source.
  • Check the participant, provider, timing and timezone from the full detail page.
  • Review the relevant table filter, calendar, history, report or linked invoice instead of relying only on a success message.

Controls, checks and common mistakes

  • Never expose the secret key in documentation or page source.
  • Use keys authorised for the live domain.
  • Test after changing domains or subdomains.
  • Use the least destructive correction and retain the appointment history when the booking existed operationally.
  • Never bypass a permission, availability, approval, client-access or verification control by changing an unrelated route or setting.
Scheduling and data safetyAppointment changes can notify customers, reserve provider time, update remote calendars, create meeting links or invoices and alter reports. Confirm the exact record, timezone, status and recipients before saving.
Browse connected topics:booking formcustomersinvoicepaymentcheckreportapprovalappointmentschedulingserviceprovideravailabilityremindersfeedback
Allow guest appointment booking →Public booking form overview →Understand appointment data, public links and security boundaries →Troubleshoot public booking and Appointments permissions →Choose services shown on the public booking form →Customise the booking form heading and description →Enable the client-area booking link →Show provider email or phone on the public form →