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

Rob Becker
参加日2023年3月20日
·
前回のアクティビティ2024年10月07日
フォロー中
0
フォロワー
0
合計アクティビティ
8
投票
0
受信登録
4
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Rob Becker
Rob Beckerさんがコメントを作成しました:
October 7, 2024, and this still isn't being taken seriously. This is so basic; it's shocking that this hasn't been addressed by now. This is now a seven year old issue. That's embarrassing.
コメントを表示 · 投稿日時:2024年10月07日 · Rob Becker
0
フォロワー
0
投票
0
コメント
Rob Beckerさんがコメントを作成しました:
Walter Bellante Is there any sort of update on this? Still on track for Q3 or Q4?
コメントを表示 · 投稿日時:2024年7月08日 · Rob Becker
0
フォロワー
1
投票
0
コメント
Rob Beckerさんがコメントを作成しました:
I found this discussion because I'm struggling with the same. There has got to be a better way to handle this. If Messaging is preferred over classic chat, there needs to be some consideration for those who want to treat Messaging sessions as seperate for a a multitude of reasons. This flow doesn't make sense:
1) Customer has a Messaging session with an agent, and a resolution is reached during that session. Ticket moved to Solved.
2) Customer receives the CSAT prompt in the widget and responds, they are then given the stock "Thanks for your feedback. If you need more help, you can ask another question at any time." message.
From here, it's as if the customer is dropped off in the middle of nowhere. Questions aren't answered by the bot - although it would be easy for a customer to think the bot might respond. Instead, the original ticket is reopened. What if the original ticket is for a completely different issue?
I've attempted to set up a macro/trigger/automation to force the ticket into an actual Closed status, but can't seem to get that to happen. I can change the ticket category to Closed, but the ticket status remains Solved.
Am I missing something here as far as how this should work? There should be some way to kick the customer back to the beginning of the Messaging flow once a ticket is solved.
Also, to offer that customers should pay for Sunshine Conversations to achieve the multi-party conversation feature is not a solution. I've been given various expected targets for this to become a stock Zendesk feature on our plan over the last year plus, and I believe we're now looking at 2H 2024. The more I dig into this, the less thrilled I am with it.
コメントを表示 · 編集日時:2024年4月11日 · Rob Becker
0
フォロワー
3
投票
0
コメント