Feature · Reporting

See the work that is moving, waiting and missing context.

CRM reporting can help a team review enquiry sources, ownership, appointments and pipeline activity when the underlying records are current and the metric definitions are understood.

Subscribe to 121 CRM Seller, billing and cancellationSee the product journey

Customer Thread

An operational review, not a verdict

Illustrative example

Question
Choose a useful decision
Definition
Name fields and time window
View
Compare current activity
Interpret
People inspect the context
Human decision
Action
Owner addresses the exception

All figures are fictional. No revenue, attribution or performance result is claimed.

Operational dashboard

Review ownership, due work and recorded source together.

The figures are deliberately fictional and demonstrate information hierarchy rather than a performance promise.

121 CRM · Reporting summary

Journey summary

New

Illustrative

Owned

Illustrative

Due

Illustrative

Website

Referral

Direct

Illustrative exampleFictional figures only. Definitions, access, data quality and interpretation determine whether a view is useful.

How it helps

See how the feature supports the work.

Each part has a clear job. It becomes useful when it fits the way customers already move through the business and your team knows when to step in.

Capability 01

Dashboards

Combines supported widgets and filters into an operational view for ongoing monitoring.

How it works: Aggregates eligible source data into configured dashboards, reports or exports.
Why use it: Helps a team review the few measures needed for the next decision.
Plan for: A report reflects available source data and configuration; it does not prove causation or data completeness.
Your team owns: A person must interpret results, investigate gaps and decide what action is justified.

Capability 02

Custom reports

Builds multi-page reports from selected widgets, sections, themes and date settings.

How it works: Aggregates eligible source data into configured dashboards, reports or exports.
Why use it: Packages relevant performance information for a particular audience instead of exporting everything.
Plan for: A report reflects available source data and configuration; it does not prove causation or data completeness.
Your team owns: A person must interpret results, investigate gaps and decide what action is justified.

Capability 03

Scheduled reports and PDF export

Sends or exports a configured report on a schedule, with detailed drill-down remaining inside HighLevel.

How it works: Aggregates eligible source data into configured dashboards, reports or exports.
Why use it: Makes routine reporting repeatable while preserving the live system as the detailed source.
Plan for: A report reflects available source data and configuration; it does not prove causation or data completeness. Emailed or exported reports do not provide every live drill-down available inside HighLevel.
Your team owns: A person must interpret results, investigate gaps and decide what action is justified.

Capability 04

Attribution reporting

Uses captured source and journey data to report supported lead and revenue attribution views.

How it works: Aggregates eligible source data into configured dashboards, reports or exports.
Why use it: Helps a team investigate which recorded routes contributed to an enquiry or sale.
Plan for: A report reflects available source data and configuration; it does not prove causation or data completeness.
Your team owns: A person must interpret results, investigate gaps and decide what action is justified.

Capability 05

Custom metrics

Builds calculated measures from eligible data sources and fields, subject to plan and data-quality limits.

How it works: Aggregates eligible source data into configured dashboards, reports or exports.
Why use it: Lets a business express a useful ratio or KPI without maintaining a separate spreadsheet formula.
Plan for: A report reflects available source data and configuration; it does not prove causation or data completeness.
Your team owns: A person must interpret results, investigate gaps and decide what action is justified.

Useful reporting

Start with a management question, not a wall of widgets.

A useful dashboard brings the operational picture and recorded source together. 121 also keeps the definition and decision boundary visible.

Enquiry and ownership

Review new enquiries, assigned owners, overdue next actions and records without a current action.

Appointments and pipeline

Inspect scheduled activity, stage movement, ageing and recorded outcomes using agreed definitions.

Conversation workload

Where supported, review open, assigned and exception conversations without treating speed alone as service quality.

Definitions and data quality

A chart is only as reliable as the records beneath it.

Source, stage, date and outcome need consistent meaning if they are used for comparison.

Metric definition

Record what is counted, which date is used, exclusions and the reporting window.

Missing and stale data

Show incomplete ownership or next actions rather than silently excluding inconvenient records.

Access

Give people only the reporting detail appropriate to their role and the sensitivity of the customer information.

Definition register

A metric needs a definition and an owner.

Useful reporting records what is counted, the relevant time window, exclusions and known data limitations.

121 CRM · Control responsibilities

Control questionOwnerNext check

Who can export customer data?CustomerConfirm

Who changes workflow permissions?Agreed scopeRecord

What happens at account closure?SharedDefine

Which suppliers process data?SharedCheck

Illustrative exampleIllustrative governance pattern. It does not assert that a specific technical control or certification is in place.

Interpretation

Use patterns to ask better questions — not to manufacture certainty.

Operational dashboards do not prove causation, future revenue or individual performance without context.

Lead source

A recorded source can support review but may not capture every influence or establish what caused an outcome.

Pipeline value

Values and stages depend on human updates and assumptions; they are not guaranteed income.

Human judgement

Management review

A responsible person considers capacity, exceptions and data quality before deciding what to change.

Questions about this page

Useful answers, without the sales fog.

1. What can we report on?

Potential views include enquiries, ownership, next actions, appointments, stages, outcomes and supported conversation activity. Exact fields and reports depend on the configured account.

2. Can reporting show which source works best?

It can organise recorded source and outcome data, but accuracy depends on definitions, tracking and updates. A source field alone does not prove causation.

3. Does the CRM forecast revenue?

No forecast or revenue outcome is promised. Pipeline values and stages are working records that require human interpretation and current data.

Read all CRM questions

Continue the journey

Sales pipelines Customer management See the product journey

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing