最近の検索
最近の検索はありません

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
コメント