From Patient Need to Contact Demand

Contact Center Field Guide · Foundation 02

Best for: Healthcare executives, contact-center leaders, access leaders, digital leaders, and emerging leaders
Helps with: Demand analysis, channel strategy, repeat-contact reduction, digital-service design, and cross-functional improvement
Reading time: Approximately 10 minutes
Last reviewed: October 7, 2026

Executive summary

Contact volume measures interactions. It does not measure the number of underlying patient needs.

One patient need may generate one successful interaction. It may also generate several calls, messages, transfers, portal attempts, and follow-up contacts. The difference depends partly on the patient's situation and partly on how the organization communicates, designs processes, manages capacity, and completes promised work.

This distinction matters because leaders often treat demand as something the contact center simply receives. In reality, the broader organization shapes much of it.

A change in contact volume may reflect growth, seasonal need, a new program, confusing instructions, appointment scarcity, a digital problem, an unresolved prior interaction, or several causes at once. The contact center must prepare to handle actual demand while helping the organization understand why that demand exists.

The executive question is therefore not only, “How many contacts should we expect?” It is also, “What patient needs produced those contacts, and which parts of the organization could change the pattern?”

The concept in plain English

Patient need describes what the person is trying to accomplish.

Contact demand describes the interactions that need produces across measured service channels.

A patient may need to schedule a specialist visit. That need might produce:

• one portal transaction;
• one completed phone conversation;
• a portal attempt followed by a call;
• an abandoned call followed by a second attempt;
• a transfer and a callback;
• several contacts while the patient waits for missing information; or
• no recorded contact because the patient gives up.

These paths represent the same underlying need differently. Counting contacts without understanding the need can overstate how many distinct people or issues the organization served. It can also hide how much effort the patient had to expend.

Research on call-center retrials supports this distinction. Customers may contact an organization again when a prior interaction does not produce satisfactory resolution, which means some measured arrivals reflect earlier service outcomes rather than new needs.¹ Operations research also distinguishes new demand from redials after abandonment and reconnects after answered contacts.²

The path from need to demand

Five decisions and conditions shape whether a patient need becomes contact demand.

1. The need itself

Some needs occur naturally. People need appointments, information, billing assistance, referral status, technical help, or changes to existing arrangements.

The contact center cannot and should not eliminate necessary service demand. Its responsibility is to make appropriate help available and help the organization understand the demand.

2. Information already available

Clear instructions, accurate websites, accessible communications, and reliable status information may allow someone to act without assisted service.

Poor or inconsistent information can produce clarification contacts even when the underlying process works correctly.

3. The available channel

Channel design influences whether a person completes the task digitally, contacts an employee, switches between channels, or gives up.

Digital service does not automatically eliminate assisted demand. A portal may prevent calls when it works well. It may generate calls when authentication fails, information differs from what staff can see, a workflow stops before completion, or a patient cannot find the needed function.

A qualitative study of adult portal users documented difficulties with login, messaging, scheduling, refills, and locating information. Some participants described turning to telephone service when the portal did not complete the task.³ This does not establish how frequently every portal creates calls, but it illustrates how channels influence one another.

4. The first service outcome

A complete answer may close the need. An unclear answer, abandoned attempt, transfer failure, missed callback, or unresolved dependency may generate additional demand.

Repeat contact should not automatically be treated as employee failure. The cause may involve policy, authority, system access, a downstream team, changing information, or a new development in the patient's situation.

5. The patient's decision to continue

Not every unsuccessful attempt creates another recorded contact. People may wait, seek help elsewhere, arrive in person, use urgent or emergency services, ask a family member for help, or abandon the effort.

In a qualitative Veterans Health Administration study, patients described waiting, doing nothing, trying again later, or seeking unscheduled in-person care after encountering telephone-access barriers.⁴ Contact data therefore reveal only part of unmet need.

Necessary, influenced, and preventable demand

Leaders need a practical classification that does not imply every contact is undesirable.

Necessary demand

The person has a legitimate need that requires assisted service under the organization's current service model.

Examples include a complex scheduling request, a billing question that requires account-specific review, or help using an accessibility service.

Influenced demand

The need is legitimate, but organizational choices affect the channel, timing, or amount of effort required.

Examples include a patient calling because appointment status is not available digitally or because the organization directs people to telephone service for a particular task.

Preventable demand

The organization generated additional contact through an avoidable failure, unclear communication, incomplete work, or broken promise.

Examples include:

• a patient calling because an expected confirmation did not arrive;
• a second contact because the first employee lacked correct information;
• a call after a portal workflow failed;
• repeated status checks because the organization provided no completion date; or
• another interaction after a transfer lost the original context.

The term failure demand is sometimes used for contacts caused by an organization's failure to do something or to do it correctly. The concept can be valuable, but the label can encourage premature judgment. A contact pattern should be investigated before leaders call it preventable.

