Understand appointment cron reminders
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Ensure scheduled reminders, recurring appointments and feedback tasks are processed by the server cron at the required time.
What you’ll accomplish
Ensure scheduled reminders, recurring appointments and feedback tasks are processed by the server cron at the required time. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The module hooks into the CRM cron and queries records whose reminder, recurrence or feedback work is due.
Processing records notification/cycle state to avoid uncontrolled repetition.
A configured reminder cannot run if the CRM cron itself is not executing.
Follow these steps
- Verify the CRM cron command is installed and running.
- Configure a test appointment reminder.
- Wait for the due processing window.
- Check CRM logs, appointment activity and delivery.
- Test recurrence and feedback 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 create a second cron without understanding the existing schedule.
- Timezone affects when records become due.
- Review failures without repeatedly resetting notification state.
- 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.