Contact Centers and High-Volume Voice

The MSP's Guide to VoIP: Part 16 of 20

Disclaimer: This post is educational content about contact center deployment and compliance considerations for MSPs. It is not legal advice. Regulations change, interpretations vary, and your specific situation may differ from the general scenarios described here. Consult with a telecom attorney to determine how these regulations apply to your business.

There is a moment in most MSP-client relationships where someone asks for something that a regular phone system is not designed to do. They want to know how many calls were missed last Tuesday. They want calls routed to the agent who has been idle the longest. They want calls recorded for training purposes. They want a wallboard in the call center showing real-time queue statistics.

These are contact center requirements, and the distinction between a phone system with a queue feature and an actual contact center platform is one of the most important lines in voice services. Getting it right means delivering a solution that genuinely improves the client's operations. Getting it wrong means deploying a phone system that almost does what they need, which is worse than not doing it at all because it creates the expectation without delivering the result.

The difference between a queue and a contact center

Most PBX platforms, hosted and on-premises, include some form of call queuing. Calls come in, if all agents are busy the caller waits in a queue, and when an agent becomes available the next call is delivered. Basic queue features include hold music, position announcements, and perhaps a timeout that sends the caller to voicemail if the wait exceeds a threshold.

This is fine for a business that receives moderate call volume and just needs an orderly way to handle peaks. A medical office with three receptionists, a small law firm, a landscaping company during spring. The queue smooths out the bumps.

A contact center is different in kind, not just degree. The contact center model assumes that managing call flow is a core operational function with dedicated staff, metrics, and management processes. It includes:

Automatic Call Distribution (ACD) with sophisticated routing that goes well beyond first-in, first-out. ACD is the engine that decides which agent gets which call, and the routing strategy is a business decision.

Real-time monitoring so supervisors can see what is happening right now: how many calls are in queue, which agents are available, which are on calls, how long the longest wait is.

Historical reporting so management can analyze performance over time: service level percentages, average handle times, abandonment rates, peak periods, agent utilization.

Agent state management so the system knows whether an agent is available, on a call, in after-call work, on break, or logged out, and routes calls accordingly.

Recording and quality management for compliance, training, and dispute resolution.

A PBX queue does not provide these things, or provides them only in a limited way that does not scale. If the client needs any three of the five items above, they need a contact center platform, not a PBX with a queue.

ACD routing strategies

The routing strategy determines how the ACD selects which agent receives the next call. Different strategies suit different operations.

Round robin. Calls are distributed evenly across agents in a fixed order. Agent A gets the first call, agent B gets the second, agent C gets the third, then back to A. This is simple and ensures even distribution, but it does not account for agent availability or skill.

Longest idle. The call goes to the agent who has been waiting the longest since their last call. This produces the most even workload distribution and is the most common strategy for general-purpose queues.

Skills-based routing. Calls are routed to agents based on their skills. A Spanish-speaking caller gets routed to a bilingual agent. A technical support call gets routed to a tier-2 agent. A VIP customer gets routed to the senior team. Skills-based routing requires defining skill groups, assigning agents to groups, and configuring routing rules that match call attributes (dialed number, IVR selection, caller ID, time of day) to skill requirements. Before building a complex IVR tree, map the menu structure with an IVR Planner to visualize the paths callers will follow and catch dead ends before they go live.

Priority routing. Certain calls jump the queue based on criteria: VIP customer, callback request, escalation from another queue. Priority routing can be combined with skills-based routing so that a high-priority call still goes to a qualified agent.

The choice of routing strategy is a business decision that the client's operations team should drive, with the MSP implementing and configuring it technically. The MSP should understand the options well enough to advise, but the business rules come from the people running the call center.

Reporting

Contact center reporting divides into real-time and historical, and both are essential.

Real-time metrics

Real-time data is typically displayed on a wallboard (a monitor or web dashboard visible to agents and supervisors) and includes:

• Calls in queue: How many callers are waiting right now.
• Longest wait: How long the longest-waiting caller has been in queue.
• Available agents: How many agents are ready to take a call.
• Service level: The percentage of calls answered within the target time (e.g., 80% of calls answered within 20 seconds).

These metrics tell supervisors whether the current staffing is adequate for the current call volume. If the queue is building and the longest wait is climbing, they need more agents on the phones now.

Historical metrics

Historical reporting is used for planning, performance management, and identifying trends:

• Service level over time: Were staffing levels adequate each hour, each day, each week?
• Average handle time (AHT): How long does a typical call take, from answer to the end of after-call work? This is the key input for staffing models.
• Abandonment rate: What percentage of callers hang up before being answered? High abandonment indicates insufficient staffing or excessive wait times.
• Average speed of answer (ASA): How long does the average caller wait before being connected to an agent?
• Peak periods: When are call volumes highest? Are there patterns (Monday mornings, first of the month, after marketing campaigns)?

Historical data informs hiring decisions, scheduling, training priorities, and process improvements. Without it, the contact center is operating blind.

Call recording

Call recording is a common requirement in contact centers, driven by compliance, training, quality assurance, and dispute resolution. The implementation details matter more than most people realize.

