YesomaDocs
Back to Docs
Inbox & follow-ups·Beginner8 min read

Tour of the Insights dashboard

Walk through every block on /insights — outcomes, revenue + Customer Hub, quotes funnel, referrals, channels, categories, regulars.

In this guide

Insights is Yesoma's leadership decision workspace. It shows what changed across customer demand, relationship health, and recorded revenue, then links you to the Cases or invoices behind the numbers. Workspace owners, admins, and managers can open Insights from the sidebar. Agents and viewers return to the Dashboard because Insights contains workspace-wide leadership information.

Start with the decision layer

The top of every Insights view has four shared tools:

  • Segment bar — filter by teammate, channel, category, Company, or new/returning customer.
  • Trust bar — see when data refreshed, how many records are in the evidence set, the active period and segments, and how the metrics are calculated.
  • Recommended actions — open the highest-value exact Case or verified revenue bottleneck.
  • Decision story — follow one connected explanation from demand to customer health to revenue.

Yesoma applies segments before calculating the graph, KPIs, comparisons, health queue, and funnel. That means a filtered headline and the Cases beneath it always describe the same population.

If a comparison has fewer than eight combined records, Yesoma labels it Early signal or Directional. Counts are still exact; the label warns you not to over-read a percentage from a small sample.

Switch between the four views

Overview

Overview is the leadership briefing. It combines the current action queue, customer risks, response and follow-up performance, outcomes, and the most important demand and revenue evidence. Use it for a quick daily check before opening a specialist view.

Customer health

Customer health explains who needs care and why. It separates open work, waiting-on-customer work, overdue follow-ups, complaints, and relationship-risk signals. The care queue links to the exact Case that produced the risk, so you can act without searching through a customer's history.

Health scores are derived from recorded Case activity. They are prioritization signals, not a promise about a customer's feelings.

Demand

Demand shows what customers want and where inquiries originate. Choose one synchronized period:

  • 14 days — daily buckets
  • 3 months — weekly buckets
  • 12 months — monthly buckets
  • 3 years — quarterly buckets

The headline, comparison, graph, categories, and channels all use that same period. Select a graph bar to see its exact Cases. Select a category or source row to keep the period and other segments while narrowing the whole view to that driver.

Use Add event below the graph to record a campaign launch, pricing change, holiday, outage, or other dated business event. Event markers appear on matching graph buckets so future reviews can separate correlation from guesswork. The creator of an event can remove it later.

Revenue & outcomes

Revenue & outcomes uses recorded Yesoma evidence rather than estimated pipeline values. Choose 30 days, 90 days, 12 months, or all time, and select a currency when the workspace has more than one.

The quote journey follows one sent-at cohort:

  1. Sent — the invoice was actually sent in the selected period.
  2. Qualified view — a customer view was recorded after send.
  3. Recorded acceptance — acceptance was saved.
  4. Paid — a successful payment was recorded.

Bars and stages open their linked invoices. The Revenue Leak Radar highlights verified stops such as sent but not viewed, viewed but not accepted, accepted but unpaid, or payment confirmation still missing. Historical payments that cannot be matched to an invoice remain in revenue totals but are clearly disclosed as non-drillable.

Segment the whole workspace

Use one or several filters, then choose Apply. The active-segment count appears in the Segment label. Clear returns to the all-workspace view while preserving the active specialist view and its period.

  • Team member answers who owns the work.
  • Channel compares where customers reach out.
  • Category isolates a type of request.
  • Company shows one account's Cases.
  • Customer type compares first inquiries with returning-customer inquiries.

If a valid segment has no matching records, Yesoma shows an honest empty result instead of falling back to workspace-wide totals.

Save and share useful views

Open Saved views, name the current view, and choose Save. The saved view remembers the specialist tab, period, currency, and all active segments.

Leave Share with workspace leadership off for a personal view. Turn it on when other owners, admins, or managers should use the same operating lens. You can delete views you created; shared views created by another leader remain read-only for you.

The Briefings on or Schedule briefing button opens notification settings. Email briefings use the workspace's recorded priorities and weekly Pulse; they do not change the saved-view filters.

Understand what is real

Open How metrics are calculated in the trust bar at any time:

  • Recorded evidence comes from Cases, messages, follow-ups, invoices, payments, and outcomes saved in the workspace.
  • Derived metrics are counts, rates, medians, and period comparisons calculated from those records.
  • AI-written content is narrative wording. AI does not create the underlying values.

Outcome reporting depends on consistently marking Cases Won or Lost. Revenue depends on recording payments and refunds. Category and sentiment labels are AI-assisted and can be corrected on the Case; corrected data flows into the next Insights refresh.

Refresh behavior

Insights is calculated when the page loads and shows the refresh age in the trust bar. Reopen or refresh the page after changing a Case, follow-up, outcome, invoice, or payment. Saved views and annotations are workspace-scoped and protected by the same leadership access rules as Insights.

  • Daily: open Overview, work the first recommended action, and scan Customer health.
  • Weekly: compare Demand with the prior period, explain the largest driver, and review revenue leaks.
  • After a business change: add an event annotation and revisit the affected graph after enough Cases have accumulated.
  • Monthly: save or share the segments leadership repeatedly uses and remove views that no longer drive a decision.

More in Inbox & follow-ups

Was this article helpful?

If something was unclear or missing, tell us and we'll fix it.

Still stuck?

We'll help you get this working. Send us a message, or ask about Managed Setup.

Contact supportAsk about Managed Setup