Skip to main content

Core Concepts

Volv Analytics helps teams understand sales performance by bringing activity, meeting, deal, and revenue data into one working system. The platform is most useful when you think of it as a set of connected views rather than a single scoreboard with one universal formula for every metric.

What Volv organizes​

At a high level, Volv organizes sales data around a few recurring concepts:

  • Activities: Calls, transcripts, and related agent work captured across communication channels.
  • Meetings: Scheduled sales conversations and attendance-related signals.
  • Deals and revenue: Opportunity outcomes, won deals, cash collected, and related performance views.
  • Attribution and journey context: The path from first touch through later meetings, deal movement, and revenue events.

These concepts appear across the product in different ways depending on the page you are using.

Views are purpose-built​

Volv does not present every metric the same way in every part of the app.

  • The Dashboard focuses on high-level performance cards, rep comparisons, and summary charts.
  • The Analytics page emphasizes attribution, conversion, revenue, and trend exploration.
  • Meetings and Call Analytics focus on meetings, calls, transcripts, and agent activity.
  • The Customer Journey view focuses on one lead or customer timeline at a time.

Because each view serves a different job, labels and calculations can be contextual. A metric that appears prominently in one workflow may be absent, renamed, or scoped differently in another.

Metrics are contextual, not universal​

You will see recurring business terms such as new leads, meetings, closed deals, revenue, calls, inbound, outbound, cash collected, sales cycle, or speed to lead. These are useful concepts, but they should be interpreted in the context of the page and date range you are viewing.

For example:

  • On the Analytics page, summary cards center on New Leads, Meetings, Closed Deals, and Revenue.
  • In Call Analytics, the visible stat cards center on Calls, Inbound, Outbound, and Meetings.
  • In the current Customer Journey experience, you may see contact-level context such as Sales Cycle, SDR, Closer, and last-contact details.

That does not mean every page uses one master KPI vocabulary or one shared formula for all reporting. When definitions matter for operational decisions, always interpret the metric through the specific report or workflow where it appears.

The customer journey matters​

One of Volv's core ideas is that sales reporting becomes more useful when isolated records are connected into a timeline. Instead of reviewing meetings, calls, and revenue as unrelated events, Volv tries to show how those events relate to the same prospect or account over time.

This journey-oriented model helps teams:

  • review how a lead moved from first touch to later sales activity,
  • understand which meetings and calls happened along the way,
  • connect deal progress and revenue events back to earlier interactions, and
  • investigate individual timelines when summary reporting raises questions.

A practical way to read the platform​

When you use Volv, it helps to read the product in two layers:

  1. Summary views for trend spotting, team monitoring, and performance review.
  2. Record-level views for understanding the activity history behind those numbers.

That combination is the core concept behind the platform: broad reporting for orientation, with enough underlying journey detail to support investigation and follow-up.

[ASSET REQUEST]

Target Image: customer-journey-timeline.png
Page: Overview > Core Concepts
UI State: A detailed view of a single customer's journey timeline.
Crop/Focus: Center on the timeline showing meetings, calls, and payments.
Annotations: Highlight the progression from lead to closed deal.
Owner/Source: Product Design Team