Mark an appointment In Progress
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Move an approved or pending operational record into active delivery when the appointment begins.
What you’ll accomplish
Move an approved or pending operational record into active delivery when the appointment begins. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
The status action validates permission and the appointment record before changing the stored status to in-progress.
The update becomes visible in summary cards, table filters, calendar styling and reports.
The module records lifecycle history so staff can distinguish scheduled work from work actively being delivered.
Follow these steps
- Go to the appointment at the start of delivery.
- Verify the customer, service and provider.
- Select In Progress.
- Save or confirm the status action.
- Check the record appears in the In Progress filter.
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 In Progress as a substitute for approval when approval is required.
- Avoid leaving finished appointments in this state because reports will be inaccurate.
- Record meaningful notes separately where operational context is needed.
- 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.