최근 검색
최근 검색 없음

Rob Lajeunesse
가입한 날짜: 2022년 7월 11일
·
마지막 활동: 2023년 7월 18일
팔로잉
0
팔로워
0
총 활동 수
17
투표 수
6
플랜 수
2
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Rob Lajeunesse
Rob Lajeunesse님이 에 댓글을 입력함
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.
댓글 보기 · 2023년 7월 18일에 게시됨 · Rob Lajeunesse
0
팔로워
0
투표 수
0
댓글
Rob Lajeunesse님이 에 게시물을 만듦
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.
2023년 5월 04일에 게시됨 · Rob Lajeunesse
10
팔로워
20
투표 수
9
댓글
Rob Lajeunesse님이 에 게시물을 만듦
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.
2023년 4월 27일에 게시됨 · Rob Lajeunesse
1
팔로워
1
투표
1
댓글
Rob Lajeunesse님이 에 댓글을 입력함
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).
댓글 보기 · 2023년 4월 14일에 게시됨 · Rob Lajeunesse
0
팔로워
1
투표
0
댓글
Rob Lajeunesse님이 에 댓글을 입력함
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.
댓글 보기 · 2023년 3월 14일에 게시됨 · Rob Lajeunesse
0
팔로워
1
투표
0
댓글
Rob Lajeunesse님이 에 댓글을 입력함
There's still a gap here for GA4 support for the Messaging widget. When will GA4 work with Messaging to fire events?
댓글 보기 · 2023년 2월 02일에 게시됨 · Rob Lajeunesse
0
팔로워
0
투표 수
0
댓글
Rob Lajeunesse님이 에 댓글을 입력함
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.
댓글 보기 · 2022년 11월 28일에 편집됨 · Rob Lajeunesse
0
팔로워
0
투표 수
0
댓글
Rob Lajeunesse님이 에 댓글을 입력함
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.
댓글 보기 · 2022년 8월 02일에 게시됨 · Rob Lajeunesse
0
팔로워
3
투표 수
0
댓글