Sales: 616-465-5001

Product detail · Enhanced reporting

Follow the call path at the level the question requires.

Answer operational call questions that require more history and detail than basic PBX tools provide. Heritage positions CloudSweet as an optional enhanced-reporting layer—not a replacement name for basic PBX CDR, standard ACD reporting, recorded audio, or recording retention.

Product record reviewed August 4, 2026. Source: Andy Lauppe — Owner/Founder and official vendor materials; exact configuration review required.

Product boundaryEnhanced call detail is not recorded audio.

A call can have historical detail and a beginning-to-end event path without an associated recording. Recording requires separate eligibility, configuration, access, and policy.

Structured product record

Best fit

  • Teams investigating how calls moved from entry through queues, transfers, answers, or endings
  • Managers who need recurring prepared reports for defined operational questions
  • Organizations requiring enhanced historical call-detail review

Selected product scope

Included and optional

Included when selected
  • Enhanced historical call-detail reporting
  • Beginning-to-end call-path detail
  • Filtering and drill-down for configured call data
  • Prepared operational reports
  • Scheduled reporting
Separate optional product
  • Recording Discovery & Retention for eligible separately configured PBX recordings

Verified reporting categories

Start with the operational question.

CloudSweet can provide enhanced historical call detail, beginning-to-end call paths, filtering and drill-down, prepared reports, and scheduled reporting. The exact record content and report behavior must be confirmed against the selected configuration.

Historical detail

Review call events over time

Use retained call-detail records for approved operational review. No default history period is stated here.

Beginning to end

Follow the call path

Investigate the configured events that describe how a call entered, moved, and ended without assuming a universal field set.

Focused investigation

Filter and drill down

Narrow configured call data around a defined question. Available filters, events, and groupings require confirmation.

Recurring visibility

Prepared and scheduled reports

Use available prepared reports and scheduling after the report, recipients, access, timing, and delivery behavior are verified.

Reporting levels

Use the lightest layer that answers the question.

Managed PBX

Basic call detail

Useful basic CDR and call-history tools are part of the managed phone system. Exact fields and access depend on the configured role.

Hosted phone system

Standard ACD reporting

Standard agent, queue, dialed-number, and summary report families support configured call-center operations.

Separate products

Recording and retention

Recorded audio, discovery, and retention require separate eligibility, policy, access, configuration, and commercial decisions.

Before activation

Validate the data and the people using it.

  • Confirmed reporting question, call flow, source data, and organizational groupings
  • Defined users, roles, and authorized access
  1. 01

    State the question

    Define the recurring operational or investigative question before choosing a report.

  2. 02

    Trace the call flow

    Identify the numbers, queues, transfers, users, departments, locations, and other relevant groupings.

  3. 03

    Confirm available data

    Validate the source events, fields, history, filters, and report content available in the selected service.

  4. 04

    Define access and delivery

    Confirm authorized roles, recipients, scheduling, delivery behavior, and responsibility for reviewing the result.

Commercial structure

A recurring reporting add-on.

Recurring reporting add-on; exact scope and amount require a confirmed configuration. The selected history, reports, users, storage, and delivery requirements shape the proposal.

Configuration details

Exact reports remain configuration-specific.

Report names, fields, events, filters, exports, recipient roles, schedules, delivery methods, integrations, retention periods, security controls, compliance posture, and expected results are defined for the selected configuration.

Common questions

Keep the answer tied to the reporting question.

Is CloudSweet included with the managed PBX?

No inclusion claim is made. It is an optional recurring enhanced-reporting add-on with scope and amount confirmed for the selected configuration.

Does CloudSweet replace standard ACD reporting?

Not necessarily. The hosted phone system has standard ACD report families. CloudSweet is for questions requiring enhanced historical, call-path, filtering, drill-down, prepared-report, or scheduled-report capability.

Does enhanced call detail mean the call was recorded?

No. Call-detail data and recorded audio are separate. Recording must be eligible and configured independently.

Which fields and reports are available?

Heritage validates the source call flow, configured services, available data, groupings, roles, and intended question before confirming a field or report.

Can reports be scheduled?

Scheduled reporting is a verified category. The specific report, recipients, timing, access, delivery, and failure behavior require configuration-specific confirmation.

Is recording retention part of this page?

CloudSweet users may select the separate Recording Discovery & Retention product when eligible recordings need discovery and granular retention. Its policy, access, retention, deletion, and commercial requirements are reviewed separately.

Related solution

Place enhanced reporting inside the complete call-data design.