How a Contact Center Works

Contact Center Field Guide · Foundation 01

Best for: Healthcare executives, contact-center leaders, operational leaders, and emerging leaders
Helps with: Contact-center scope, capacity decisions, service design, technology priorities, and performance interpretation
Reading time: Approximately 10 minutes
Last reviewed: October 7, 2026

Executive summary

A modern healthcare contact center is not simply a group of people answering phones. It is a coordinated operating system that connects patient needs with information, resources, and action.

That system includes people, processes, knowledge, technology, data, and relationships with other parts of the organization. It may support voice, messaging, chat, email, portal assistance, and outbound communication. International contact-center standards likewise recognize that contact centers can operate across inbound and outbound interactions and multiple channels.¹

The contact center's performance therefore depends on more than employee effort. A patient may contact the organization to schedule a specialist visit, but the ability to resolve that request may depend on referral status, appointment availability, scheduling rules, system access, language support, and the authority to act.

This is why a contact center can appear to have a call-handling problem when the underlying cause sits elsewhere in the organization.

For executives, the central idea is straightforward: the contact center is where demand, capacity, organizational complexity, and patient experience meet. Its conversations also provide evidence about where patients struggle to navigate the system.

The concept in plain English

An industry definition describes a contact center as a coordinated system of people, processes, technologies, and strategies that gives customers access to information, resources, and expertise through appropriate communication channels.²

That definition matters because it shifts attention away from a physical room or telephone platform. A contact center is defined by the work it performs and the access it provides.

In healthcare, that work might include:

• scheduling or changing an appointment;
• answering a billing question;
• helping someone use a patient portal;
• locating a referral;
• explaining an administrative process;
• finding the correct service or department;
• supporting an outbound reminder or service campaign; or
• coordinating the next nonclinical step in a patient's journey.

These interactions can arrive through several channels. The channels differ, but the underlying operating challenge remains: connect a person's need with the right capability at the right time and complete as much of the work as the organization can safely and appropriately resolve.

The operating chain

Every contact center has an operating chain, whether leaders manage it explicitly or allow it to emerge through local decisions.

1. A person has a need

The process begins outside the contact center. A patient needs an appointment, information, assistance, reassurance, or action from the organization.

2. The need produces contact demand

The patient decides to contact the organization or responds to an outbound communication. One underlying need may produce several attempts if the person cannot find the right channel, abandons while waiting, reaches the wrong department, or does not receive a complete answer.

Contact volume is therefore not the same as the number of underlying needs.

3. The person enters through a channel

The interaction may begin through voice, chat, messaging, email, a portal, or another supported channel. Channel choice may reflect preference, urgency, accessibility, task complexity, or what the organization makes available.

Accessibility is part of operating design. Federal guidance emphasizes that people with communication disabilities must be able to receive information from and convey information to covered organizations effectively. The appropriate support depends on the nature, length, complexity, and context of the communication.³

4. The interaction becomes operating work

The work arrives at a particular time, with a particular level of complexity and an expected amount of effort. Leaders must understand not only how much work arrives, but when it arrives, which skills it requires, and whether it can wait.

5. Capacity meets demand

The organization forecasts demand, decides what responsiveness it intends to provide, calculates required capacity, and schedules employees with the appropriate skills.

Those decisions occur before the interaction, but the patient experiences their consequences in real time.

6. Routing connects work with resources

Technology and operating rules direct the interaction to an employee, team, automated service, or deferred queue. Routing may consider channel, language, service line, reason for contact, geography, urgency, or employee skill.

More specialization can improve expertise. It can also fragment capacity and increase transfers. Routing design always involves tradeoffs.

7. The organization acts

The employee or automated service uses processes, knowledge, systems, and organizational authority to address the request. The quality of the interaction depends partly on communication skill, but also on whether the representative has accurate information and the ability to act.

8. The interaction produces an outcome

The patient may receive a complete resolution, a partial answer, a transfer, a callback commitment, deferred work, or no resolution at all.

