The free Connect scorecard
The scorecard is a read-only report on your Amazon Connect instance's last 90 days. It is separate from Arena: a much smaller CloudFormation stack, no subscription, and nothing sent outside your AWS account. Launch it from arenaforconnect.com/scorecard.html, where there is also a sample report.
Running it
- On the scorecard page, paste your instance ARN (Amazon Connect console, your instance, Overview) and choose Launch in CloudFormation. The console opens in your instance's region with the template and ARN filled in.
- Set the settings below, tick the IAM acknowledgement and create the stack. Two to five minutes for most centres.
- Open the stack's Outputs tab and follow ReportUrl.
- Delete the stack when you are done.
| Setting |
Default |
What it does |
| ConnectInstanceArn |
none |
The instance to report on. Same account and region as the stack. |
| Timezone |
UTC |
Your centre's IANA time zone, such as America/New_York, so each day is your working day. |
| ShowNames |
full |
How agents appear: full names, initials, or hidden (numbered). |
| Days |
90 |
How far back to read, 7 to 90. |
| RunId |
1 |
Change it and update the stack to build a fresh report with a new link. |
What the report shows
- Totals: agents with activity, contacts handled, average handle time, evaluations performed, average evaluation score.
- Contacts by week.
- A leaderboard for the last 30 days, ranked by Arena points at the default scoring mix: 6 to 12 points per contact depending on handle time, and up to 30 per evaluation with nothing below 70%. It says how many of the ten busiest agents are not in the top ten by points.
- Teams: each routing profile's agents, contacts, handle time and evaluation average.
- Flags: the busiest quarter of agents with an evaluation average under 70%; agents active on five or more days who have handled nothing in the last 14; agents with 20 or more recent contacts and no evaluation.
- What Arena would cost, from your own active agents per day in the last 30 days, with the first 10 a day taken off.
Without Contact Lens evaluations the report covers contacts and handle time and says that quality is missing.
The founding-customer link
The report ends with one link to the founding-customer form. The link carries five totals after the # in its address: agents with activity, active agents a day, contacts handled, evaluations performed and the monthly estimate. Browsers do not send that part of an address to any server, so opening the link sends us nothing. The form shows the five numbers with a ticked box; they reach us only if you leave it ticked and press Send. Agent names, teams and everything else in the report are never part of the link. An empty report has no link.
What it reads, and what it cannot do
The function's role allows five Amazon Connect actions, all read-only, on the one instance you name: DescribeInstance, ListUsers, DescribeUser, DescribeRoutingProfile and GetMetricDataV2. From those it takes each user's name, username and routing profile, and four numbers per agent per day: contacts handled, total handle time, evaluations performed and their average score.
It reads no contacts, recordings, transcripts, customer data or contact attributes. It cannot change anything in your instance.
Where the report lives
- The page is one self-contained HTML file with no scripts and no external requests, stored in a private, encrypted bucket the stack creates. It expires after 30 days.
- It is served by a Lambda function URL. The link in ReportUrl carries a random 160-bit token; without the token the function answers "not found". Anyone holding the link can read the page, so share it as you would the numbers, and choose
initials or hidden names if it will travel.
- Nothing is sent to EKPK or anyone else: no telemetry, no callback. We see your numbers only if you show them to us.
- If your organisation blocks public Lambda function URLs, the stack will fail to create. Nothing is left behind; tell us and we will send the report another way.
The code
The template contains a small loader you can read in a minute. It downloads the report code from the public release location, refuses it unless its SHA-256 matches the one in the template, and runs it. Both checksums are printed with each release on the release notes.
Cost
One function run of a few seconds to a few minutes and a few kilobytes of storage: a fraction of a cent. Deleting the stack removes the function, the role, the bucket and the page.
If something goes wrong
- The stack fails with a message about the instance: the ARN must be the full instance ARN, and the stack must be in the same account and region as the instance.
- "No agent activity found": the instance has no handled contacts in the period, or it is not the instance your agents work on.
- "This report is no longer here": reports expire after 30 days. Change RunId and update the stack.
Current as of version 0.36.0. See the release notes for what changed since.