Do you have any control for the Agent Statuses without Control Contact Panel Api?

0

https://github.com/amazon-connect/amazon-connect-streams this is my temporarily solution
problem is, it's a hassle in the UI side.

so is there a way for me, to change all the agent statuses without accessing the CCP panel?

asked 3 years ago290 views
5 Answers
1
Accepted Answer

This is now possible via the PutUserStatus API call. Added within the last month.

https://docs.aws.amazon.com/connect/latest/APIReference/API_PutUserStatus.html

ledge
answered 2 years ago
1

It is not clear what you are trying to achieve can you explain further?

m66rus
answered 3 years ago
1

There is no API from the server-side to do this, so you would need to have a listener on the client to capture the events.

You could debug https://instanceid.awsapps.com/connect/real-time-metrics?tableType=skill to see how the supervisor changes the agent's state from this portal which impacts the specific agent.

m66rus
answered 3 years ago
0

What I'm trying to do, is to change the Agent State in the AWS Lambda
so I wouldn't need to Access the CCP then Change state there

because at the moment,
it can only change 1 agent status/state of the current online agent,
using the CCP which is activated in the Frontend Website,

so in order for me to change the states of many agents,
I need to create a websocket on the website, then emit the changes on each statuses
hoping that the agent that I want to change the status is Online and is using the website.

which is I'm trying to prevent.

What I want to do, is to change the agent status/state in the AWS Lambda,

what is happening in the SDK is that, I could only get the List of the Current Agents and all their info,

but I couldn't Manipulate let's say, Change the Agent's routes or status/states.

So what I'm asking is,
is there a way to change the status of the agent using
the SDK provided by AWS which out activated the Contact Control Panel, which is a IFrame for the Website

answered 3 years ago
0

that's just, sad, oh well, i'll just stick to the old code then.

they should have done that, so it's easier to manage agent status in backend to avoid overloading the website.
oh well can't complain.

thank you for the help

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions