Contact Rate
Calculate attempt-based contact rate with a worked call log. Separate repeated conversations, unique people reached and outcomes still awaiting review.
Trellus adds power and parallel dialing inside the CRM your team already uses. See pricing Book a demo
On this page
On this page
Contact rate measures how often call attempts produce a qualifying conversation with the intended person. In this guide, it is an attempt-based measure: successful contact attempts divided by all issued attempts in the same reporting period, multiplied by 100. Count an attempt once, even if several people join its conversation.
A second conversation with the same person can count as another successful attempt. It doesn't mean the team reached another person. Keep those two facts separate when deciding whether a calling list is producing conversations or how much of the audience remains unreached.
How Contact Rate Is Calculated
Contact rate = qualifying contact attempts ÷ issued call attempts × 100. Write down the period, time zone and qualifying rule beside the calculation. A dashboard label alone doesn't establish what was counted.
For the fictional example below, a contact requires a live exchange between the rep and the intended person. A conversation only with a receptionist, voicemail, an automated menu and a wrong-number answer don't qualify. A buyer saying “we aren't interested” does qualify if the exchange meets that rule. Contact describes whom the rep reached; it doesn't establish interest or qualification.
The denominator includes every issued attempt in this example, including unsuccessful attempts. A person waiting in the list who was never called isn't an issued attempt. If your reporting system treats failed-to-start calls differently, document that rule rather than silently removing inconvenient rows. Apply the same rule to every block you compare.
A worked call log with repeat conversations
Suppose a rep attempts four intended people during one block. All eight attempts have been reviewed and assigned an outcome. These are invented counts for the calculation, not a customer result or a recommended calling pattern.
| Intended person | Issued attempts | Attempts with a qualifying contact |
|---|---|---|
| A | 3 | 2 |
| B | 2 | 1 |
| C | 2 | 0 |
| D | 1 | 0 |
| Total | 8 | 3 |
The attempt-based contact rate is 3 ÷ 8 × 100 = 37.5%. Person A contributes two successful attempts, while B contributes one. There are three qualifying contacts but only two different people reached.
Among the four people attempted, unique-person reach is 2 ÷ 4, or 50%. That is a separate measure. If A answers one more issued call under the same rule, the contact rate becomes 4 ÷ 9, about 44.4%, while the number of different people reached stays two. The extra conversation may be useful follow-up; it doesn't show broader audience coverage. Use the account-reach worksheet for the fuller distinction between attempts, people and companies.
Leave uncertain outcomes visible
If the rep hasn't established who answered one of the eight attempts, the example is no longer fully classified. Show confirmed contacts, total attempts and the number awaiting review. Don't record the uncertain attempt as a confirmed failure or quietly drop it from the denominator.
You can label a calculation provisional while that review is open. If there were three confirmed contacts and one unresolved attempt among eight, the confirmed-contact calculation would remain 3 ÷ 8. The unresolved row could change the final result. A missing record is different from a known no-answer outcome.
When no attempts were issued, leave the rate uncalculated and report the count. Zero attempts doesn't produce a 0% contact rate; the denominator is zero. A missing attempt total also leaves the percentage uncalculated.
Contact Rate Versus Pick Up Rate
Pick up rate can mean answered calls divided by attempts, but check what “answered” means in the report you're using. A provider's answer status may include a machine or an automated menu. A human answer may be a receptionist rather than the intended person. Neither status alone establishes a qualifying contact under this guide's rule.
A duration threshold can help define a team's reporting convention, but it doesn't identify the speaker. A long voicemail greeting can last longer than a brief exchange with the right person. Keep the outcome and participant evidence alongside duration when reviewing a disputed row.
Teams also use “connect rate” in different ways. Read the actual connection rule before comparing it with contact rate. The connect-rate worked example separates human answers, buyer conversations and meetings. There is no reason for two differently defined measures to match just because their names sound similar.
Measuring and Monitoring Contact Rate Trends
Before comparing two blocks, keep the audience and type of work visible. Due callbacks and first attempts to a new list are different populations. A rep can have a higher rate because more of the block involves people who already agreed to another conversation. That is useful work, but it doesn't establish that the new list became easier to reach.
Retain the counts behind each percentage. Don't average rep percentages without accounting for their attempt totals. For two fictional, fully classified blocks, three contacts from eight attempts and one from two attempts combine to four contacts from ten attempts: 40%. Averaging 37.5% and 50% would give 43.75%, which isn't the combined attempt-based rate.
Keep the reporting cutoff stable too. If a conversation occurred during Monday's block but its outcome was reviewed on Tuesday, record the correction and when it was made. A fresh export can otherwise appear to change Monday's performance without explaining why. Compare results at equivalent review cutoffs, or show which earlier results were revised.
The call-list comparison guide helps check audience and attempt mix. Use its fuller comparison when the decision involves choosing between lists, rather than ranking reps from a small percentage difference.
Improving Contact Rate Without Increasing Call Volume
Start with a recorded problem you can inspect. If attempts reach the wrong business, check the number field and list preparation. If the intended people are repeatedly unavailable, compare an appropriate calling window on a similar audience. If a rep reports missing or delayed audio, investigate that technical experience separately; the contact-rate total cannot diagnose its cause.
Choose one change that answers the observed question, then record what else differed. A new list, another rep and a new time slot together leave several possible explanations for a changed rate. There is no universal best hour or number type established by this worksheet.
Apply the team's existing contact restrictions and agreed follow-up rules before planning another attempt. An unreached person isn't an instruction to keep calling. Preserve an agreed callback even if a fresh list would make the next block's percentage look better.
Limitations of Contact Rate
A higher contact rate establishes more qualifying contacts per attempt under the stated definition. It doesn't guarantee more meetings, pipeline or revenue. In the worked block, all three contacts could decline a next step. They would still count as contacts.
Track agreed follow-ups, booked meetings, held meetings and qualified opportunities separately. If you're reviewing later sales outcomes, the cohort conversion guide explains how to keep those outcomes tied to the same starting group. Don't divide this week's contacts into meetings from an unrelated group or earlier period.
Copy a contact-rate review note
Period, time zone and reporting cutoff: List and type of work, such as first attempts or due callbacks: Issued-attempt rule and total: Qualifying-contact definition and count: Outcomes awaiting review: Contact rate, or why it is uncalculated: Different people reached, reported separately: Corrections since the earlier review: Observed problem, next check and person responsible:
Keep contact details and call recordings in the team's approved system. The review note needs an appropriate record reference, not copied prospect information. If you're evaluating Trellus in a supported CRM or sales engagement platform, bring this definition and your calling setup so the evaluation can check the workflow you actually need.