Arena for Amazon Connect

Help center › Genesys Cloud

Genesys Cloud

Arena can score contacts handled on Genesys Cloud. Genesys Cloud publishes each finished agent interaction to Amazon EventBridge in your own AWS account, and Arena's connector turns it into a handled contact: points, leaderboard, streaks, challenges and reports work as they do on Amazon Connect.

Nothing is polled and Arena stores no Genesys credential.

Tested status. The connector follows Genesys Cloud's published event format and is covered by automated tests, and its function has been run in AWS with events in that format. It has not yet run against a live Genesys Cloud organisation. If you are the first, tell us and we will work through it with you.

What is scored

From Genesys Cloud In Arena
An agent's part of an interaction ends (the user.end detail event) One handled contact for that agent
Talk time plus hold time Handle time, which sets the points for the contact
The queue The queue shown on the contact
The interaction and the agent's session The contact's id, so a repeated delivery is counted once

Setting it up

  1. In Genesys Cloud, add the Amazon EventBridge Source integration. Give it your AWS account id and region, and select the topic v2.detail.events.conversation.{id}.user.end. Activate it.

  2. In the AWS console, open Amazon EventBridge, then Partner event sources. Find the source Genesys created (its name starts with aws.partner/genesys.com/cloud/) and choose Associate with event bus. This creates an event bus with the same name.

  3. Update your Arena stack: set GenesysEventBusName to that event bus's name, and set Provider to generic so the console's wording matches. The stack adds one function and a rule on the bus.

  4. Give Arena the names. Genesys sends ids, not names. Until an id is mapped, the agent appears under the id, in a team named after the division. The mapping is filled by a small script, genesys-names.js, published beside the template of each release: take your template's address and replace template.yaml with genesys-names.js. It needs Node.js 18 or later and the AWS CLI signed in to the stack's account. Use it in one of two ways:

    From a spreadsheet, with columns kind,id,name,team:

    kind,id,name,team
    user,3f9a1c2e-0000-0000-0000-000000000001,Ann Lee,Billing team
    queue,7b21d4aa-0000-0000-0000-000000000002,Billing,
    
    node genesys-names.js <your stack name> --csv names.csv
    

    Or from Genesys Cloud directly, with an OAuth client you create there (Client Credentials grant, able to view users, queues and divisions). Its id and secret are read from your shell on your own machine and are never sent to Arena:

    node genesys-names.js <your stack name> --genesys mypurecloud.com
    

    Add --dry-run to see what would be saved. Run it again when people or queues change.

  5. Put the agent panel where agents work. Register <SiteUrl>/agent-panel.html as a web page in the Genesys Cloud agent desktop if your organisation allows embedded pages, or have agents keep it open in a browser tab.

  6. Create sign-ins for agents in the stack's user pool, with each agent's Genesys user id as their agent id, so the panel shows their own points. See users and sign-in.

Teams

Arena groups agents into teams. On Amazon Connect a team is a routing profile. On Genesys Cloud it is whatever you put in the mapping's team column. With --genesys, that is the agent's Genesys work team when they have one, else their division.

People who already exist in Arena

If you are moving from Amazon Connect to Genesys Cloud, link each person's Genesys user id to their existing record under People in the console. Their Genesys contacts then score on the same person, and their history, streak and level carry over. See connecting other platforms.

If nothing is scoring

Billing

An agent with a scored Genesys contact on a day is an active agent that day, exactly as on Amazon Connect.

Current as of version 0.35.0. See the release notes for what changed since.