The blocker
A customer calls about a refund that never arrived. The agent is helpful, checks what they can, and promises that someone in finance will look into it. The call ends politely. A week later the customer calls again, gets a different agent, and starts from the beginning. Nobody can see what was promised, who owns it, or whether anyone did anything.
On the dashboard, both calls look fine. They were answered quickly and handled in a reasonable time. But the issue was never resolved, and every repeat call costs you twice: once in agent time, and again in the customer’s patience.
Why it happens
- The contact is tracked, the issue is not. Contact center systems measure calls and chats. The problem the customer called about has no record of its own.
- Follow-up work lives in email and spreadsheets. A promise made on a call goes into an inbox, where it has no owner, no priority and no deadline.
- No link between contacts. When the customer calls back, the new contact is not connected to the earlier ones.
- Nobody measures resolution. Service level and handle time are reported. Reopened issues and first contact resolution are not.
How Amazon Connect solves it
Amazon Connect has two features built for this: Cases to record and track the issue, and Tasks to route the work needed to resolve it.
1. Record the issue as a case
Amazon Connect Cases lets you track, collaborate on and resolve customer issues. AWS describes a case as a record of the customer’s issue, the steps and interactions taken to resolve it, and the outcome. You can enable Cases without integration work.
Every case is built from a case template, a form that makes sure agents collect the right information for each type of issue, with required fields where you need them. Each case is connected to a customer profile.
2. Link every contact to the case
The Cases flow block can get, create and update cases inside a flow, and search for a case linked to a contact. When you link a contact to a case, it is recorded in the case’s activity feed. When the agent accepts a contact linked to a case, the case opens automatically as a tab in the agent workspace.
That changes the callback. Instead of starting again, the next agent opens the call with the case, its history and its status already on screen. Cases is available in the agent workspace out of the box, or through the Cases APIs in a custom agent application.
3. Turn promises into tasks
With Tasks, a unit of follow-up work becomes a contact. It is routed, prioritized, assigned and tracked like a call or a chat. Tasks can be created in several ways:
- Agents create them from the Contact Control Panel, for example to call a customer back with an update.
- A Create task block in a flow can start a task now or schedule it for a future date and time.
- Pre-built application integrations can create tasks from events in supported CRMs without code, and your own applications can use the StartTaskContact API.
- Agents can create a task directly from a case.
Task templates give agents the fields they need for each type of task, so the back-office team gets the same information every time.
4. Set deadlines and act when they slip
SLAs in Cases set a target, such as the case status reaching Resolved, and a deadline. Each SLA shows whether it is active, due soon, overdue, met or not met. You can create rules that run when a case is created, updated or breaches an SLA. Rules can assign SLAs, create tasks, end tasks, update cases or email a manager. For example, a rule can alert a supervisor when a high-priority case is created.
5. Measure resolution, not just handling
Once Cases is enabled and you have at least one case template, case metrics appear in historical metrics reports and the GetMetricDataV2 API. They include average case resolution time, average contacts per case (Average Case Related Contacts), cases created, resolve and reopen case actions, and the case first contact resolution rate. The Cases performance dashboard shows volume, resolution trends and SLA achievement, with drill-down by template, status, queue or agent.
Average contacts per case is the number to watch. If it is rising for one case template, that is where customers are calling back.
What good looks like
Every issue that cannot be fixed on the first contact has a case, an owner and a deadline. Follow-up work arrives in a queue as a task, not in someone’s inbox. When the customer calls back, the agent sees the case before saying hello. Supervisors see overdue cases before customers chase them, and leaders report on resolution as well as speed.
Where to start
- Pick the three contact reasons that cause the most callbacks.
- Enable Cases and build one case template for each, with only the fields agents really need.
- Add a Cases block to the inbound flow to find and link open cases for the caller.
- Add an SLA and a breach rule for each template, then track average contacts per case each week.