An interaction can end while the underlying need remains open. That distinction is essential.

9. The organization learns, or fails to learn

Contact reasons, transfers, repeat attempts, complaints, conversation themes, and unresolved work can reveal where patients encounter friction. The organization can use that evidence to improve the source process and reduce future demand.

Without a structured feedback loop, the contact center repeatedly absorbs the consequences of problems it cannot correct.

Why queues form

Contact-center demand does not arrive evenly. Ten interactions may arrive within a few minutes and very few may arrive shortly afterward. The time required to complete each interaction also varies.

Employees cannot always become available at the exact moment work arrives. When incoming work temporarily exceeds available capacity, work waits in a queue.

This creates an important executive lesson: annual and daily averages can conceal the operating reality. A center can appear to have enough total labor across a month while still leaving patients waiting during predictable periods of the day.

Queue performance depends on the timing and variability of demand, the capacity available during each interval, routing choices, employee availability, and the responsiveness the organization intends to provide. Later Field Guide entries will examine these relationships in detail.

Six capabilities that must work together

No single department, employee, or technology creates a successful contact-center interaction. Six capabilities operate together.

Demand and access

Leaders must understand why people contact the organization, which channels they can use, what prevents successful access, and which demand the organization could prevent through clearer communication or better processes.

Workforce and capacity

The organization must translate expected work into people with the right skills at the right times. This includes forecasting, staffing, scheduling, attendance, and daily adjustments as actual conditions differ from the plan.

Process and authority

Employees need clear processes and enough authority to complete appropriate work. A well-trained employee cannot resolve an interaction if policy requires unnecessary approval or the work must pass through several disconnected teams.

Knowledge and skills

Representatives and automated services need accurate, understandable, current information. Employees must also know how to interpret that information, communicate it effectively, and recognize when the request requires escalation.

Technology and data

Technology routes interactions, presents information, records work, connects systems, supports communication, and produces operating data. Poor integration forces employees and patients to bridge gaps manually.

Organizational partners

Contact centers often depend on clinics, referral teams, revenue-cycle functions, digital teams, information technology, language services, and other operational groups. The contact center may own the interaction without controlling every resource required for resolution.

A weakness in any one capability can appear in common operating measures. Longer handle time may reflect system latency. Transfers may reflect fragmented ownership. Repeat contacts may reflect incomplete downstream work. Long waits may reflect a capacity problem, but they may also reflect unexpected demand created elsewhere.

An illustrative healthcare example

Illustrative example: This scenario demonstrates how operating dependencies can affect a patient interaction. It does not describe a specific organization or represent an industry benchmark.

A patient receives a referral and contacts a health system to schedule a specialist appointment.

When the system works

The interaction reaches the correct scheduling team. The referral is visible and complete. Scheduling rules are clear. The employee can identify appropriate availability and has authority to schedule it. Language or accessibility support is available when needed. The patient receives an appointment and understandable next steps during the interaction.

The patient experiences one contact and one resolution.

When the system fragments

The referral is not visible, or information is missing. The patient reaches a general queue and is transferred. The next employee can see the referral but cannot act until another department corrects it. Follow-up work enters a separate queue. The patient receives no reliable completion date and contacts the organization again.

The original need now appears in several operating measures:

• more contact volume;
• additional handle time;
• one or more transfers;
• deferred work;
• a repeat contact;
• greater patient effort; and
• a longer path to care.

Hiring more contact-center employees might reduce the wait before the first conversation. It would not correct the missing referral information or fragmented process that prevented resolution.

Research supports treating telephone access as part of the broader patient-access experience. One Veterans Health Administration study found an association between faster call answering and better patient perceptions of urgent-care access, while also finding that the relationship did not extend to every access measure examined.⁴ Other qualitative research found that patients facing telephone barriers sometimes waited, gave up, or sought unscheduled in-person care.⁵ These studies do not establish a universal service target, but they show why communication access deserves executive attention.

Availability and work placement

The contact center's primary role is to remain available for patient needs and resolve them effectively. That does not mean every activity must end when the interaction ends.

