Blocker 34 · Solutions

Customers give up on web chat: fixing chat abandonment with the Amazon Connect communications widget

Chat is supposed to be the easy channel. But a chat window that goes quiet, forgets the conversation when the page changes, or can't take a photo of the problem loses customers fast. Amazon Connect has a fix for each of those.

7 daysHow long a chat flow's Wait block can keep waiting for the customer to come back and send a message.Source: AWS, Wait flow block documentation

Illustration. The blocker: Customers give up on web chat. The fix: Chat that keeps the conversation going.

The blocker

A customer opens the chat on your website with a quick question. A message says an agent will be with them shortly. Then nothing. No position in line, no estimate. They switch to another tab to keep working, miss the agent’s reply, and the chat times out. Or they click to another page and the chat starts over. Some try to describe a problem that would take one screenshot to show, and give up.

Chat abandonment rarely means customers don’t want to chat. It means the chat experience asked them to wait in silence, stay on one page, or type out what they could have shown.

Why it happens

  • The queue is silent. Voice callers hear music and messages. Chat customers often see nothing while they wait.
  • The widget forgets. A page change or a new tab starts a new chat, and the customer loses their place.
  • Customers can’t see that the agent replied. If they move to another tab, the reply sits unread.
  • There is no way to share files. Error messages, photos and documents have to be described in text.
  • The agent starts cold. The chat arrives with no idea who the customer is or what page they were on.

How Amazon Connect solves it

Amazon Connect provides a hosted communications widget that you configure in the admin website and add to your site with a short snippet. Because Amazon Connect hosts it, the latest version is always live. The rest is configuration and flow design. We covered enabling chat and routing it with other channels in Voice, chat, SMS and email live in separate tools.

1. Start the chat already knowing the customer

Your website can pass contact attributes into the widget, such as a member ID or the page the customer is on, inside a JSON web token signed with the widget’s security key. Agents see them in the Contact Control Panel, and flows can use them. A pre-chat form captures the reason for the chat before it starts. If your customers sign in first, pre-chat authentication with the StartChatContact API marks the chat as authenticated.

2. Don’t let the queue go quiet

The default customer queue flow does not support chat out of the box, because its Loop prompts block is voice only. AWS recommends creating your own. In a chat queue flow, Play prompt sends text messages, and Get metrics can return chat-only metrics for the queue, so the flow can tell the customer how busy it is and offer alternatives.

The queued callback in Transfer to queue is not available for chat. Instead, when the wait is long, the flow can offer to take the request offline and use a Create task block, which works for chat contacts, to route a follow-up to an agent now or at a scheduled time.

3. Keep the customer connected when they look away

The widget sends browser notifications when an agent replies and the customer is not on the page with the chat. A red dot shows on the minimized widget. Both are included without extra setup, once the customer allows notifications. You can turn on Delivered and Read receipts so customers know their message arrived.

By default, a new tab starts a new chat. A few lines of code added to the widget snippet enable chat session persistence across tabs, so the customer reconnects to the chat they already started. You can also launch the widget from your own “Chat with us” button.

4. Let customers show the problem

With attachments enabled, customers and agents can share files in chat. You turn sharing on for the instance, choose the Amazon S3 location and set allowed file types and size limits. The hosted widget supports this directly. Custom chat interfaces use the attachment APIs.

5. Decide what happens when the customer goes quiet

Chat timeouts mark a customer or agent as idle and can disconnect after a set time, from 2 minutes to 8 hours. Timers reset whenever the participant sends a message or an attachment. In a flow, the Wait block can wait up to 7 days for a customer to reply, with a Customer return branch that can route them back to the same agent or queue.

With persistent chat, a customer who comes back later continues the earlier conversation, with the transcript carried forward. It is not automatic: you pass the previous contact ID when the new chat starts, or in a Create persistent contact association block. AWS recommends a small store of past contact IDs per customer, which is something you build. Customers can also download the transcript from the widget, and a post-chat survey tells you how it went.

