Skip to content
Valtier Media

Industry Insights

What Should Your Call Provider’s Report Include?

Choose useful call-provider reporting fields, reconcile billing and connect agency outcomes without confusing delivery data with policy results.

Valtier Media Editorial Team2 Oct 2026 · 6 min
Illustration of a call reaching an insurance agent: What Should Your Call Provider’s Report Include?

A call-provider report should let insurance agents and agencies identify activity, understand billing and investigate delivery questions. It should not be mistaken for a complete sales report unless it actually contains verified policy outcomes from your operation. For Spanish Final Expense calls, start with a small data dictionary and a reliable link between the provider's call record and your own follow-up record. A useful report makes a question answerable; a large export with unexplained fields can create more uncertainty than it resolves.

Define what the provider can actually report

Ask which events the provider observes directly and which information comes from the buyer. A platform may know that a call was routed, connected or billed without knowing whether a policy later issued. Do not interpret an empty sales field as proof of no sale, or a connected-call status as proof of a completed application. Separate delivery facts from agency outcomes at the beginning so every later calculation uses the right source of evidence.

Request an explanation of the available report rather than specifying fields the platform may not offer. Valtier's owner-described service includes call tracking and recordings, but the exact export format, access details and any integrations should be confirmed. Write a list of fields your process needs and mark each as available, unavailable or awaiting clarification. An unavailable field is a planning constraint, not an invitation to invent a replacement value. The provider-evaluation guide places reporting within the wider purchasing decision.

Build a small data dictionary

For each field you intend to use, document its meaning, source and update behavior. An identifier should be stable enough to connect the record to a question later. A timestamp needs a time zone and a clear event definition. A duration should say which interval it measures. A billing field should distinguish an original charge from a confirmed adjustment. These definitions matter more than an attractive chart because the chart inherits every ambiguity in its underlying fields.

Keep a copy of the dictionary with your operating notes. When the provider changes a label or your team changes a status, record the effective date. Otherwise, a report that combines older and newer records may appear consistent while mixing different meanings. Make the definitions accessible to the person reconciling the records, not only the person who attended the original demonstration.

Questions for the reporting dictionary
FieldDefinition to confirm
Call identifierWhich value uniquely identifies the provider's call record?
TimestampWhich event is recorded and in what time zone?
DurationDoes it measure the same interval used for billing?
Billing statusIs the charge final, adjusted or still under review?
Agency outcomeIs this supplied by your team or observed by the provider?

Reconcile calls, charges and adjustments

Choose a defined reporting period and compare the call records with the relevant billing or wallet movements. Use the call identifier when investigating differences. Keep original charges and adjustments traceable so you can explain the net amount without subtracting a credit more than once. If the report and the statement use different time references, resolve that difference before assuming activity is missing. An apparent discrepancy may be a cutoff issue rather than an absent call.

Do not count a wallet top-up and the calls purchased from that balance as two separate acquisition expenses in the same metric. The billing guide explains that distinction and the importance of the measured duration. At Valtier, the current price is $60 per billable call with a 90-second threshold; confirm the complete campaign terms rather than deriving them from a chart. A report should help apply the agreement accurately, not silently become a substitute for it.

Join agency outcomes without losing the original event

Add a link from the provider's record to your agency's follow-up or CRM record. Preserve the original delivery event while allowing later outcomes to develop. A call answered today may lead to a later appointment or application; updating that outcome should not erase when the call arrived or who first received it. Keep the ownership of outcome updates clear so the report does not depend on someone remembering to tell the analyst informally.

Watch for duplicate records and ambiguous attribution. A person may call more than once or speak with more than one agent. That does not automatically mean each interaction is a separate issued-policy outcome. Define how the agency links interactions and policies for its own analysis and document uncertain cases. The report becomes more useful when it shows what is known and what is pending than when it forces every record into a neat outcome prematurely. Missing information should remain visible until it is resolved.

Limit access and unnecessary copies

The FTC's guide to protecting personal information emphasizes keeping only needed information and limiting access appropriately. Apply that idea when exporting call reports or sharing recordings. A general management summary often needs counts, identifiers and operational observations rather than a full set of consumer details. Keep sensitive records in the controlled system suited to their purpose. A convenient spreadsheet should not automatically become the place where every piece of information is copied indefinitely.

Ask who can access recordings, how access is managed and what your organization's requirements are for using them. This guide does not establish a recording-law or retention rule. Those questions need the appropriate business and compliance process. For routine reporting, use a reference to the original record where possible and avoid distributing recordings through general team channels. The objective is to make an operational issue understandable to the people responsible for resolving it without expanding access beyond that purpose.

Sources: FTC: Protecting Personal Information

Design a report around decisions

A practical recurring report can show delivered activity, billed activity, unresolved billing questions, known agency outcomes and records awaiting an update. Add a short explanation of any change in definitions or campaign settings during the period. Then state the action the agency is considering: fix a reporting gap, adjust coverage, investigate a delivery issue or evaluate another controlled purchase. A report should support that decision rather than accumulate charts that nobody knows how to use.

Before starting, bring your reporting questions to a discovery call. Ask how the actual platform can support your proposed reconciliation and follow-up process. If a requirement is not available, decide how that affects the fit instead of assuming it will appear later. The useful outcome is a report your team can interpret consistently, reconcile to the purchase and connect to its own records, with uncertainty clearly labeled rather than hidden behind a polished dashboard.

Frequently asked questions

Should the provider report my issued policies?

Only if that information is actually available through an agreed process. Do not assume the provider observes outcomes that happen inside your agency or carrier systems.

What is the most important reporting field?

A stable call identifier is a useful starting point because it connects delivery, billing questions and agency notes. Its value still depends on clear definitions for the other fields you use.

Are more metrics always better?

No. Prioritize fields that answer real operating questions and can be interpreted consistently. Unexplained or unreliable metrics can distract from the records needed to make a sound decision.