Reports overview
The reports module gathers the numbers from reservations, vouchers, guests and team into one dashboard — on the web and in the manager view of the mobile app.
Reports is its own module in the module catalog. Once subscribed, it shows up as "Dashboard" on the webapp module picker; managers additionally get the key numbers in the mobile app under "Reports".
The four views
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| Overview | view | — | — | The day and week picture: covers, booking state, utilization, no-show rate — the numbers that matter before service. |
| Revenue | view | — | — | Revenue metrics from sold vouchers and tickets, redemptions and outstanding voucher liability. |
| Guests | view | — | — | Guest metrics: new vs. returning guests, visit frequency, segments, sources (widget, phone, walk-in, AI agents). |
| Operations | view | — | — | Operational metrics: peak hours, table utilization and dwell time, shift and time-tracking summaries. |
Every reservation carries a structured source (reservation_sources) — widget, booking page, phone, walk-in, Reserve with Google or an AI agent like ChatGPT. Every report can be filtered by it, so you can see which channel actually brings guests.
Reports in the mobile app
Managers get a compact reports view with the daily KPIs in the team app — meant for a glance between services, not as a replacement for the web dashboard. The detailed breakdowns and filters stay in the webapp.
Who sees what
Reports is an admin and manager surface. Employees only see the module when it has been explicitly assigned to them — like every module, assignment works per person or group. Neo answers metric questions only within the rights of the asking user.