- Discovery of eligible recordings through associated call detail
- Configurable recording-retention duration using extension, call direction, and call type
Product detail · Recording
Retain the right eligible recordings under a defined policy.
Make recording discovery and retention follow an approved call scope and policy. This optional layer remains separate from call-detail reporting, PBX recording, external storage copies, and downstream analysis.
Product record reviewed August 5, 2026. Source: Andy Lauppe — Owner/Founder; exact configuration review required.
Product boundaryDiscovery and retention begin with eligible PBX recordings.
A call-detail record may exist without recorded audio. Recording eligibility and policy must be established separately.
Structured product record
Best fit
- Organizations that need to find eligible recordings using associated call detail
- Workflows requiring different retention treatment for defined groups of recordings
- Customers prepared to define recording policy, access, retention, and deletion requirements
Selected product scope
Included and optional
- Separate Heritage recording-handler workflow for compatible customer-designated external storage
Verified retention dimensions
Apply duration according to defined recording groups.
The selected retention option can configure how long recordings are retained using extension, call direction, and call type. Heritage confirms the exact combination and resulting behavior before activation.
Identify the applicable extension grouping without assuming that every user or call is recorded.
Distinguish applicable inbound and outbound recording treatment according to the approved configuration.
Apply the configured definition of call type only after its source behavior and intended policy are confirmed.
Set an approved duration for the applicable group. No default or maximum period is published here.
Do not collapse the layers
Four related functions answer different questions.
Reporting and CDR
Describes call events and activity. It does not establish that audio exists.
PBX recording
Creates eligible audio under a separately approved recording configuration and policy.
Discovery & retention
Associates eligible audio with call detail and applies approved granular retention rules.
External copy or analysis
Moving or processing a recording broadens the data path and requires its own destination, access, security, retention, and review decisions.
Before activation
Define the recording policy and operating responsibilities.
- Eligible and separately configured PBX recording
- Customer-approved recording notice, consent, authorization, and internal policy
- Defined recording scope, authorized access, retention rules, and deletion requirements
Commercial structure
Explain the cost drivers without inventing an amount.
Recording scope, retention, and storage drive cost; exact amounts require a confirmed configuration. More retained recordings and longer retention affect the scope, but this page publishes no amount, range, tier, allowance, or included capacity.
Still configuration-specific
No archive assurance is implied.
Exact source behavior, eligible recordings, formats, access, storage, deletion, export, security, availability, service levels, and legal or compliance requirements remain unclaimed until verified for the selected configuration.
Common questions
Keep the answer tied to the selected recording service.
Does call-detail reporting mean a recording exists?
No. Reporting data and recorded audio are separate. PBX recording must be eligible and configured independently.
Can different recordings use different retention durations?
The selected option can configure duration using extension, call direction, and call type. Heritage confirms the exact groupings and resulting behavior before activation.
What is the default or maximum retention period?
No period is stated here. The requirement, selected service, applicable recording group, storage, policy, and commercial scope must be confirmed.
Is an external storage copy included?
No automatic inclusion is claimed. Heritage’s separate recording-handler workflow may copy eligible recordings to a compatible customer-designated destination after its access, lifecycle, security, deletion, and operating responsibilities are defined.
Is this a legal-hold or compliance product?
No such claim is made. Recording, retention, discovery, access, deletion, export, and legal obligations require appropriate customer policy and legal guidance.
Related solution