Request appointment rescheduling as a client
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Propose a new date and time through the client portal without directly overwriting the approved appointment.
What you’ll accomplish
Propose a new date and time through the client portal without directly overwriting the approved appointment. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The client controller validates contact access and captures the requested replacement date/time and reason.
The request remains pending until staff approve or deny it.
Staff approval must recheck provider availability before applying the new schedule.
Follow these steps
- Go to the appointment in the client portal.
- Select Request reschedule.
- Select or enter the proposed date/time and reason.
- Submit.
- Wait for the staff decision and revised confirmation.
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
- A request is not a confirmed new time.
- Do not choose a time outside available provider hours.
- Calendar invitations remain unchanged until staff approval.
- 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.