Business Intelligence is the Dashboard's analytics section, designed for pricing and sales decisions. It uses the same period filters as the entire Dashboard (Today, Week, Month, Year, or custom range).
The financials (at the very top)
| Card | What it measures |
|---|---|
| Average ticket | Average amount per booking, as a time evolution and with a comparison against the previous period. |
| ADR | ADR (Average Daily Rate): average price per night. It's calculated as sum of amounts ÷ sum of nights. |
| Lost demand | How much estimated money wasn't billed due to lost leads, in your main currency. |
How lost demand is calculated
For each lead marked as lost in the period, its value is estimated in this order:
- If the assistant got to quote a price, that amount is used.
- If it didn't get to quote, it's estimated as period ADR × nights requested.
- If there also aren't concrete check-in/check-out dates, it's counted as 1 night.
Only the loss reasons that represent real demand that couldn't be captured are included: lack of availability, price too high, customer who didn't respond, rate not loaded yet, and missing requested services. The rest of the reasons (tests, duplicates, etc.) are left out so as not to inflate the number.
- The card shows the breakdown by reason with its percentage, and each reason has a "View conversations" link that opens the chat listing filtered exactly by that subset (period's last-activity date + Lost status + that reason) — the breakdown's number and the number of conversations you see when clicking match. You can build the same slice by hand with the "Last activity date" and "Currency" filters of the chat listing.
- If there were lost quotes in other currencies, they appear listed separately at the bottom ("Also in other currencies"): they aren't added to the total so as not to mix currencies.
- The colors are inverted on purpose: here, going down is good (you lose less money).
Demand vs. availability
Two 6-month calendars, side by side:
- Requested dates (green): which check-in days you get inquired about the most.
- Dates inquired about without availability (red): where there was demand and you didn't have room.
The gap between the two is your lost opportunity. Clicking a day takes you to the funnel filtered by those conversations (in the red calendar, straight to the leads lost due to lack of availability).
Inputs for your pricing
- Average lead time: how many days before the requested check-in you get inquiries, grouped into 1, 2, 3, 4–6, 7–13, 14–29, and 30+ days.
- Requested length of stay: distribution of the nights requested (1 to 7 nights one by one, then 8–14 and 15+).
Sales pipeline
- Funnel: the conversion chart by stage — at each step you see how many leads are lost. With funnel and customer-status selectors.
- Lead attribution: a card with tabs — Channel (where each lead came in from), Geography (countries), and Ads (if you don't have the Audience section active; if you do, that detail lives there).
Portfolio and activity
- Tag statistics: a treemap where the size of each rectangle is proportional to that tag's volume — much easier to compare than a pie chart when the values are very different. By clicking the legend you can hide or show tags (useful for removing a giant tag from the treemap that crushes the others).
- Stop reason and Loss reason: why the assistant stopped and why customers were lost — they appear in long periods (month, year, or ranges of 30+ days).
- Activity Heatmap: a 7-day × 24-hour grid with when you receive the most messages — ideal for defining your team's hours. It has a Messages / Conversations toggle.
The Messages / Conversations toggle of the heatmap
| Mode | What it measures |
|---|---|
| Messages | Number of incoming messages received per day and hour. |
| Conversations | Number of conversations started per day and hour, regardless of how many messages each one had. |
The difference matters: a guest who sends 10 messages in the same conversation counts as 10 in Messages mode, but as 1 in Conversations mode — which better reflects the real demand (how many distinct guests wrote in each slot).
ℹ️ In Conversations mode, the moment the conversation started is counted (not its last message), all conversations are included — even if the assistant was off — and, as throughout the Dashboard, the time zone configured in your account is used.
Frequently asked questions
Why did lost demand "go up" and it's in red?
Because losing more is worse: in this card the colors are inverted on purpose.
Why doesn't lost demand include all my lost leads?
It's intentional: only the reasons that represent real uncaptured demand are valued (no availability, high price, customer who didn't respond, rate not loaded, missing services). Losses for other reasons — tests, duplicates, "Other" — don't add to the amount.
I quoted in two currencies and the lost demand total doesn't add them up.
Correct: the total is calculated only in your main currency. Lost quotes in other currencies are listed separately at the bottom of the card, without being added, so as not to mix currencies.
Does the heatmap count activity even if the assistant was off?
Yes — in Conversations mode all started conversations are counted, with or without the assistant active.
Why don't I see "Stop reason" or "Loss reason"?
They only appear with long periods (month, year, or ranges of more than 29 days).