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

Rolf Hayes
参加日2022年2月22日
·
前回のアクティビティ2025年1月28日
フォロー中
0
フォロワー
0
合計アクティビティ
126
投票
17
受信登録
39
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Rolf Hayes
Rolf Hayesさんがコメントを作成しました:
Hello Shawna James
What would make it an exciting year is to bring this back on plan for this year. As others have said, we're not looking for lots of innovation with AI and fancy developments; we just want some simple features to be added to help us provide better customer service. AI is all well and good, but good customer service is still done in person by humans and AI is still a long way from being personable.
Perhaps Zendesk could provide some good customer service to their customers like we are trying to do to ours by using your system. Seems a bit of a paradox to me.
Scott Allison look forward to your comments on this too as we were really looking forward to having it this year.
コメントを表示 · 編集日時:2025年1月28日 · Rolf Hayes
0
フォロワー
2
投票
0
コメント
Rolf Hayesさんがコメントを作成しました:
I just wanted to express my thanks to everyone here. We've set up our own webhook and trigger for internal comments on a ticket where we need a clear prompt for agents as a warning for a particular org.
コメントを表示 · 投稿日時:2025年1月03日 · Rolf Hayes
0
フォロワー
0
投票
0
コメント
Rolf Hayesさんがコメントを作成しました:
Rolf Hayesさんがコメントを作成しました:
I couldn't agree more Julian
Brett Bowser Ashwin Raju can you provide any feedback for your customers? I think we've been very patient.
コメントを表示 · 投稿日時:2024年11月26日 · Rolf Hayes
0
フォロワー
1
投票
0
コメント
Rolf Hayesさんがコメントを作成しました:
Stéphane Bahraoui I feel your pain and the apparent lack of product management and dev team addressing some very old requests by ZD customers that should be very simple, yet almost daily there are announcements of some AI-related new releases. I feel ZD should get some of the simple functionality developed that was requested years ago. Split tickets is only one of them. Consider, customised fields in the search view, URL-type custom field, Custom statuses for different support groups/agents.
In the meantime I've found the Split ‘n’ Close app has worked well for us. You may find the free plan is sufficient for your needs.
Link to the app in ZD Marketplace:
コメントを表示 · 投稿日時:2024年11月22日 · Rolf Hayes
0
フォロワー
0
投票
0
コメント
Rolf Hayesさんがコメントを作成しました:
Thanks Jorn I've managed to get this to work well now and through some test tickets and this API call you mentioned above it works well. It is always just the same user ID that we need to remove so answers the above questions I had. Thanks again for your help in solving our challenge.
コメントを表示 · 投稿日時:2024年10月16日 · Rolf Hayes
0
フォロワー
0
投票
0
コメント
Rolf Hayesさんがコメントを作成しました:
Jorn thanks for your advice and API recommendation for CC'd users. Does this work for followers too? Do I need to amend the API code for a follower as opposed to CC? I haven't tried this yet, hoping to later today.
コメントを表示 · 投稿日時:2024年10月08日 · Rolf Hayes
0
フォロワー
0
投票
0
コメント
Rolf Hayesさんがコメントを作成しました:
Peter Hochstrasser Joel Cohen 4 years for a response or development seems consistent with other ZD development suggestions from their customers and users. At least Zendesk is consistent even if consistently slow.
I'm the CS world as you suggest 4 years is an eternity. We have to measure response times in hours otherwise we loose customers.
Please Zendesk. Respond to the needs of your customers quicker. We implore you.
コメントを表示 · 投稿日時:2024年10月01日 · Rolf Hayes
0
フォロワー
0
投票
0
コメント
Rolf Hayesさんがコメントを作成しました:
ERIC C the first condition is for tickets in the Solved status
The second condition will include any ticket with a status of Solved or any custom statuses that you've created within the Solved category.
See “Ticket statuses” in your admin side of your Zendesk instance.
コメントを表示 · 投稿日時:2024年7月31日 · Rolf Hayes
0
フォロワー
1
投票
0
コメント
Rolf Hayesさんがコメントを作成しました:
Hello Loc Mai
As Dianne has confirmed there isn't a time-based condition for triggers. Triggers run at the time of ticket update, Automation can be set to run a certain amount of time after an update or event.
My suggestion is to use a combination of triggers and automation with a tag for the 60 minute aspect.
Trigger 1: - Add a tag (for example “create_60min”) to the ticket when it is created.
Automation: Remove the tag, when hours since created is more than 1.
Trigger 2: - Ticket is updated with a comment and ticket contains tag “create_60min”.
Hope this helps.
コメントを表示 · 投稿日時:2024年7月01日 · Rolf Hayes
0
フォロワー
0
投票
0
コメント