最近搜索
没有最近搜索

Daniel Pohl
已加入2021年4月15日
·
最后活动2024年2月15日
关注
0
关注者
0
活动总数
5
投票
0
订阅
2
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Daniel Pohl
Daniel Pohl 进行了评论,
Our server desk has the same complaint. To us it doesn't make sense, that in an existing Side Conversation, the Send button line is sticky, but when you write a new Side Conversation it vanishes down.
Please make the Send button line also sticky for a new Conversation!
Here the locked bar with existing Side Conv.:
Here the vanishing Send button bar with new Side Conv.:
Looking forward to a solution!
Best regards
Daniel
查看评论 · 已于 2024年2月15日 发布 · Daniel Pohl
0
关注者
0
投票
0
评论
Daniel Pohl 进行了评论,
Hi Lila,
as I wrote, 28 days is set and it is the maximum configurable, unfortunately. But the 28 days are not the actual problem. I mean, the tickets should be closed one day anyway, otherwise we would end up in having thousands of not-closed tickets. Our main interest is to be able to reactivate a closed ticket.
查看评论 · 已于 2018年12月04日 发布 · Daniel Pohl
0
关注者
0
投票
0
评论
Daniel Pohl 进行了评论,
+1 to reopen a closed ticket!
We handle travel agency requests of flight bookings and we like to have all requests about the same booking inside one Zendesk ticket.
With your restriction that a closed ticket cannot be reopened, you force us to create a new ticket on the same flight booking every time there is another schedule change or name change or refund request. And as flight bookings are made long time in advance, 28 days is nothing. In our previous case management system, we had cases being closed and reactivated again over a whole year.
In Zendesk, our Service Desk needs to click through several Zendesk tickets to understand what was when. This is annoying and was definitely much better in our last case management tool.
So, please, please, allow us to reopen a closed ticket!!
查看评论 · 已于 2018年12月04日 发布 · Daniel Pohl
0
关注者
0
投票
0
评论