Create a recurring appointment
Configure a parent appointment to generate future appointments at a supported interval.
What this feature does
Configure a parent appointment to generate future appointments at a supported interval. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
The create flow saves the initial appointment and its recurrence settings.
Future records are not all created immediately; the cron processes the next due recurrence.
Each generated record uses the parent relationship, provider, service, attendees and copied custom fields subject to availability.
Step-by-step workflow
- Create the initial appointment.
- Enable Recurring.
- Choose frequency, interval and cycles.
- Save and verify recurrence details on the parent.
- Wait for/test cron and inspect the first generated record.
Important fields and decisions
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
- Do not delete the parent without reviewing future generation.
- Choose a start time that is normally available.
- Test custom fields and attendees on the first child.
- 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.
