최근 검색
최근 검색 없음

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
댓글