Skip to content

Reports

The Reports section (main menu → Reports) is a self-serve report builder. Where the Analytics dashboards answer fixed questions, Reports let you ask your own - pick what to measure, how to slice it, and how to chart it - then save it, arrange saved reports into dashboards, or ask in plain English.

It has two tabs: Builder and Dashboards.

At the top of the builder, a Build method toggle picks how you compose a report: Build manually (the default) or Ask Aimy to describe it in plain English. The Report builder is the AI-assisted surface, so its menu link carries a ✨ sparkle.

In Build manually mode you set up a report from a few controls, with a live preview updating as you go:

Control What it does
Measure The number to report - e.g. Bookings, Covers, Revenue (see the full list). Add a 2nd or 3rd measure to compare side by side.
Break down by The dimension to split by - Date, Weekday, Venue, Status, Type, Currency, Guest, Campaign or Visit frequency (some depend on your permissions).
Group dates by Day, week or month (when breaking down by date).
Then by An optional second breakdown, drawn as stacked series.
Chart Bar, stacked bar, line, area, pie, donut, heatmap, table or a single stat.
Sort & limit Sort by value or label, and keep the Top N (or Bottom N).
Filters Narrow by venue, booking status, source/type, event, party size or guest segment.
Date range Presets (last 7/30 days, this/last month, year to date) or a custom from/to.
Compare to Nothing, the previous period, the previous week (same day last week), or the previous year - shown as a delta.

Relative date ranges stay dynamic: a report saved as “last 30 days” always re-runs against today when you open it.

Visit frequency is a special breakdown: instead of grouping by a field, it buckets guests by how many times they’ve visited in the report window - 1, 2, 3, 4–5, 6–10 and 11+ visits - so you can see, say, covers or revenue split across one-time and repeat guests.

The guest segment filter groups guests by lifecycle - Loyal, Active, New, At risk and Lapsed - based on how recently and often they visit. It’s a lifetime property, so it’s independent of the report’s date window.

To get going fast, there are one-click standard reports you can open and then tweak:

  • Bookings over time
  • Covers by venue
  • Covers by weekday
  • Bookings by status
  • Revenue by venue
  • Revenue by currency
  • Key-spend revenue by venue
  • Add-on sales by venue
  • Top guests by covers
  • Average rating over time
  • Average rating by venue
  • Reviews by venue

Save a report with a name and it’s shared with your team by default, so everyone works from the same numbers. The saved-reports list is searchable and filterable by owner; only the owner can edit or delete a report. A saved report re-runs live each time - and re-checks permissions, so a teammate only ever sees what their role allows.

On the Dashboards tab you can arrange several saved reports into a single view:

  1. New dashboard - give it a name.
  2. Optionally share it with your team.
  3. Tick the saved reports to include - they appear in the order you pick them.

Each panel spans between 1 and 4 columns of the dashboard grid - drag a panel’s right edge to resize it, and a small width badge shows its span (e.g. 3/4). You can pin a dashboard as a private favourite so it floats to the top of your list - pinning is per-person and doesn’t affect anyone else. When a shared dashboard is opened, each panel re-checks the viewer’s permissions, so people only see the panels they’re allowed to run.

Switch the builder’s Build method to Ask Aimy to request a report in plain English - for example:

revenue by venue this month

no-show % by venue last month

covers per day over the last 30 days as a line chart

Pressing Ask Aimy (or one of the example prompts) opens the Aimy chat panel, where Aimy answers as a conversation you can keep asking follow-up questions in. The report it builds also appears in the Preview box here, with Save to Builder to keep or refine it. It understands time phrases, breakdowns, comparing two measures, and even a requested chart type.

Aimy takes into account the venues selected here, so a follow-up question stays scoped to them - naming a different period or venue in your question overrides it.