What good looks like

The chat opens knowing who the customer is and what they are looking at. While they wait, they get updates and a choice: keep waiting or get a follow-up. They can switch tabs without losing the chat, and they see the agent’s reply when it arrives. They can send a screenshot instead of describing it. If they leave and come back tomorrow, the conversation is still there.

Where to start

  1. Pull a month of chat contact records and find where customers disconnect: in queue, after the agent joins, or after a long gap.
  2. Build a chat customer queue flow with text updates and a Create task option for long waits.
  3. Turn on message receipts and attachments in the widget, and test the browser notifications it already includes.
  4. Enable persistence across tabs, add persistent chat for signed-in customers, then compare abandonment before and after.
High-level architectureA chat that keeps the customer in the conversation
Customer
  • Website
  • Mobile app
Communications widget
  • Pre-chat form
  • Attachments
  • Browser notifications
Chat flows
  • Inbound flow
  • Customer queue flow
  • Wait block
  • Create task
Routing
  • Chat queue
  • Routing profiles
Agents
  • Agent workspace
  • Chat transcript
Your website
  • Sign-in
  • Page context
  • People
  • Amazon Connect
  • Your systems
  1. The customer opens the communications widget. Your website can pass who they are and which page they are on as contact attributes in a signed token.
  2. A pre-chat form captures the reason for the chat, so the inbound flow can route it, or answer it with a bot, before an agent is needed.
  3. While the customer waits, a customer queue flow built for chat sends text updates, using Get metrics to tell them how busy the queue is.
  4. If the wait is long, the flow offers to take the request offline and uses Create task so an agent follows up later.
  5. Customers who switch tabs get browser notifications when the agent replies, and can share files with attachments.
  6. If the customer goes quiet, a Wait block or chat timeouts decide when to close. With persistent chat, they can come back to the same conversation later.
References

Official AWS documentation

Every Amazon Connect capability in this post links to AWS’s own documentation, so you can check the details for your Region and account.

  1. Add a chat user interface to your website hosted by Amazon Connectdocs.aws.amazon.com
  2. Customize widget launch behavior and button icondocs.aws.amazon.com
  3. Pass contact attributes to an agent when a chat startsdocs.aws.amazon.com
  4. Add a pre-contact or pre-chat formdocs.aws.amazon.com
  5. Pre-chat authentication using the StartChatContact APIdocs.aws.amazon.com
  6. Default customer queue flowdocs.aws.amazon.com
  7. Flow block: Get metricsdocs.aws.amazon.com
  8. Flow block: Play promptdocs.aws.amazon.com
  9. Flow block: Transfer to queuedocs.aws.amazon.com
  10. Flow block: Create taskdocs.aws.amazon.com
  11. Enable attachments to share filesdocs.aws.amazon.com
  12. Send browser notifications to customers when chat messages arrivedocs.aws.amazon.com
  13. Enable message Delivered and Read receiptsdocs.aws.amazon.com
  14. Set up chat timeouts for chat participantsdocs.aws.amazon.com
  15. Flow block: Waitdocs.aws.amazon.com
  16. Enable persistent chatdocs.aws.amazon.com
  17. Download the transcript for your chat widgetdocs.aws.amazon.com
  18. Enable post-chat surveydocs.aws.amazon.com
Start here

Tell us what you want to improve.

We will tell you whether a voice agent fits it, what it would take, and what it should return. You will hear back within a week.

  • AWS Advanced Tier Services Partner
  • AWS Migration Services Competency
  • Amazon Connect Delivery Partner
  • AWS AI Services Competency
  • AWS Experience-Based Acceleration (EBA) partner
  • ISO/IEC 27001 certified
  • SOC 2 Type II
Certified supplierMWDBE certifiedTexas HUB certifiedNCTRCA certified
+1 (214) 550-14936275 West Plano Parkway, Suite 500, Plano, Texas 75093