Some requests create legitimate follow-up work. A representative may need to obtain missing information, complete documentation, coordinate with another department, or confirm that an action occurred. The organization must decide where and when that work should happen.

Leaders should distinguish four categories:

1. Work necessary to resolve the current interaction
2. Deferred work created by the interaction
3. Administrative work assigned to the contact center for organizational convenience
4. Work requiring a specialized operational or clinical team

The purpose of this distinction is not to push work away. Work consumes capacity somewhere. The purpose is to assign it deliberately, protect patient access, and give each activity the skills and controls it requires.

SELAS perspective: Contact centers should accept the work required to fulfill their service promise. They should not become the default home for unrelated work simply because they have a measurable workforce and a queueing platform.

If employees perform both live interactions and deferred administrative work, leaders should make the tradeoff visible. Every hour assigned to offline work is an hour unavailable for new contacts unless the staffing model accounts for it.

What executives often see incorrectly

High volume does not have one meaning

Volume can reflect growth, successful outreach, seasonal need, unclear communication, digital failure, limited appointment availability, repeat attempts, or unresolved work. A volume report describes activity. It does not explain the cause.

A service problem is not always a staffing problem

Insufficient capacity can create waits. So can an inaccurate forecast, poor schedule fit, unexpected absence, routing complexity, system disruption, or a surge in demand caused elsewhere.

A shorter interaction is not always a better interaction

Lower handle time may reflect simpler work or a more efficient process. It may also reflect premature transfers, incomplete documentation, rushed conversations, or failure to resolve the need.

A transfer is not automatically a failure

Specialized work sometimes requires a transfer. The more important questions are whether the transfer was necessary, whether the patient reached the right destination, and whether the receiving team had the context required to continue.

High occupancy can conceal fragility

Keeping employees continuously busy may appear efficient. It can also leave little capacity for normal variation, learning, coaching, complex work, or recovery after a disruption.

These examples show why individual metrics should never substitute for understanding the operating system.

The contact center as an organizational sensor

Healthcare contact centers hear where people struggle to navigate an organization. Interactions may reveal:

• unclear instructions;
• unavailable appointments;
• referral or authorization friction;
• billing confusion;
• failed digital experiences;
• inconsistent policies;
• broken handoffs;
• unmet language or accessibility needs; and
• repeated service failures.

This evidence can support system improvement, but raw interaction data are not automatically organizational intelligence.

The organization must classify the issue consistently, identify meaningful patterns, validate those patterns against other evidence, assign an owner, correct the source process, and monitor whether the change produces a better outcome.

Contact-center data also have limitations. They represent people who reached a measured channel. They may omit people who could not find the channel, abandoned before identification, used an unmeasured path, relied on someone else for help, or gave up entirely.

A recent consensus framework developed with US health-system leaders included contact-center management among the major components of patient-access management, alongside leadership, capacity management, appointment availability, data, process simplification, and timely connection to care.⁶ That broader view is important: the contact center contributes to access, but it cannot create access alone.

Questions leaders should ask

1. What patient needs generate the most demand, and which parts of the organization create or influence that demand?
2. Can people reach us through channels that are appropriate and accessible for them?
3. Do we measure successful resolution or mainly activity and speed?
4. Which contacts require transfers, callbacks, or repeat attempts, and why?
5. What work prevents employees from remaining available for new patient needs?
6. Where do employees lack the knowledge, authority, access, or system capability to complete a request?
7. Which apparent contact-center problems originate outside the contact center?
8. How does interaction evidence reach the leaders who can correct those problems?
9. Which people or unmet needs may be absent from our current data?

Decisions this concept should inform

Understanding the contact center as an operating system should influence:

• the center's organizational role and scope;
• channel strategy and accessibility;
• ownership of deferred and administrative work;
• workforce and capacity investment;
• routing and skill design;
• technology and integration priorities;
• measures of access and resolution;
• cross-functional governance; and
• the use of conversations to improve the broader organization.

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.