The blocker
The support inbox shows hundreds of unread messages. A handful of people work it, each scrolling for something they can answer. Some emails get two replies from two agents. Others sit for a week because the subject line looked hard. A customer who wrote on Monday writes again on Wednesday, then calls on Thursday, angry. Nobody can say how long the average email waited, because the inbox doesn’t know.
A shared mailbox is not a queue. It has no order, no priority, no owner for each message and no service level. As volume grows, it falls behind, and the backlog turns into calls.
Why it happens
- Agents pick their own work. Easy emails get answered first, hard ones age.
- There is no triage. Spam, out-of-office replies, complaints and simple questions all land in the same list.
- Customers get no acknowledgement. Without a reply, they write again or call, which adds to the pile.
- Email lives outside the contact center. It isn’t routed, staffed or reported like calls and chats.
- Every reply is written from scratch. The same answer is typed again and again.
How Amazon Connect solves it
Amazon Connect email uses Amazon SES to receive and send messages, and every inbound or outbound email is its own contact, linked into a thread. That one change makes email routable. We covered turning email on next to other channels in Voice, chat, SMS and email live in separate tools. Here we focus on clearing the backlog.
1. Give each mailbox an address and a flow
You can create up to 100 email addresses on your Amazon Connect domain or up to five custom domains verified in Amazon SES. Each address can have its own flow, so billing@ and support@ start different logic. An address with no flow is outbound only, a no-reply address. If you want to keep your current public address, you can forward it to the address on your instance’s email domain. Web forms can create email contacts directly with the StartEmailContact API.
2. Triage before an agent sees it
The flow runs as soon as the email arrives. A Check contact attributes block can read the email segment attributes: the email subject, for keywords such as “refund” or “cancel”, and the Amazon SES spam and virus verdicts. AWS suggests disconnecting emails that fail those checks, or sending them to a special queue for managers to review.
From there, the flow sets the queue. Because Set routing criteria works for email, you can also route by agent skill, such as language or product, as described in Calls land with the wrong team. A Lambda function you build can add a customer’s account tier from your own systems.
3. Acknowledge every email automatically
The Send message block can send an automatic acknowledgement, such as “Thank you for your message. We will get back to you in 24 hours.” It can also send a templated reply that resolves the email outright, such as password reset steps. AWS’s email setup guide shows how to address the reply dynamically to the customer and reuse their subject line.
AWS warns about email loops. Amazon Connect blocks self-addressed emails automatically, but bounces and out-of-office replies can still loop. Add filtering to your inbound email flows, and avoid Send message with email in outbound flows unless you have safeguards.
4. Route email to agents like any other contact
Email contacts are offered to agents through queues and routing profiles. In the routing profile, maximum contacts per agent sets how many emails an agent can hold at once. Each queue has a default From address, up to 49 more, and its own outbound email flow, so different teams or brands can reply from the right address.
When an email is offered to an agent, they have a set time to accept it. If they don’t, it returns to the queue and might be offered to someone else. Nobody cherry-picks, and two agents don’t end up answering the same email.
5. Help agents reply faster
- Message templates give agents a signature, a disclaimer or a full response.
- Quick responses are searchable snippets for chat and email, assigned by routing profile.
- With Amazon Connect AI agents, an agent who accepts an email gets a conversation overview, knowledge recommendations and a drafted reply they can edit before sending.
- Agents can pause an email while they wait for an approval. Paused time is tracked separately, and flows can resume or transfer emails paused too long.
- Drafts save automatically every few seconds, with no configuration.
What good looks like
Every email gets an automatic acknowledgement. Spam is filtered out before it reaches an agent. Refund requests go to the refunds team, in the customer’s language, oldest first. Agents work one email at a time, with the thread and a drafted reply on screen. Supervisors see email queues next to calls and chats, so the backlog is a number on a dashboard, not a guess.
Where to start
- Sample a week of the shared inbox and sort it into the five or six reasons customers write.
- Create an Amazon Connect address and an inbound email flow for one mailbox, with spam checks and an acknowledgement.
- Route each reason to a queue, and add templates for the three most common answers.
- Forward the mailbox to Amazon Connect, then track time in queue and contacts handled each week.









