Asynchronous Messaging

Asynchronous messaging is customer service by message where the customer and agent don't need to be present at the same time - the customer can send a message, leave, and pick the conversation up later, through channels such as SMS, in-app messaging, WhatsApp or Facebook Messenger.

What is asynchronous messaging?

Asynchronous messaging is a way for customers and organisations to communicate by message without both being online at the same time. A customer sends a message while waiting for the bus, gets on with their day, and reads the reply when it suits them. The conversation stays open, with its history, until the issue is resolved.

Typical channels include:

  • SMS, including two-way text conversations.
  • In-app messaging within an organisation’s own app or customer portal.
  • Third-party messaging apps such as WhatsApp, Facebook Messenger and Apple Messages for Business.
  • Persistent web messaging, where a website chat can continue after the customer closes the page.

The word “asynchronous” is the key. In synchronous channels, such as phone and live webchat, both people are present and the conversation happens in one sitting. In asynchronous channels, each side replies in their own time.

Why it is growing

  • It fits how people communicate. Many customers already message family, friends and businesses throughout the day. They expect to do the same with service providers.
  • No waiting on hold. The customer isn’t stuck in a queue or tied to a browser window.
  • Rich and accurate. Customers can send photos, screenshots and documents, and agents can send links and confirmations.
  • Efficient for agents. Because replies aren’t needed instantly, agents can work several conversations at once and the workload can be smoothed across the day.
  • Proactive potential. Organisations can start conversations too, for example with an appointment reminder or an outage update that customers can reply to.

How it changes contact centre operations

Asynchronous messaging needs different planning from voice:

  • Forecasting and staffing. Workforce management has to model open conversations and response time targets rather than calls arriving in real time. Work can be deferred within limits, which helps smooth demand.
  • Continuity. The next message in a conversation may be picked up by a different agent, so a complete history in the CRM is essential. This is where omnichannel foundations matter.
  • Measurement. Useful measures include time to first response, time between responses and total time to resolution. Handle time per message can be misleading on its own.
  • Automation. Chatbots can answer simple messages instantly, gather details before an agent joins, and keep the customer informed out of hours.

Good practice

  1. Set expectations in the first reply, including when the customer will hear back.
  2. Triage by urgency. A message about a safety issue or a vulnerable customer shouldn’t wait in a queue behind routine questions.
  3. Close conversations clearly, and make it easy for the customer to reopen them.
  4. Protect privacy. Agree what can be discussed on third-party apps, and how customers are identified before account details are shared.
  5. Know when to switch. Some issues are faster by phone. Agents should be able to offer a call without losing the thread.

Used well, asynchronous messaging is a low-effort option for customers and a flexible one for contact centres. It also supports channel shift away from the phone for routine contacts, without forcing customers into self-service.

How Telnet Helps

Where Telnet comes in

Telnet handles written channels, including email, webchat and social media messaging, alongside phone, with the same trained onshore agents and the same quality standards.

  • One conversation history. In ContactSuite, the built-in CRM keeps one view of each customer across phone, email, SMS and webchat, so whichever agent picks up the next message can see what was said before.
  • Work sorted by content. Iris, our AI agent assist, captures details from email, routes and prioritises work by what it is about, and writes up the outcome, so urgent written contacts don’t sit behind routine ones.
  • Capacity that flexes. Because written work doesn’t need an instant answer, it fits well with our blended model: shared agents move between queues as demand changes, and you pay per interaction, not per seat.

If you are considering adding messaging, we can help you work out which contact types suit it and what response times to set.

FAQ

Asynchronous Messaging FAQs

What's the difference between asynchronous messaging and webchat?

Webchat is synchronous: both sides are present and the chat ends when the customer leaves the page. Asynchronous messaging keeps the conversation open, so the customer can reply minutes, hours or days later, often from their phone, without starting again. Many modern platforms blur the two, letting a webchat continue as a message thread after the customer leaves.

Is email a form of asynchronous messaging?

Technically yes, since neither side needs to be present at the same time, but the term usually refers to conversational channels such as SMS, in-app and social messaging. These feel more like a running conversation than email: messages are short, threads stay together, and customers expect faster replies than they would for an email.

What response time should we set for messaging?

Commonly somewhere between a webchat and an email: minutes to a few hours, depending on the channel and the issue. Set clear expectations in the first automated reply, and prioritise by urgency rather than strictly by arrival time. Safety issues and vulnerable customers should be identified and escalated quickly, whatever the channel.

Ready to scale?

Outsourced contact centre
for New Zealand & Australia.

30+ years. 100% onshore. The leading provider to the energy & utilities industry.

Get in Touch