Synchronous Communication in Customer Service
Synchronous communication is any customer interaction that happens in real time — both parties present, both engaged, both waiting on each other for the next reply. Phone calls and live chat are the everyday examples. Synchronous channels are where contact centres have nowhere to hide: the customer is there, right now, and service failures are felt immediately.
Why it matters
Synchronous channels are the highest-stakes mode in customer service. Tone, timing, empathy and capacity all show up live. Get it right and customer satisfaction moves immediately; get it wrong and the failure is visible in real time.
What makes this mode powerful
Real-time engagement delivers what no other channel can — immediate clarification, tone and emotion conveyed naturally, and complex issues resolved in a single interaction. But it requires live capacity, every minute it's open.
What this guide covers
A clear definition, the synchronous channels in use today, where sync outperforms async, the staffing and KPI model it demands, the pitfalls that cost centres most, and how to know when your sync channels are actually working.
What is Synchronous Communication?
Synchronous communication occurs in real time. Both parties are present and engaged simultaneously, trading information back and forth in a continuous conversation. It is characterised by immediate feedback, live interaction, and the implicit expectation that the other side is waiting for your next reply.
Plain-English Definition
Synchronous means "at the same time." Both the customer and the agent are engaged together, and silence on either side is noticed instantly. Walk away from a live chat and you'll hear about it. Walk away from an email and nobody notices for hours.
✓ What synchronous communication IS
- Real-time, live two-way exchange
- Both parties present and engaged simultaneously
- Immediate feedback and tone cues
- Customer expectation: "you are with me now"
✕ What synchronous communication is NOT
- Staffable at arbitrary convenience — it requires live capacity
- The right fit for every customer interaction
- The same thing as "fast" — async can be fast too
- Defined by the channel alone — defined by customer expectation of immediacy
The counterpart
Synchronous and asynchronous communication are paired modes — you can't understand one properly without the other. Where synchronous means real-time presence, asynchronous means engagement on each party's own schedule. Both have their place; the strategic question is matching the mode to the interaction.
Synchronous Channels in Customer Service
Synchronous and asynchronous channels sit alongside each other in every modern contact operation — but they behave very differently. The diagram below shows both modes side by side, with the synchronous channels highlighted. The messaging apps category sits at the boundary between them, which is the source of most customer expectation failure in modern customer service.
Synchronous channels at a glance, with the asynchronous counterpart shown alongside. Messaging apps sit at the boundary — the category where customer expectations and operating models most often diverge.
Four synchronous channels dominate customer service in Australia today. Each has its own staffing model, agent skill requirement and customer expectation profile.
Phone Calls
The original synchronous channel. Direct verbal dialogue, immediate clarification, tone and emotion carry through naturally. Customer expectation of response is measured in seconds, not minutes. Still the dominant channel for complex, urgent or emotionally charged interactions.
Live Chat
Real-time text exchange via a website or app chat widget. Agent and customer both present. Tone is harder to read than voice, but the real-time expectation is identical. Agents can typically handle two to three concurrent chats — higher concurrency erodes quality.
Video Conferencing
Face-to-face via Zoom, Teams or Webex. Adds visual cues to voice and extends synchronous interaction to screen sharing, product demonstrations and more complex issue resolution. Increasingly used for premium support, financial services and healthcare.
In-Person Service
The highest-bandwidth synchronous mode. Physical presence, full non-verbal communication, no channel mediation. Retail counters, service desks, branch banking. Often underestimated but still the mode where complex or high-value interactions land.
Synchronous vs Asynchronous — When Each Wins
Neither mode is universally better. The question is never "sync or async" — it's "what is this specific interaction asking for?"
When synchronous wins
Complex issues requiring live clarification. Emotionally charged interactions. Sales conversations where objection-handling matters. Outages and emergencies. Any scenario where tone, empathy and immediate dialogue materially change the outcome.
When asynchronous wins
Documentation-heavy requests (claims with attachments, policy changes). Non-urgent general enquiries. After-hours contact. Customers who want a written record. Interactions where the customer benefits from time to think.
When it's a judgement call
Routine account enquiries, status updates, simple changes. These work either way — the right answer is usually whichever mode costs less to serve at the quality level the customer expects.
The principle behind the choice
Choose synchronous when the cost of delay or miscommunication is high. Choose asynchronous when the cost of live capacity exceeds the benefit of immediacy. Most centres default one way or the other out of habit rather than design — the result is channels used for the wrong jobs, staffed on the wrong model, and measured against the wrong KPIs.
Channel Performance — What the Data Says About Sync
The 2024 Australian Contact Centre Best Practice Report measured abandonment rate across channels. Synchronous channels show higher abandonment than asynchronous — but the gap tells a more interesting story than it first appears.
Abandonment Rate by Channel Type — Australian Contact Centres
Source: 2024 Australian Contact Centre Industry Best Practice Report.
Reading this from the sync perspective
Synchronous channels expose failure. That's not a weakness — it's honesty. When your voice queue hits 8% abandonment, you know about it. When your live chat drops to 7%, you know about it. The operational signal is immediate, the customer impact is measurable, and the lever that fixes it (service level) is well understood.
Async's 3% is not the benchmark sync should chase. It's largely a measurement artefact — customers don't really "abandon" an inbox, they just drift away and never come back. The business never registers it as a failure. The apparent sync-async gap isn't about customer patience; it's about what each mode makes visible.
For the full framework on reading these numbers honestly, see the Abandonment Rate glossary term.
Key Components of a Synchronous Operation
Running synchronous channels well requires four components working in concert. None of them are optional.
Accurate Interval Forecasting
Synchronous channels live and die at interval level. A daily forecast is not enough — you need volume forecasts by 15- or 30-minute interval, by channel and contact type. Under-forecasting at interval level is the single most common cause of sync service failure.
Erlang-Based Capacity Planning
Sync staffing is non-linear — doubling volume doesn't mean doubling staff. Erlang C and related models translate interval forecasts into required staffing based on service level, handle time and shrinkage. Every sync channel needs this; no exceptions.
Disciplined Intraday Management
Real-time adherence, skill-based routing, intraday re-forecasting and rapid escalation protocols. When reality diverges from the plan — and it always does — intraday is what keeps service level on target.
Agent Capability for Live Handling
Live-mode agents need different skills from async-mode agents: real-time tone management, fast cognitive switching between concurrent conversations (for chat), and the ability to handle emotional content without recovery time. Train for the mode, not just the subject matter.
How to Run Synchronous Channels Well
Six practices separate well-run sync operations from ones that firefight every intraday. None are novel — but together they are what disciplined sync operations look like.
Set a service level objective and manage to it
Every sync channel needs an explicit service level target (e.g. 80/20 for voice, 90/30 for chat). Staff to the target, measure performance at interval level, and accept that the right lever on customer experience is service level — not abandonment, handle time, or any downstream metric.
Don't blend sync and async into single queues
The two modes require different capacity planning. A universal agent pool handling both looks efficient on paper and fails in practice — live demand always wins over queued demand, and async SLAs get quietly missed.
Match chat concurrency to quality
Two to three concurrent chats per agent is the sustainable zone for most centres. Higher concurrency erodes handle time, tone and first-contact resolution — and the cost saving disappears in repeat contacts.
Route by intent, not by channel
A complex escalation that starts on voice should be able to pivot to video. A sales conversation that starts on chat should be able to move to a phone call without starting over. The sync infrastructure should support seamless mode shifts when the interaction demands it.
Measure with the right KPIs
Service level, average speed of answer, abandonment rate, and first-contact resolution are the sync metrics. First-response time, case cycle time, and resolution rate are async metrics. Don't mix them.
Invest in live-mode training, not generic communication training
Real-time handling is a distinct skill set. Agents managing concurrent chats need different capabilities from voice agents, and voice agents on complex lines need different training from general enquiry handlers. Generic "customer service skills" courses don't cover this.
Benefits of Well-Run Synchronous Channels
Immediate Resolution
Complex issues resolved in a single interaction, rather than stretched across multi-day async exchanges that erode customer patience.
Tone and Empathy at Full Resolution
Voice and video carry emotional content that text strips out. For sensitive interactions — complaints, claims, care — the mode itself is part of the service.
Strong Sales Conversion
Real-time objection handling converts at rates async channels cannot match. For revenue-generating centres, sync is where the commercial outcome is made or lost.
Honest Operational Signal
Sync failures are measured in real time. You don't wait for a survey or a complaint to discover the problem — service level, abandonment and AHT tell you immediately.
First-Contact Resolution Lift
Real-time clarification means fewer follow-ups, fewer repeat contacts, and lower downstream cost. FCR on well-run sync channels is typically higher than on equivalent async channels.
Trust and Brand Preference
Customers remember interactions where someone was actually there. In a multichannel world where most customer service feels automated or delayed, genuine real-time service is a brand advantage.
Common Pitfalls in Synchronous Operations
Over-concurrency on live chat
Pushing agents to four, five, or six concurrent chats looks efficient on paper. In practice it kills handle time quality, tone and first-contact resolution — and the repeat contacts that follow wipe out the savings.
Treating voice as a cost to reduce rather than a channel to optimise
Many centres frame voice as legacy and push customers to async. For complex, urgent or emotional interactions, this is a downgrade the customer feels. Voice isn't legacy — it's the right channel for the right interactions.
Staffing sync channels on async assumptions
Sync requires live-capacity scheduling to an Erlang model. Staffing to a "headcount divided by volume" average guarantees intraday service level failures — which then show up as abandonment spikes.
Chasing the 3% async abandonment benchmark
Synchronous abandonment is genuinely measurable; async isn't comparable. Trying to match async's apparent abandonment rate is chasing a measurement artefact, not a performance target.
Blended skilling without live-mode specialisation
Cross-skilling agents across voice, chat and video without training them specifically for live handling produces mediocre performance in all modes. The skills are genuinely different, even when the subject matter is the same.
No intraday re-forecasting
Synchronous channels are volatile. A morning that runs 15% over forecast will destroy the afternoon's service level if no one re-forecasts and re-allocates. Daily planning is not enough.
Frequently Asked Questions
What's the simplest way to remember synchronous versus asynchronous?
Synchronous = "at the same time." Both parties are present and engaged live — phone, chat, video. Asynchronous = "not at the same time." The customer sends, the agent replies later — email, messaging, social. The difference is the expected response time, not the channel itself.
Is live chat always synchronous?
Technically yes — but in practice many modern chat widgets are async dressed up as sync. If the message sits in a ticket queue with a one-hour SLA, it's async regardless of the interface. The test is whether a human is actively waiting to respond, or whether it joins a queue for later. If it's the latter, it's asynchronous.
Which channel is more expensive to operate?
Synchronous channels are generally more expensive per interaction because agents can typically handle only one voice call at a time (or two to three concurrent chats). Async allows much higher concurrency — dozens of tickets per shift per agent. But "more expensive per interaction" is not the same as "more expensive overall" — sync's first-contact resolution and conversion rates often mean lower total cost-to-serve.
Should I push customers from voice to chat or messaging?
Only if you can genuinely match customer expectation to the operating model. A customer who wanted a two-minute phone call and instead gets a three-day messaging resolution is a lost customer, not a cheaper one. The channel shift only works when the interaction type genuinely fits a lower-touch mode — not just because voice is expensive.
Why do synchronous channels show higher abandonment rates?
Partly because customers can abandon them — a queue is something you leave. More importantly, async channels don't really measure abandonment the same way; the customer who "abandons" an email just never follows up, and the business never registers it as a failure. The apparent 3% vs 7% gap is as much about measurement as behaviour. See the Abandonment Rate page for the full framework.
How many concurrent chats should a live chat agent handle?
Two to three for most contexts. Higher concurrency degrades handle time, tone, and quality — and for complex or emotional interactions, even three is too many. Treat concurrency as a quality variable, not a productivity one.
What training do synchronous agents need that's different from async?
Real-time tone management, rapid cognitive switching (for concurrent chat handling), live conflict de-escalation, and the ability to handle emotional content without needing recovery time between interactions. Async training focuses on written communication craft and considered problem analysis — different skills entirely.
Where to Next
Summary
Synchronous communication is any real-time customer interaction where both parties are present and engaged together — phone, live chat, video, in-person. It's the highest-stakes mode in customer service because there is nowhere to hide: service failures are felt immediately, the operational signal is honest, and the lever that fixes it (service level managed at interval level) is well understood.
Sync channels deliver what no other mode can — immediate clarification, tone and emotion conveyed naturally, complex issues resolved in a single interaction, and real-time sales conversion. They cost more per interaction because live capacity is genuinely expensive, but the first-contact resolution uplift and customer trust they produce typically deliver lower total cost-to-serve than async equivalents for the interactions that genuinely need live handling.
Run synchronous channels on their own terms. Erlang-based forecasting, interval-level service level management, chat concurrency kept at quality-preserving levels, intraday discipline, and training specifically for live-mode handling. Don't chase async abandonment benchmarks — they aren't comparable. Don't blend sync and async capacity — they require different models. And don't treat voice as legacy — it's the right channel for interactions that reward being there. For the counterpart mode, see asynchronous communication.
