Review staff performance and popular services
Use provider and service report sections to understand workload and demand without treating counts as standalone quality or revenue measures.
What this feature does
Use provider and service report sections to understand workload and demand without treating counts as standalone quality or revenue measures. It uses Britixo's permission-aware appointment, availability, status and integration flow rather than an unconnected diary entry.
How the module flow 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.
Step-by-step workflow
- Select the reporting period.
- Review provider appointment and completion data.
- Review popular-service ranking.
- Compare with cancellations, no-shows and feedback.
- Open source records before making operational decisions.
Important fields and decisions
What happens after completion
After this workflow completes, Britixo 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 Britixo 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.
Controls, checks and common mistakes
- 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.
