Skip to main content
Open Analytics → Custom Analytics to review saved views. Select the option to create a view to open the guided builder. Custom Analytics is feature-gated. The available datasets, fields, chart types, and actions depend on your team and role.

​
Ask a complete business question

Include:
  • The measure you want to count, sum, average, or calculate
  • The time range
  • The grouping, such as day, call reason, source, assistant, or service area
  • Filters that define the population
  • The intended chart type when it matters
For example:
Show inbound booked calls by week for the last 90 days, split by service area.
Avo turns the request into a draft. Review the draft fields rather than assuming the chart matches the wording.

​
Review the chart specification

Check:
  • Dataset: the product data used for the chart
  • Measure: the value being calculated
  • Grouping: the categories or time grain on the axes
  • Filters: the population included or excluded
  • Date range: the current preview range and the saved default
  • Visualization: line, bar, pie, aggregate table, stat card, call list, or another supported type
  • Sort and limits: especially for ranked tables and categorical charts
Line charts need a time-based x-axis. Pie charts should use one meaningful category with a limited number of segments. A stat card should answer one ungrouped headline question.

​
Refine with Avo

Use follow-up instructions such as:
  • “Make this a line chart by week.”
  • “Only include inbound calls.”
  • “Split it by call reason.”
  • “Exclude silent and spam calls.”
  • “Rename the chart to Weekly booked calls.”
The builder sends the current draft with each refinement, so a follow-up edits the active chart instead of starting an unrelated one.

​
Build a list of individual calls

Ask Avo for a call list when the question is “which calls?” rather than “how many?” For example:
List the unbooked inbound calls from yesterday with customer name, phone number, call reason, and duration.
A call list shows one row per call instead of an aggregate. The call start time is always the first column. Ask Avo to add or change up to eight other columns, such as customer name, customer phone, call reason, duration, booking outcome, AI or human handler, transfer destination, team call reason, or available Oversight tags and evals. Use filters and the date picker to define the population. By default, a list shows the 25 most recent matching calls; ask Avo for a different row limit or sort when needed, up to 100 calls. In the dashboard, select anywhere on a row to open that call in a new tab. An enterprise call list opens each call in its owning team. If more calls match than the saved row limit, the preview says that additional calls matched the range.
Call lists are available only for call analytics. Avo creates the list and changes its columns; the standard measure and grouping controls are for aggregate charts.

​
Validate before saving

  1. Choose a short period with known activity.
  2. Compare the result with the closest standard report or metric drill-down.
  3. Confirm the dataset, measure, filters, and timezone.
  4. Inspect a table version or, for a call list, open representative call rows.
  5. Check empty categories, null values, and unexpected totals.
  6. Restore the intended saved date range.
A visually plausible chart can still answer the wrong question. Validate the population and calculation, not only the trend shape.

​
Save and organize views

Give every saved view:
  • A specific title
  • A description that states the business question
  • The important population or exclusions
  • A sensible default date range
From the saved-view library, you can open a view, change its preview date range, edit its title or description, edit it in the builder, reorder supported views, or delete it. Deleting a team-owned view removes it from the Custom Analytics library. Confirm that it is not used in a recurring review before deleting it.

​
Export a report

When PDF export is available:
  1. Select the saved charts to include.
  2. Choose the report date range.
  3. Review the preview and chart titles.
  4. Export the PDF.
The export has a maximum number of charts. Use a focused set that tells one story rather than combining unrelated views. When a call list appears in a PDF, scheduled email report, or CSV output, it is rendered as a plain table. Dashboard call links are not included in those exported rows, and the saved row limit still applies.

​
Troubleshoot a chart

  • No data: widen the date range, remove one filter at a time, and confirm the selected dataset is available.
  • Unexpected total: compare the measure and denominator with Analytics → Metrics.
  • Too many categories: add a filter, choose a higher-level grouping, or apply a supported limit.
  • A call list is too short: ask Avo to increase its row limit, up to 100, and confirm whether the preview says more calls matched.
  • A call list opens the wrong population: review its filters and date range; its columns describe each call but do not define which calls are included.
  • A line chart will not render: use a date grouping on the x-axis.
  • A saved view changed: confirm the preview date range and whether the view was edited in the builder.
Record the saved-view title, team, date range, and the specific value that differs when escalating.