9 docs tagged with "Dashboards"

The account Overview ledger: key facts, a timeline chart, and a filterable list of renewals, risks, and upcoming meetings for one account.

The Accounts view (/accounts) is the primary grid for your customer organizations: renewal context, open risks and opportunities, model-driven columns, and filters that match how RevOps and CS actually slice the business. Open it whenever you need to find accounts, narrow a cohort, sort by risk or revenue, or export a list for offline work.

One account view of every activity and customer metric: what changed, which products are in use, and how each item is trending.

Custom dashboards are curated, chart-first layouts—often provisioned for enterprise workspaces. Use them when leadership needs a fixed board with specific KPIs, branding, and layout, while analysts still use Accounts and Journey for operational drill-down.

The Dashboard & insights area of FunnelStory is where you see your book of business at a glance, drill into accounts, follow metrics and signals, and review activity over time.

Metrics in FunnelStory are numeric or aggregate measures tied to accounts (and sometimes users or products) that refresh with your workspace data models. You interact with them on the default dashboard as summary cards, inside the Accounts grid as columns or sparklines, on account detail as trends, and—when enabled—under Other views → Property charts for cross-account distributions.

A relationship map visualizes who on your team talks with which customer contacts, how strong those ties are, and how frequently conversations happen—grounded in the meetings, emails, chats, and tickets FunnelStory already ingests. Open it from an account's Customer Relations tab when you need a single-pane map for coverage planning, escalation handoffs, or spotting single-threaded accounts.

Signals are workspace rules that fire on a metric, prediction, or attribute condition, feeding Timeline, Notifications, CRM sync, and AI Agents.

The Event timeline is a chronological feed of what happened for an account or user—product activity, integrations, model changes, and (optionally) signals—so CSMs and AMs can reconstruct the story event by event before a call or escalation without opening five tools.