# The administrator's Dashboard: how to read each number

> For the administrator: how to read the Dashboard (actions, the funnel from service to the ERP, the team and the habit) and where to see the organization's AI usage.

Source: https://vendria.com/en/ajuda/dashboard-do-administrador

## Where to find it

In the menu, under **Dashboard**. For the administrator, the screen answers **how much your
team is using Vendria**, not how much it sold. At the top are the store
filter (**All stores** or one store) and the period selector, and right below the
**Dashboard** and **Trend** tabs.

AI credit usage is not here: it is on the **Plans and usage** page, in the
top bar, on the **Plan usage** tab, which counts by the subscription's billing period (see the
section about it further down and [Créditos de IA: quanto cada ação custa e quanto foi usado](/ajuda/creditos-de-ia-da-sua-conta)).

## The periods you can choose

The selector offers **Today**, **Yesterday**, **Last 7 days**, **Last 28 days**,
**Last 90 days** and the last calendar months. The Dashboard opens on
**Last 28 days**; Evolution, on **Last 90 days**. Each tab keeps its own
period: changing it on one does not touch the other.

The store filter applies to the whole screen, including the habit block.

## The "In the period" block: three numbers

The dashboard opens with three cards: **Actions**, **Active people** and **Volume in orders confirmed in the ERP**.

**Actions** is the main number on the screen. It counts everything the **Actions** screen
lists in the period:

- what Dri did in conversations (search, order, list and the other actions);
- the sends to the ERP made through the screen;
- the imports made through the import screen (one that arrived through a conversation
  counts inside the conversation);
- the quote sends;
- the order notices that went out on WhatsApp, one per order and stage.

Under the number come the variation and **in N conversations with an action**. The breakdown by type
is in the **Actions · by type** table, right below.

**Active people** says how many people with access acted in the period, and **of M with
access** gives the real size of the usage. "With access" counts the administrators, the store
team (administrators and sellers) and the WhatsApp contacts who have already
chatted. Sales reps are left out of this count and appear in the
**Own team and rep agencies** section, further down. Someone acted if they did anything the dashboard counts:
someone who only imported a spreadsheet or only sent a quote also counts.

**Volume in orders confirmed in the ERP**, highlighted, is the value of the orders that entered the ERP in the
period, by each order's total, once per order, with how many orders there were.
Without a connected ERP, the card says **No ERP connected** instead of showing zero.

The variation is against the previous period of the same length (hover to see
against what: "vs. previous 28 days", "vs. previous month", "vs. yesterday up to the same
time"). **new** means it was zero before; **—**, that it was zero and is still zero.

## Actions · by type

**Actions · by type** lists each type of action that happened in the period, one per
row, with **Times** (how many times it happened) and **Conversations** (in how many different
conversations). Import, quote sending, order notice and sending to the
ERP through the screen do not happen in a conversation, and get **—** in that column. The table's
total is the number on the **Actions** card. **No actions in this period.** appears
when there were none.

Dri's actions that have no short name on the dashboard (such as **Search**, **Order** and
**List**) appear with the name from the **Guide** tab of the **Plans and usage** page, for example
**Quote built by Dri** or **Choose the conversation's customer**. When Dri does
the same action in two ways, both go into a single row. A Dri action that the
Guide does not know goes into **Other**. The **Guide** tab belongs to whoever administers the organization or belongs to
a rep agency; an organization seller who is not an administrator sees only the summary.

## The Top members table

In the **Top members** section, a single table shows, by **Person**, actions and usage on the
same row, ordered by actions. Everyone who acted in the period is included: the team and
outsiders, such as sales reps. First comes the **Actions** group: **Total**,
**Search**, **Order**, **List**, **Import**, **Sending**, **ERP** and **Other**.
The ERP column adds up the sends to the ERP through the screen and through Dri. Then comes the
**Usage** group: **Conversations**, **Quotes** and **Confirmed**.

⚠️ **The sum of the Conversations column does not match the funnel, and that is correct.** In the table
only the conversation the seller opened counts: in a conversation the buyer started,
the number is the buyer's, not the typist's.

## The Own team and rep agencies section

It always appears. The first row,
highlighted, is your company's **in-house team**: the sum of those who are not outsiders,
with **Active** (how many people on the team acted) and the same **Actions** and
**Usage** groups. It serves as a reference to compare with each rep agency. The other
rows are the rep agency companies, ordered by actions, with **Active** (*"N of M"*: how many members acted
in the period, out of how many the company has) and the same **Actions** and **Usage** groups as the
team table, added up for the whole company. Acting, here, is anything
the dashboard counts: conversation, quote, confirmation, send to the ERP, import, quote
send or Dri action. Without a rep agency company with an active mandate,
the own team stays in the table and the notice below it says there is no
rep agency.


## The funnel, at the end of the dashboard

The last item on the dashboard is the **Funnel · from first contact to the ERP**, from top to
bottom, one bar per stage:

