Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Rob Lajeunesse
Beigetreten 11. Juli 2022
·
Letzte Aktivität 18. Juli 2023
Folge ich
0
Follower
0
Gesamtaktivitäten
17
Stimmen
6
Abonnements
2
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Rob Lajeunesse
Rob Lajeunesse hat einen Kommentar hinterlassen
Simple answer, it's because it's custom code enabled by Sunshine Conversations. To fully use that, you likely need a developer and additional SKU when you exceed a relatively small amount of MAU.
Agree this should be standard.
Kommentar anzeigen · Gepostet 18. Juli 2023 · Rob Lajeunesse
0
Follower
0
Stimmen
0
Kommentare
Rob Lajeunesse hat einen Post erstellt
For our chat experiences, we need to be able to set better expectations in Messaging around agent availability and potential waiting times/spot in the chat queue. This would help customers understand if they want to wait and chat live, or take it async.
We use a ton of offshore resources so we don't have consistent ticket ownership, so this is a critical feature for us.
Gepostet 04. Mai 2023 · Rob Lajeunesse
10
Follower
20
Stimmen
9
Kommentare
Rob Lajeunesse hat einen Post erstellt
We have a use case to be able to identify words during a Messaging conversation and provide real time guidance to our agents in escalations scenarios. Example would be a customer threatening BBB, or some sort of legal action, that would tag and provide real time guidance to the agent on how to handle.
Gepostet 27. Apr. 2023 · Rob Lajeunesse
1
Follower
1
Stimme
1
Kommentar
Rob Lajeunesse hat einen Kommentar hinterlassen
Agree with all the sentiment here, this is crazy it hasn't been prioritized. This and time based triggers to prompt a message to restart the bot should be table stakes especially if this is a core part of the Product.
Zendesk proving they are not enterprise-grade by not only continuing to deprioritize this, but also other critical functionality gaps (e.g. can't report on missed chat data with Omnichannel routing, basic metrics missing in Explore).
Kommentar anzeigen · Gepostet 14. Apr. 2023 · Rob Lajeunesse
0
Follower
1
Stimme
0
Kommentare
Rob Lajeunesse hat einen Kommentar hinterlassen
Also having similar issues as the posting above with agents getting assigned a bunch of tickets through the EAP. It almost seems like tickets are being assigned without the agents clicking the accept button but want to confirm behavior as designed.
Kommentar anzeigen · Gepostet 14. März 2023 · Rob Lajeunesse
0
Follower
1
Stimme
0
Kommentare
Rob Lajeunesse hat einen Kommentar hinterlassen
There's still a gap here for GA4 support for the Messaging widget. When will GA4 work with Messaging to fire events?
Kommentar anzeigen · Gepostet 02. Feb. 2023 · Rob Lajeunesse
0
Follower
0
Stimmen
0
Kommentare
Rob Lajeunesse hat einen Kommentar hinterlassen
Barry Neary few feature requests as we're standing this up:
- The ability to group and organize statuses for agents is critical for agent experience. It would be great to group productive and break statuses together so agents can quickly find custom statuses. This is critical for our BPO Vendor Management.
- Having some ability to do fallback routing for Voice would be great to have sooner, rather than later, or some ability to prioritize based on a group what tickets agents get first.
- With custom statuses, being able to remove default statuses as long as we have equivalents setup to keep agent experience more cleanly.
Kommentar anzeigen · Bearbeitet 28. Nov. 2022 · Rob Lajeunesse
0
Follower
0
Stimmen
0
Kommentare
Rob Lajeunesse hat einen Kommentar hinterlassen
Agree on this feature, this is table stakes.
Not sure Dane what you mean above by a "much simple" visualization/chart type, that's not really a workaround, it's forcing users to leverage a different visual (which you all call out in the article that the charts are best for specific data comparisons) to see the legend. Not a great experience.
Kommentar anzeigen · Gepostet 02. Aug. 2022 · Rob Lajeunesse
0
Follower
3
Stimmen
0
Kommentare
Rob Lajeunesse hat einen Kommentar hinterlassen
Adding my vote, we need this feature and it should be foundational.
Kommentar anzeigen · Gepostet 11. Juli 2022 · Rob Lajeunesse
0
Follower
3
Stimmen
0
Kommentare