Configure custom appointment recurrence
Repeat an appointment every specified number of days, weeks, months or years. 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
Repeat an appointment every specified number of days, weeks, months or years. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow works
Custom recurrence stores an interval value and period unit.
The cron adds that interval to determine the next candidate date.
The candidate is checked for blocked dates and slot availability before a child is created.
Follow these steps
- Enable recurrence.
- Select Custom.
- Enter the interval number.
- Select day, week, month or year.
- Set cycles, save and verify the next candidate.
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
- Avoid zero or ambiguous intervals.
- Test month-end custom recurrence.
- Document skipped occurrences caused by unavailable slots.
- 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.
