Choose an appointment recurrence frequency
Select weekly, monthly, yearly or custom recurrence based on the actual service schedule.
What this feature does
Select weekly, monthly, yearly or custom recurrence based on the actual service schedule. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Standard frequencies advance the next occurrence by one week, month or year.
Custom mode combines an interval number with day, week, month or year units.
The generated date remains subject to blocked-date and availability validation.
Step-by-step workflow
- Open recurrence settings.
- Choose Week, Month, Year or Custom.
- Review how the next date will move from the parent.
- Set cycles.
- Save and inspect the displayed recurrence summary.
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
- Monthly dates can behave differently around short months.
- Annual recurrence can cross daylight-saving changes.
- A valid recurrence date can still be skipped for unavailability.
- 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.
