Genesys Cloud - Main

Is there a way to automate agents to be On Queue when they log in? I know we can auto answer, but haven't been able to see anything on this, so I'm assuming its a no.

#Implementation

------------------------------
Danielle Apple
Empeople Credit Union
------------------------------

Hi Danielle, we don't have a solution for it yet.

Genesys has an idea for it, but this is an idea only: https://genesyscloud.ideas.aha.io/ideas/DIG-I-326

------------------------------
Breno Canyggia Ferreira Marreco
https://www.linkedin.com/in/brenocfm-40b62182/
------------------------------

Hey Danielle, 

You could subscribe to the v2.users.{id}.activity topic, then make decisions based on the schema. Eg, first loging for the day logic would then use the /api/v2/users/{userId}/presences/purecloud to update their on queue status. 

Not a simple thing, but it's doable for sure

------------------------------
Lawrence Drayton
Prvidr Pty Ltd
------------------------------

Hi Danielle,
have not done this by myself, but you should be able to use the trigger for Agent presence (Admin --> Triggers --> v2.users.{id}.activity) This would start a workflow in which you could call a data action. This could use PUT /api/v2/users/{userId}/routingstatus to set the userstatus. Please note, that you can pass the {id} from the trigger to the workflow by declaring it as an input variable in the workflow.
Best regards
Christoph

------------------------------
Christoph Domaschke
CRONBANK AG
------------------------------

I recently did something to help with a project, but before implementing it, you need to keep in mind:
- Number of concurrent requests to avoid reaching the limits;
- I forced a 10s wait, which can be changed and/or triggered through a data table;
- Always check the Available status, which is the status after login;
- If you have a substatus in Available, it will not be checked;

You will need:
- trigger;
- Work Flow;
- Data Action;

Here are the examples:

Hope this helps!

------------------------------
Danniel Cioti
PS
------------------------------

Original Message:
Sent: 07-01-2024 02:28
From: Christoph Domaschke
Subject: Automatic Queue login

Hi Danielle,
have not done this by myself, but you should be able to use the trigger for Agent presence (Admin --> Triggers --> v2.users.{id}.activity) This would start a workflow in which you could call a data action. This could use PUT /api/v2/users/{userId}/routingstatus to set the userstatus. Please note, that you can pass the {id} from the trigger to the workflow by declaring it as an input variable in the workflow.
Best regards
Christoph

------------------------------
Christoph Domaschke
CRONBANK AG
------------------------------

Thanks for the info Danniel. Any negative feedback from this customization? We might want to use something similar so I am a bit curious.

------------------------------
Andrew Lagarde
Engineer
------------------------------

Original Message:
Sent: 03-14-2025 11:17
From: Danniel Cioti
Subject: Automatic Queue login

I recently did something to help with a project, but before implementing it, you need to keep in mind:
- Number of concurrent requests to avoid reaching the limits;
- I forced a 10s wait, which can be changed and/or triggered through a data table;
- Always check the Available status, which is the status after login;
- If you have a substatus in Available, it will not be checked;

You will need:
- trigger;
- Work Flow;
- Data Action;

Here are the examples:

Hope this helps!

------------------------------
Danniel Cioti
PS
------------------------------


Original Message:
Sent: 07-01-2024 02:28
From: Christoph Domaschke
Subject: Automatic Queue login

Hi Danielle,
have not done this by myself, but you should be able to use the trigger for Agent presence (Admin --> Triggers --> v2.users.{id}.activity) This would start a workflow in which you could call a data action. This could use PUT /api/v2/users/{userId}/routingstatus to set the userstatus. Please note, that you can pass the {id} from the trigger to the workflow by declaring it as an input variable in the workflow.
Best regards
Christoph

------------------------------
Christoph Domaschke
CRONBANK AG