SELAS perspective: Demand reduction should mean removing unnecessary patient effort and organizational failure. It should not mean discouraging legitimate contact or making access harder.

A healthcare example

Illustrative example: This scenario demonstrates how one need can produce different amounts of contact demand. It does not describe a particular organization or represent an industry benchmark.

A patient wants to know whether a referral is ready for scheduling.

Path A: visible status

The referring clinician submits complete information. The organization confirms receipt and gives the patient a realistic next step. Status remains visible through the patient's preferred accessible channel. When scheduling becomes available, the patient completes the task.

One underlying need may produce no assisted contact or one scheduled interaction.

Path B: uncertain status

The patient receives no confirmation. The portal does not show the referral. The patient calls a general number, waits, and reaches an employee who cannot see the referral. The patient contacts the referring office, then tries the health system again. A later employee locates the referral but cannot estimate when scheduling will occur.

The same need now creates several interactions across multiple functions.

The contact center must handle those interactions. But a staffing response alone will not remove the missing confirmation, inconsistent visibility, or unclear ownership that generated them.

Why channel shifting can mislead leaders

Organizations often celebrate a reduction in voice volume after launching digital service. That result may represent successful self-service, but volume movement alone does not prove success.

At least four outcomes are possible:

1. The digital channel completed the need with less patient effort.
2. The patient switched channels but required similar organizational effort.
3. The patient used digital service and still needed assisted support.
4. The patient failed to obtain help and disappeared from measured demand.

Evaluation should therefore include completion, repeat contact, channel switching, patient effort, accessibility, and unresolved work. A Canadian portal study found that many respondents reported easier scheduling and less repetition, while its authors also noted the need to understand workflow effects and broader limitations.⁵

The right question is not, “Did calls decline?” It is, “Did more people complete the underlying task with appropriate effort and outcomes?”

What contact volume does not tell us

Volume does not reveal:

• the number of unique people;
• the number of unique needs;
• whether the contact was necessary or preventable;
• whether the patient completed the task;
• the effort required before and after the interaction;
• whether another channel failed first;
• whether the person abandoned an unidentified attempt; or
• which organizational condition created the demand.

These limitations do not make volume unimportant. Contact volume is a fundamental workload input. It simply cannot carry the full interpretation leaders often place on it.

Measures to consider alongside demand

No single metric explains demand. Useful companion measures include:

Unique people and unique needs

These help distinguish growth in the number of people served from multiple interactions about the same issue.

Contact reason

A consistent reason taxonomy allows the organization to identify patterns. Categories should describe the patient's need rather than merely the destination queue.

Repeat-contact rate

This can show how often another interaction occurs within a defined period, but the organization must define whether it measures the same person, the same need, the same channel, or any subsequent contact.

Abandonment and redial behavior

Abandoned contacts may reappear as later attempts. Treating every arrival as a new need can distort demand estimates.

Transfer and channel-switch paths

These reveal how people move through the organization and where context may be lost.

Completion or resolution

This asks whether the organization completed the underlying task, not only whether an employee ended an interaction.

Patient effort

Steps, delays, repeated explanations, mode switching, and uncertainty can make access difficult even when each individual interaction appears acceptable.

From demand reporting to organizational learning

A useful demand-management process has six parts.

1. Define the underlying patient need.
2. Connect interactions across channels when privacy, identity, and data quality allow it.
3. Separate new needs from repeat attempts and follow-up contacts.
4. Identify the organizational condition associated with the pattern.
5. Assign the source problem to a leader who can influence it.
6. Monitor both demand and patient outcomes after the change.

The contact center should participate in this process, but it should not own every solution. Referral teams, digital teams, clinics, revenue-cycle functions, communications teams, and technology leaders may control the conditions that create demand.

Questions leaders should ask

1. Do our reports count contacts, unique people, unique needs, or some combination?
2. Which demand reflects normal service, and which demand may reflect uncertainty or failure?
3. How often does one need cross several channels or organizational functions?
4. Which digital experiences reduce patient effort, and which create assisted demand?
5. What happens to patients who abandon or never reach an identified interaction?
6. Which contact reasons are defined clearly enough to support action?
7. Who owns the upstream conditions behind our largest repeat-contact patterns?
8. When demand declines, how do we know the underlying need was completed rather than abandoned?

Decisions this concept should inform

Understanding the path from need to demand should shape:

• demand forecasting;
• channel and digital-service strategy;
• contact-reason taxonomy;
• repeat-contact analysis;
• patient communication;
• process-improvement priorities;
• cross-functional accountability;
• self-service evaluation; and
• investment in data that connects interactions with outcomes.

This entry addresses contact-center operations and does not provide clinical, legal, or regulatory advice. Organizations should apply their own clinical governance, privacy, compliance, accessibility, and legal requirements.