connect to agent workspace queue via virtual agent
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2020 01:13 PM
Hi Experts,
Need your guidance on one thing .
How to route Virtual agent conversation on portal to Agent Workspace queue rather than Connect queue..
I tried to look into the example of Transfer to HR agent but currently it has script for moving to HR queue of connect .
Could anyone let me know if they have achieved it this , and a step by step process will be helpful.
NOTE : I have looked into docs but it is too much data and not able to identify which one matches my need so best would be if you can do step by step and show me by attaching snapshots
- Labels:
-
Virtual Agent

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2020 01:19 PM
Hi ,
Here are links which will help you.
https://community.servicenow.com/community?id=community_blog&sys_id=ea1c93bddba21780d58ea345ca961957
https://www.workplace.com/blog/servicenow-workplace-integration/
If it helps,Please mark ✅ Correct and 👍 Helpful.
Warm Regards,
Milind

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-14-2020 02:11 PM
Completely understood that documentation isn't great for this - especially considering how easy Connect Support is to setup and Agent Chat... not so much.
You'll need to use Advanced Work Assignment to route chats to Agent Workspace so you should be at least remotely familiar with that. You'll also need to ensure your Chat Setup is configured to use Agent Workspace instead of Connect Support as a basic setup step.
Here's my solution (copied from another recent thread😞
I ran into this as well and it's very frustrating how poorly Agent Chat + Advanced Work Assignment is documented because it's considerably more complex than Connect Support, even if you want to use it in the exact same manner.
Sometimes for routing chats from VA, you don't need fancy routing - i.e. if somebody is in Topic A, the chat will always go to Queue A - and I think I got this working...
Some examples show a scripted advanced condition to route chats, but that seems utterly ridiculous to stoop to that complexity for something as simple as this. Let me know if this works because I've only tried it on a small scale with two chat queues.
In Advanced Work Assignment, create a chat Queue (and assignment eligibility ofc) and in 'Work item routing condition' (Simple Condition), select "Show Related Fields", then click again and select "Context => Interaction Context fields", then click it again and you will see all the Live Agent Variables from VA Designer which you should be able to use. At this point I just select "queue IS [unique friendly name]" - there's no point using the sys_id now since you have to define this variable yourself...
Speaking of which, now, go back into the desired topic of VA Designer, add the Live Agent Variable "queue" to the Topic, edit the topic flow, show Live Agent Variables, then set the value of "queue" to be [unique friendly name].
As far as I've come across, this is the simplest way to route chat from Virtual Agent so let me know if you run into specific stumbling blocks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2020 03:09 PM
Hi Chris,
We're going through the process of transitioning from Connect Support to Live Agent chat, and I agree, the documentation around all this is woeful. I finally found this post of yours, and setting the condition on the AWA queues to make the sys_id match the sys_id of the VA queue variable worked.
We have a VA topic where the user picks the department they want to chat with, and then we set the VA queue to be the sys_id of the queue for that department, and then use the 'vaSystem.connectToAgent()' function after checking if there is an available agent. This all worked fine with Connect Support. However, when I set up the AWA queues the transfers did not work properly at all until I added the work item routing conditions you describe above, so thank you! It seems that 'vaSystem.connectToAgent()' does not work with AWA queues even if you set the sys_id of the VA queue context variable in an earlier script node, as the documentation describes, unless you have the sys_id in the work item routing condition.
I have an open HI case on this, so I will post here if they get back with any sort of explanation on this...
Cheers,
Steve
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-20-2021 06:19 AM