Where recordings are stored

Recordings need to be stored securely and with appropriate retention. For cloud contact center platforms, the provider typically handles storage. For on-premises systems, recordings are stored locally or pushed to a file server or object storage. The storage requirements add up: a single G.711 call at 64 kbps generates approximately 0.5 MB per minute of recording (roughly 1 MB per minute when storing both sides separately). A contact center handling 500 calls per day averaging 5 minutes each produces about 2.5 GB of recordings per day, or roughly 50 to 75 GB per month depending on format and overhead.

Plan the storage, retention, and backup strategy before deploying recording. Running out of disk space and losing recordings is both an operational failure and, in regulated industries, a compliance violation.

Compliance considerations

PCI DSS. If the contact center handles payment card data (credit card numbers, CVVs), PCI DSS requires that this data not be recorded. Most compliant recording systems can pause recording during the payment portion of a call, either manually (the agent presses a button) or automatically (the system detects DTMF tones or integration with the payment system triggers a pause). This is a non-negotiable requirement for any business that processes payments over the phone.

HIPAA. Healthcare organizations that record calls containing protected health information (PHI) must ensure recordings are stored, transmitted, and accessed in compliance with HIPAA. This includes encryption at rest and in transit, access controls, audit logging, and Business Associate Agreements with any third party that handles the recordings.

State recording laws. Some states require all-party consent for call recording (all parties to the call must be informed and consent to recording), while others require only one-party consent. The client needs to understand the laws in their state and the states their callers are in, and configure appropriate recording announcements. This is a legal question, not a technical one, and the MSP should flag it rather than answering it.

CRM and ticketing integration

A contact center that is not integrated with the client's CRM or ticketing system creates unnecessary manual work for agents. The key integrations are:

Screen pop. When a call arrives, the agent's screen automatically displays the caller's record from the CRM, pulled by matching the incoming caller ID to a customer record. The agent immediately knows who is calling and can see their history without asking. This reduces handle time and improves the caller's experience.

Click-to-dial. Agents can initiate outbound calls from within the CRM by clicking a phone number. The contact center system places the call and connects it to the agent's phone. This eliminates misdials and saves time.

Automatic call logging. After a call ends, the contact center system automatically creates a record in the CRM or ticketing system with the call details: caller, agent, time, duration, and optionally a link to the recording. This ensures that every interaction is documented without relying on agents to remember to log their calls.

Most cloud contact center platforms have pre-built integrations with major CRM systems (Salesforce, HubSpot, Zoho, ConnectWise, Autotask). On-premises systems typically require API integration work or third-party middleware.

Infrastructure requirements

Contact centers have higher infrastructure demands than standard phone deployments because of the number of concurrent calls and the additional services running alongside voice.

Bandwidth. A contact center with 30 agents might have 25 to 30 concurrent calls at peak. Using G.711, that is approximately 2.5 to 3 Mbps of upload bandwidth just for voice. Add screen sharing, CRM web traffic, recording upload, and agent desktop activity, and the total bandwidth requirement climbs. If the client adds AI voice agents to handle first-tier calls, the math changes again: automated agents generate concurrent call volumes and traffic spikes that human staffing models do not predict. Dedicated internet access is often appropriate for contact center locations because it provides guaranteed bandwidth and real SLAs.

PoE budget. Every agent desk has a phone, and possibly a headset base station that also requires PoE. Conference rooms and common areas add more devices. Size the switch PoE budget for the full agent count plus growth.

QoS. QoS is critical in contact centers because the high volume of concurrent calls amplifies the impact of any congestion. A quality problem that causes a brief hiccup on one call in a 10-phone office causes hiccups on 25 calls simultaneously in a contact center. The QoS configuration needs to accommodate the higher concurrent call count.

Redundancy. A contact center that goes down means the business is not taking calls. For many businesses, not taking calls means not generating revenue. Internet redundancy, power redundancy (UPS for network equipment and phones), and platform redundancy (cloud platforms with multi-region failover) are appropriate for contact center deployments in a way that might be overkill for a standard office.

When to deploy a dedicated platform

The decision between stretching a standard PBX and deploying a dedicated contact center platform usually comes down to a few questions:

Does the client have dedicated staff whose primary job is answering calls? If yes, they need a contact center.

Does the client need real-time visibility into queue performance? If yes, they need a contact center.

Does the client need historical reporting for staffing and performance management? If yes, they need a contact center.

Does the client need skills-based routing? If yes, they need a contact center.

If the answer to all of these is no, a PBX with a basic queue feature is probably sufficient.

For cloud contact center platforms, the MSP typically resells or co-manages the platform (similar to the service models discussed earlier in the series). For on-premises contact center deployments, the MSP is taking on a significant implementation and management commitment.

The contact center space is one where the MSP's value is highest. The client is unlikely to have the expertise to evaluate, deploy, configure, and maintain a contact center platform on their own. The MSP that can do this well has a deeply embedded, high-value relationship with the client.

Next up: The Regulatory Landscape: What the FCC Considers a Voice Service Provider, where the compliance section begins, covering what MSPs need to know about voice service regulation.