cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Frequent Visitor

Transfer to Agent error/not handing off in Omni-Channel

Hi there, I am trying to configure PVA with Omni-Channel. I have successfully connected it to my Omni-Channel instance in PVA. I am trying to handoff to agent and getting the following error in the PVA chat: "Sorry, we aren't able to serve you at the moment." The logged in Agent in Omni receives no notification of a hand-off attempt.

 

I see my bot in the default queue. I have setup a routing rule with the VaScape varible. What am i missing? Please see attached screenshots.

 

Any help is appreciated. Thank you.

 

Chad.

14 REPLIES 14

@D365_CWeiner - Thank you for using Power Virtual Agents. I reviewed the screenshots you supplied (very helpful!). Since you have added your bot and live agent in the same queue, per the documentation (link below) you do not need a routing rule.

 

Would you please remove the unnecessary routing rule and try again?

 

>> Link to product documentation - https://docs.microsoft.com/en-us/dynamics365/omnichannel/administrator/configure-bot-virtual-agent

 

Thank you,

Pawan

Thanks @pawan-msft . I have removed the routing rule and the conversation still is not transferred to an agent. No notification occurs and you almost immediately get the "Sorry, we aren't able to serve you at the moment.".

 

Your help is appreciated.

 

Chad 

I have the exact same issue

In general my hand off to the agent is working fine but I have had transient incidents when the transfer doesn't happen and you get the "sorry we are not able to serve you at the moment" message. My GUESS is that it is a problem within the MS Platform rather than your specific setup.

Got the same issue. 😞

Thank you for your patience as we investigate this further. We tested this again and can't reproduce the issue on our end. We believe the issue is something specific with how your instance on Omnichannel is configured. We have engaged our counterparts in that team to help further. Please stay tuned!

 

Thank you,

Pawan

Thanks @pawan-msft . I am happy to jump on a quick Teams call to review my environment to help expedite the resolution. Would love to get this working and a few of us seem to be having the same issues. Would that be possible? Do you need the URL for my instance to review on the back end?
Microsoft
Microsoft

Hi all,

 

This is currently a known issue in Omnichannel and the fix is being validated. For the meantime, the workaround to this issue is to minimize the context variables (in addition to the OOB variables [va_]). See attached screenshotCapture.PNG

@madriano i am not sure i'm following what you mean by minimize. When i initiate a transfer to agent in PVA, i only see the OOB variables.

BotContextVariables.jpg

 

I am using the default queue and have the following context variables? Do these need to be changed?

BotContextVariablesWorkstream.jpg

Helpful resources

Announcements
Microsoft Ignite

Microsoft Ignite

Join digitally, March 2–4, 2021 to explore new tech that's ready to implement. Experience the keynote in mixed reality through AltspaceVR!

New Super Users

Meet the Power Virtual Agents Community Super Users!

Congratulations to our Season 1 2021 Super User Crew!

PVA Commnity Blog

NEW Power Virtual Agents Community Blog

View articles posted by fellow community members on the Power Virtual Agents Community Blog!

New Badges

New Solution Badges!

Check out our new profile badges recognizing authored solutions!

Users online (28,110)