-
Notifications
You must be signed in to change notification settings - Fork 304
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting the name of the agent that initiated a quick connect #258
Comments
I was wondering if there was any progress on this @ctwomblyamzn ? This is especially frustrating when it comes to multi party conferences with multiple internal transfers, as there is no way for me to currently identify who is who. The only thing I can think of is to add connection info to my external transfer directory, HOWEVER, the connection IDs are not unique for the contact interaction. The UUIDs for all connections are unique to the connected agent, NOT the contact interaction as a whole. So this will sadly not work :( |
this is pretty annoying, as far as i can tell there's still no way to really tell who is who on a multiparty call. sometimes the quick connect name is populated, but often it's just 'INTERNAL-TRANSFER'. |
@ctwomblyamzn Has this progressed at all? |
This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment to keep this active. |
Love the github actions, its been like this for 90 day's waiting for a response. Can we get a response on this @ctwomblyamzn ? |
This issue is stale because it has been open for 90 days with no activity. Remove stale label or comment to keep this active. |
Relevant for us too, as we generate quick connects with UUIDs and are unable to differentiate queues or agents, with names. Bump! |
Hi guys,
I'm trying to add a short message that displays 'Transfer from ' but I can't seem to find the agent name. When I inspect the connections during
onConnecting
, although I see anname
property it's always null. Is there a way to accomplish this?Thanks
The text was updated successfully, but these errors were encountered: