Review staff performance and popular services
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 provider and service report sections to understand workload and demand without treating counts as standalone quality or revenue measures.
What you’ll accomplish
Use provider and service report sections to understand workload and demand without treating counts as standalone quality or revenue measures. It uses Pixie CRM's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How it works
Staff performance groups appointment outcomes by assigned provider.
Popular services groups appointment volume by service relationship.
Both depend on consistent provider/service assignment and accurate status records.
Follow these steps
- Select the reporting period.
- Check provider appointment and completion data.
- Check popular-service ranking.
- Compare with cancellations, no-shows and feedback.
- Go to source records before making operational decisions.
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
- High volume does not automatically mean high quality.
- Service price is not the same as recognised revenue.
- Missing assignments can distort grouping.
- 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.