Configure Google Meet recording, waiting and reminder defaults
Follow this guide to set the module's default meeting options for new eligible Google Meet appointments. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
What you’ll accomplish
Set the module's default meeting options for new eligible Google Meet appointments. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The settings include defaults for enabling Meet, recording-related preference, waiting-room behaviour and reminder options supported by the module.
These values are applied when the module builds eligible Google conference event data.
Actual Google Workspace capabilities can depend on the connected account and its licence.
Follow these steps
- Go to Google Meet settings.
- Check auto-enable, recording, waiting and reminder defaults.
- Select the organisation-approved values.
- Save.
- Create a test meeting and verify actual Google behaviour.
Fields and decisions to review
How to confirm it worked
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
- Do not promise a Google capability unavailable to the account.
- Check privacy and recording consent requirements.
- Test defaults after Google policy changes.
- 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.