Recurring appointments overview
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to use Pixie CRM recurrence to generate future appointment records through cron while preserving cycle limits, service/provider relationships and individual appointment histories.
What you’ll accomplish
Use Pixie CRM recurrence to generate future appointment records through cron while preserving cycle limits, service/provider relationships and individual appointment histories. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
A recurrence parent stores frequency, custom interval, total cycles or unlimited mode and the number of cycles already generated.
The CRM cron calculates the next occurrence and creates a new appointment only when the date is not blocked and the slot is available.
Generated appointments copy supported custom fields, attendees and service relationships while resetting child recurrence, feedback, invoice and reminder-notification state.
Follow these steps
- Create or open the parent appointment.
- Enable recurrence and choose frequency.
- Set custom interval and cycle limit where needed.
- Save and confirm cron operation.
- Check each generated child appointment separately.
Settings to check
Check it worked
After this workflow completes, Pixie CRM 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 Pixie CRM 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.
Common mistakes to avoid
- Do not use recurrence without a working cron.
- Review future availability and blocked dates.
- Each generated appointment is an operational record requiring its own status management.
- 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.