Build your own baseline before borrowing anyone else’s.

Decide what you want to understand: how many eligible attempts were made, how often a person answered, whether recorded calls produced a reviewable output, or what happened after an appointment was set. Those are different questions and may require different cohorts.

Choose the reporting window, time zone, campaign scope and data cutoff. Identify the record keys needed to join an attempt to its recording, processing output and follow-up. If the join is unavailable, report separate counts instead of manufacturing a funnel.

Keep a record of exclusions and unresolved cases. A report becomes less useful when difficult records silently disappear between its numerator and denominator.

• Question:[the operational question being answered].
• Population:[campaigns, operators, contacts or attempts included].
• Window:[start, end, time zone and event used to place a record in the window].
• Cutoff:[when delayed records were last included].
• Numerator:[exact qualifying event and count].
• Denominator:[eligible records for that same definition and count].
• Join:[verified record key or explanation that counts are not joined].
• Exceptions:[unknown, pending, excluded or corrected records].
• Owner:[person responsible for reproducing the measure].

Leave an unknown field unknown. Do not insert a plausible denominator merely because the result would look familiar.

For a defined cohort, a rate is the qualifying count divided by the eligible count. Display both counts alongside the percentage. When the denominator is zero, report that the rate is not applicable rather than displaying a misleading zero-percent performance result.

Human-answer rate:define which attempts were answered by a person and which eligible attempts form the denominator. Keep human answering separate from a business-defined “qualified conversation,” which may require additional criteria.

define the expected output and eligible source calls, then join the output to those calls.

Appointment follow-through:separate requested, confirmed, held, canceled and other relevant states under your actual process. An appointment set is not a held meeting or closed business.

A contact may have more than one eligible attempt. Report both attempts and distinct contacts when the question requires that distinction. A higher attempt count does not necessarily mean a broader audience or more conversations.

Preserve the contact and attempt identifiers needed to understand repeats. Check whether an apparent new record is a duplicate import rather than a genuinely new person. Do not treat suppression or assignment conflicts as a reason to count the more convenient version.

When comparing two periods, describe changes in list source, eligibility policy, staffing, timing and configuration. A changed mix can affect results even when the software is unchanged.

Choose whether the report is about calls occurring in a window or outputs produced in a window. Both can be useful, but they answer different questions.

For a call-cohort coverage report, allow a documented processing cutoff and join the outputs back to those calls. At that cutoff, distinguish completed output, still-pending work, unavailable source audio and unresolved failures where the actual data supports those categories.

An empty field alone does not establish the reason. Keep the uncertainty visible until the underlying record is reviewed. Do not count a reprocessed or duplicate output as an additional completed conversation.

Use your own ordinary operating periods to build a baseline. Keep definitions stable enough that a change in the number means a change in the work, not a renamed status or a different join.

For a small cohort, show the counts and avoid a confident causal conclusion from a large percentage swing. For a configuration change, document what else changed and what remained comparable. A before-and-after table alone does not prove the dialer caused the result.

The published DialBreeze snapshot illustrates why cohort discipline matters: its activity totals, shorter-window rates and inventory are separate measures. This guide deliberately does not copy those values into your blank worksheet.

There is no universal best time to call. It depends on your list, so run a simple test. Split one list into two blocks, call one block in the morning and the other in the afternoon for a week, then compare how many calls connected each day. DialBreeze's funnel shows connected calls per day and per list, so you can compare the two blocks and keep the one that connects more.

DialBreeze defaults to 8am to 8pm in each lead's local time.

When nobody answers, log the outcome (no answer, voicemail or callback) and move on. A no-answer lead comes back after 24 hours by default, and a callback you set jumps to the front of the queue when it is due.

One vendor's published numbers, and what they can and cannot tell you

Allo, a competing dialer vendor, published an analysis on October 6, 2026 of 72,339 outbound calls placed through its own power dialer to US and Canadian numbers between July 1 and September 30, 2026. It reported that 26.0% of calls reached a live person and that 7.4% became a conversation of a minute or more, roughly 1 in 13 dials, and that connect rates were highest between 11 a.m. and 4 p.m. in the prospect's local time. This is observational data from one vendor's users, not a DialBreeze result, and Allo itself says its numbers show when calls connected, not that the hour alone caused it. Allo inferred each prospect's time zone from the area code, which can differ from where the person actually is, and it kept only calls where answering-machine detection returned a result, so calls without one are excluded from every figure. Use it as a hypothesis to test against your own list, not as a forecast.

What a session costs on DialBreeze (only what the pricing page states)

Calling is $0.75 per dialing hour (1.25 cents a minute), drawn from your calling credit. The pricing page says minutes are dialing-session minutes, counted while your browser audio is connected in a dialing session, and that ringing and wrap-up inside the session count. The meter is per session, not per line and not per dial. To estimate your calling-usage cost per conversation, multiply your billed session hours by $0.75 and divide by the number of conversations you actually had, if that number is greater than zero. This excludes software-seat and phone-number charges. Take both numbers from your own sessions and your own definition of a conversation; this page does not publish a per-conversation figure.

A completed measure should be explainable from its definition, records and cutoff. Another responsible person should be able to identify what was counted, what was not and why the denominator belongs with the numerator.

Keep the source records appropriately protected; a useful aggregate does not require exposing personal lead details. Report unresolved data gaps alongside the number rather than making the dashboard appear more complete than the evidence.

Use the result to choose a concrete next investigation: an import problem, a missed callback, unavailable audio or a change in the eligible list. A benchmark is useful when it improves the work, not merely when it makes an impressive headline.