Call Attempts: Measure Contact Without Inflating Access
Measure intake contact attempts separately from people reached and care accessed with a fictional call-event exercise, response definitions, and buyer checks.
Intake call attempts measure outreach effort; successful contact, appointment decisions, and attended care require their own evidence and should not be inferred from the number of calls logged.
A team can make more calls without reaching more people. It can also reach someone and learn that a different time or contact method is needed. A useful report preserves this work without counting every dial as access or treating every unanswered call as refusal.
Behavioral health intake contact attempts measurement
Define the event being counted before setting a target. A dial, a delivered message, a conversation with the intended person, and an appointment decision are separate observations. Use the organization's approved identity and communication practices, including what staff may leave in a message. Call volume alone does not establish that those practices were followed.
Use a fictional 20-attempt exercise
Five requests generate 20 attempts. Three intended people are reached, two remain unreached, and two of the reached people book visits. That is 20 attempt events, five requests, three reached requests, and two bookings. The attended outcome is still unknown. Report effort per selected request separately from the reached-request proportion. Neither number alone explains the quality of the conversation or the availability of an appropriate appointment.
Keep contact outcomes factual
An unanswered call, a full mailbox, an invalid number, a requested callback, and a completed scheduling conversation imply different next work. This article's exercise focuses measurement rather than prescribing a universal call-disposition vocabulary. An employee should record only what the event establishes. A voicemail reaching a shared number does not prove contact with the intended person. A request for a later call does not establish refusal of service.
Account for attempts across employees
If two intake employees call the same request, count the underlying attempts and inspect whether the second was useful or duplicative. Employee-level activity totals can be accurate while the distinct-request total remains one. Preserve event times and the request relationship for analysis. Do not deduplicate legitimate repeated attempts merely to lower effort, and do not count accidental duplicate entries as additional work once the error is established.
Use repeated attempts to ask a better operating question
Inspect where outreach concentrates. In the fictional set, 12 of 20 attempts concern the two unreached requests. That finding suggests a need to review contact information, preferred contact times, and the approved next approach; it does not prove that the staff should call more often. Clinical concerns arising during contact go to authorized clinicians. Set outreach policy from the organization's actual service and communication requirements rather than from an invented conversion benchmark.
Work through the fictional acceptance exercise
Use a 20-attempt event-to-request bridge separating attempted, reached, booked, and not-yet-known attendance outcomes. All examples below are fictional.
| Exercise | Starting evidence | Required action | Failure to expose |
|---|---|---|---|
| Mailbox reached | A call reaches voicemail but no person | Record the supported attempt outcome | Voicemail counts as successful personal contact |
| Requested callback | A person asks for contact after 5 p.m. | Preserve the preference and next contact decision | A callback request is coded as decline |
| Two employees | Two employees dial one request on the same day | Count both real events and review the overlap | Two calls become two people reached |
| Booking only | A reached person books a future first visit | Report booking without claiming attendance | Contact success becomes completed access |
Boundary 1: Mailbox reached
The channel worked partially. The employee still lacks evidence that the intended person received or understood the message.
Boundary 2: Requested callback
The conversation supplies useful scheduling information without ending the underlying request.
Boundary 3: Two employees
Event-level activity and person-level reach can move differently. The reporting units must remain explicit.
Boundary 4: Booking only
The next clinical event remains in the future. A report should describe the milestone actually reached by its cutoff.
More attempts produce one additional contact, not several
Five requests originally generated 20 attempts. Three intended people were reached, two remained unreached, and two reached people booked visits. Twelve of the attempts concerned the two unreached requests. Attendance was unknown at that cutoff.
For one unreached request, staff obtain corrected contact information through the approved process. On Tuesday, one call reaches voicemail; Wednesday's call reaches the intended person, who asks for a Thursday callback after work. That callback produces a booking. The three calls add three attempt events but only one newly reached request and one new booked request.
The revised totals are 23 attempts across five requests, four reached requests, three bookings, and one still unreached request. The request-level reach proportion rises from three of five to four of five. The three new calls are not three newly reached people. Nor is Thursday the first successful contact: Wednesday established contact even though booking happened later.
A report that defines successful calls only as bookings would lose Wednesday's useful conversation and its availability information. A report counting voicemail as reach would move the milestone a day too early. Retaining the separate events makes the changed contact information and the person's requested timing visible, without claiming that any booking has yet become attended care.
Observe the work before setting a target
AHRQ’s time-and-motion method measures task duration.
AHRQ describes observation in simulated settings.
Reconstruct the five fictional requests from their call-event histories. Have one reviewer calculate effort and another calculate distinct reach. Ask them to explain why the numbers differ. Then remove an event timestamp and introduce a duplicated event entry to test the investigation path. Use the result to agree on the minimum evidence needed for trustworthy measures before setting productivity goals or comparing employees.
Questions to settle with the buying committee
Does leaving a voicemail count as reaching the patient? It establishes a voicemail outcome, not necessarily communication with the intended person. Define reach using the actual evidence the organization requires.
Can contact attempts measure access to care? Attempts measure outreach effort. Booking and attended care are separate milestones requiring their own evidence.
Should several employees' calls be deduplicated as one attempt? Count real events separately while counting the underlying request once. Review accidental duplicate entries and unnecessary overlapping outreach on their evidence.
What should a high attempt count trigger? Review where attempts concentrate, contact information, stated preferences, and the approved outreach approach. A higher count alone does not establish better performance.
Bring the specimen to a full-platform review
Bring the attempt-to-request bridge to the admissions reporting review. The demonstration should make it possible to recognize useful effort without inflating the number of people who actually reached the next care milestone.
Ease offers a unified CRM, EHR, and RCM platform for behavioral health. Use the call-event bridge to ask which evidence supports reached, booked, and attended milestones across CRM, EHR, and RCM, rather than equating attempts with access.
Related reading
- Intake Forms Changed Mid-Referral: Keep the Version
- Referral Documents Arrive Late: Route Them Correctly
Frequently Asked Questions
Does leaving a voicemail count as reaching the patient?
It establishes a voicemail outcome, not necessarily communication with the intended person. Define reach using the actual evidence the organization requires.
Can contact attempts measure access to care?
Attempts measure outreach effort. Booking and attended care are separate milestones requiring their own evidence.
Should several employees' calls be deduplicated as one attempt?
Count real events separately while counting the underlying request once. Review accidental duplicate entries and unnecessary overlapping outreach on their evidence.
What should a high attempt count trigger?
Review where attempts concentrate, contact information, stated preferences, and the approved outreach approach. A higher count alone does not establish better performance.
