Hey Nick,
While I would avoid doing this myself - it's pretty simple to do. I am not sure about he email wizard part, but assuming you can still have emails coming in and they touch an inbound flow this is possible/easy. Though it's a little finicky.
Assuming that the unique "interaction id" is added as a participant attribute
- Set up data table in Genesys that matches name, userid and their unique "interaction id"
- Set up an in-queue email flow or make amends to your current one that does the following
- Get the attribute from the interaction
- Use that to run a data table search and will spit out the user ID
- Create a data action that uses the "/api/v2/conversations/{conversationId}/assign" API
- Use that data action to send to the found agentId/userId
This has some pitfalls - be aware that it will be stuck with them until the accept or decline, and might even go into a loop of always being assigned back to that person (Could make some changes to the flow to assist in this not happening) But really, if they are sick/away/retire etc and they have the emails, it's a pain to have to log in as them, and accept/transfer away.
------------------------------
Lawrence Drayton
Prvidr Pty Ltd
------------------------------