- **Conversations**: all WhatsApp conversations in the period, including those the
  buyer started.
- **Quotes**: quotes created in the period, drafts included. What is measured
  is who is using the tool.
- **Confirmed orders**: documents that became confirmed in the period. An
  order reconfirmed counts only once.
- **Orders in the ERP**: orders that entered the ERP. The person is whoever sent it, or whoever
  created the order when the send went out through the screen. Without a connection, the stage says **no ERP
  connected**, so that a zero without a connection does not look like lack of use.

Each stage shows the number, the variation and how many people acted (*"8 people
created"*). **Quotes**, **Confirmed orders** and **Orders in the ERP** also show
the value in reais (*"quoted"*, *"in confirmed orders"*, *"in orders in the
ERP"*), each document once, with the variation against the previous period. Between the
stages comes the proportion over the previous one (*"58% relative to conversations"*), and at the end
the proportion from start to finish. This percentage can go over 100%, and that is correct:
each stage counts what happened in the period, it does not follow the same orders. A
quote can come from an import with no conversation, and an order confirmed today may have
been quoted last month.

## The Evolution tab

The **Trend** tab shows the same measures over time, one chart per
measure, starting with **Actions** (then **Active users**, **Conversations**,
**Quotes created**, **Confirmed orders** and **Sent to the ERP**), with the granularity
**Day**, **Week** or **Month**. The **Volume in orders confirmed in the ERP (R$)** chart shows only the value
of the orders that entered the ERP, on its own scale, with the period total on top. The
**Funnel volume (R$)** chart shows, on the same axis, how much the quotes,
the confirmed ones and what entered the ERP are worth. With the
month granularity and a window of days, the screen warns **The first and last month of the
window are incomplete**: the drop at the ends comes from the calendar, not from usage. With
**Today** or **Yesterday** the curve has a single point. The **i** next to each
chart's title explains what a point counts, and hovering shows the point's period in
words (**July 2026**, **week of 27/07 to 02/08**).

## The Habit block, on the Evolution tab

Below the **Trend** charts is the **Habit** block, with the chosen
period in the title. It follows the period of the **Trend** tab, which is chosen
separately from the **Dashboard** tab's: changing the period on the Dashboard does not affect it. The store
filter also changes the block.

- **MAU: people active in 28 days** and **WAU: people active in 7 days**, measured
  at the end of the period, with the curve of both throughout it: MAU with one point every
  28 days and WAU with one point per week, without overlap. In a closed month, the
  card says the date on which it was measured. An active person is someone who had at least one
  action, by the same yardstick as the **Actions** card (the order notice, being automatic, does not
  count for anyone). WAU close to MAU
  indicates weekly use.
- **Intensity: actions per week**: a chart with one line per band,
  showing how many people did 10 or more, 3 to 9, or 1 to 2 actions in the
  7 days up to each point of the period.
- **Retention by cohort**: one curve per arrival group (those who had their first
  action in that month). The bottom axis counts the months since arrival, and the point is
  how many of the group acted in that month. The thickest line is the average of the groups,
  weighted by the size of each, using only months already closed. Compare the curves at the
  same age, not by date: a curve that flattens is people who stayed; a curve that drops
  to zero is people who passed through. Groups with fewer than 3 people appear lighter, and
  hovering over them shows the **N of M**.
- **Cohorts by month**: the same groups in a table, one row per month of each person's first
  action, in the six months ending at the end of the period, and one column
  per month after arrival. The cell says how many of that group acted in the month (**2
  of 5**, with the percentage next to it). A month only appears once it is closed, except
  the arrival month, which gets **\*** while it is in progress; the dash is a month that has not
  arrived yet.
- Intensity compares weeks: with **Today** or **Yesterday** the period has a single point
  and the screen says so in place of the curve. Cohorts do not depend on this and
  appear in any period.

⚠️ Habit counts what the **person** did, and that is why it is not the same measure as the
**Actions** card, which also counts the automatic order notice and each Dri action
inside a conversation.

## The organization's AI usage

AI usage is on the **Plans and usage** page, on the **Plan usage** tab: the balance,
usage per action, per store and per team member and, on the same screen, the
sales reps' usage (**By rep agency** and **By sales rep person**), all within the
plan's billing period. See [Créditos de IA: quanto cada ação custa e quanto foi usado](/ajuda/creditos-de-ia-da-sua-conta).

## When it goes wrong

**"Could not load the numbers"**: the response did not arrive. The screen does not
show zero on purpose, because zero would say nobody worked. Reload.

**"Nobody on the team acted in this period."**: it is almost always a period that is too
short. Widen the window before concluding the team stopped.

**The seller opens Dashboard and sees something else**: the same entry takes the seller
to a sales and goal screen, which not every store has enabled. See [Minhas vendas e minha meta: pelo WhatsApp e na tela](/ajuda/minhas-vendas-e-minha-meta).
