Send an appointment reminder early
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Manually send a reminder before its scheduled cron time when operational circumstances require earlier participant contact.
What you’ll accomplish
Manually send a reminder before its scheduled cron time when operational circumstances require earlier participant contact. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The detail action can trigger an appointment reminder manually under permitted access.
It uses the configured message channels and appointment data rather than changing the scheduled start.
Notification state and history should be reviewed to avoid unintended duplicate messages.
Follow these steps
- Go to the appointment.
- Verify recipient details and current schedule.
- Select the early/manual reminder action.
- Verify the intended channel.
- Check activity and delivery results.
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
- Check whether an automatic reminder is still due later.
- Do not send repeated reminders without reason.
- Update the appointment before reminding if timing changed.
- 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.
