Skip to main content

What do the Analytics and ROI pages show?

The Analytics landing page, message volume split by type, the sentiment table, and how the ROI page separates revenue reporting from the upsells that still need a human action.

Written by Sam Dundas

Analytics is where Besty opens

Analytics is the landing page after login, and it is built to be read at the start of a shift.

The Analytics landing page, showing account overview, daily message volume by type, and average response times

Account Overview, and the number that answers billing questions

Three stats sit at the top: Live Listings, Total Locks and Total Revenue.

Live Listings shows enabled over total synced, for example 81 of 149. That single ratio is the fastest answer to two of the most common questions. "Why am I being billed for this many listings" is answered by the first number. "Why is this property not getting messages" is often answered by the fact that it is in the second number but not the first, so it is synced but not enabled.

Daily Message Volume

A stacked area chart with a date range, presets for 30, 60 and 90 days and 1 year, a Message Types filter, and a legend with per-type counts and a total.

The type split is the valuable part, because it separates Journey Messages, Dashboard, Autopilot, Offer and Broadcast. That breakdown answers "how much is Besty actually doing versus my team", which is otherwise guesswork. Autopilot volume against Dashboard volume is the ratio to watch over time.

Average Response Times

A bar chart broken out per team member. Useful for spotting whether one person is carrying the inbox, and for seeing the effect when Autopilot coverage changes.

The sentiment table

Beneath the charts sits a tabbed table with Listing, Guest and Mood columns.

The Stays table with mood chips and the issues extracted from each conversation

Mood renders as an emoji chip with bulleted issue summaries pulled out of the conversation, such as a missing amenity, a parking problem or a communication breakdown. Sentiment is derived from the tone and content of the conversation, not from a survey, so it needs no guest action.

Scanning this at the start of a shift is the intended workflow. It surfaces unhappy guests without anyone reading every thread.

The ROI page

ROI has two views, Overall and By Listing. Overall opens with a date range as chips, from last 7 days through to all time and a custom range, plus Export CSV.

ROI Overall, revenue by upsell type on the left and the transaction ledger on the right

Revenue is broken into cards per upsell type: total revenue, booking booster, early check-ins, late checkouts, custom upsells, and pre-sales, which shows both an amount and a count. Pre-sales are tracked separately because the guest has reserved but not yet been charged.

The To do tab is a work queue, not a report

On the right sits a transaction ledger with three tabs, each with a count badge: To do, Complete and Pre-sales.

The To do tab, listing upsells that still need a human action

To do is operational and easy to mistake for analytics. It is the queue of upsells still needing a person to act, such as charging a guest or notifying cleaners. An upsell only leaves that queue when somebody explicitly marks it done; it does not move on its own when payment lands. If the count is climbing, that is work waiting, not revenue growing.

The ledger columns cover the task, the charge, the upsell type, the date, the payment type, the listing, check-in and check-out, the guest and the reservation reference.

If Stripe is not connected, upsells have to be charged manually rather than collected automatically, which shows up here as a permanently busy To do tab.

Still Having Trouble?

Reach out via chat or at support@getbesty.ai.

Did this answer your question?