최근 검색
최근 검색 없음

Peter Hochstrasser
가입한 날짜: 2021년 4월 15일
·
마지막 활동: 2024년 10월 01일
팔로잉
0
팔로워
2
총 활동 수
307
투표 수
69
플랜 수
85
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Peter Hochstrasser
Peter Hochstrasser님이 에 댓글을 입력함
Zendesk: 4 years.
That's how long it took your product management to finally see the merit in this request.
In our (your) industry, that is eternity.
You get good ideas and requests from your customers daily.
Pls. find a way to vet them all quickly.
댓글 보기 · 2024년 10월 01일에 게시됨 · Peter Hochstrasser
0
팔로워
0
투표 수
0
댓글
Peter Hochstrasser님이 에 댓글을 입력함
Read the paragraph „You won’t see …“ carefully, you have to request the ecport to be made available - open chat, request it - it took minutes in my case.
BR, Peter
댓글 보기 · 2024년 9월 15일에 게시됨 · Peter Hochstrasser
0
팔로워
0
투표 수
0
댓글
Peter Hochstrasser님이 에 댓글을 입력함
According to this article, Tools, Reports should be available in Suite Professional.
However, in my Admin Center, Tools just contains Benchmark Survey. How do I as the account owner get the reports menu?
댓글 보기 · 2024년 9월 09일에 게시됨 · Peter Hochstrasser
0
팔로워
1
투표
0
댓글
Peter Hochstrasser님이 에 댓글을 입력함
Mike - care to add a last name initial? There's a ton of Mike's registered, but your account is not @mentionable.
Seconded. I see this kind of indexing problems when we switch light agents to agents (and vice versa) for their support stints.
It can take anywhere from seconds to several minutes until a newly assigned agent is selectable in tickets, triggers and macros; there is even a most interesting difference between bulk ticket updates and single ticket updates - the bulk updates take even longer until they finally can see the newly assigned agent.
It all comes down to not-so-quick indexing.
댓글 보기 · 2024년 6월 10일에 게시됨 · Peter Hochstrasser
0
팔로워
1
투표
0
댓글
Peter Hochstrasser님이 에 댓글을 입력함
Hi James Hanley
Thanks for taking the time to post a general "We won't do anything" message.
I'm interested in getting to know if you use AI to generate the various "other post" links that you put into your boilerplate answers. The other post you cite here has absolutely no intersection with what we try to get you to understand here.
This is worse than just posting "We are not interested in our customers" because you seem to ridicule us.
Yours truly, Peter.
댓글 보기 · 2024년 3월 19일에 게시됨 · Peter Hochstrasser
0
팔로워
0
투표 수
0
댓글
Peter Hochstrasser님이 에 댓글을 입력함
Hey @Whitney S.
Side conversations can include literally anybody - your internal experts as well as involved 3rd parties. On their part, no license is required.
댓글 보기 · 2024년 2월 23일에 게시됨 · Peter Hochstrasser
0
팔로워
0
투표 수
0
댓글
Peter Hochstrasser님이 에 댓글을 입력함
Hi Anunay Sinha
You take away functionality, and offer some bad replacement.
Then you let us steam for some time so we can see the replacement is really as bad as it first seemed.
Finally, you add the functionality back for an additional fee.
Nice practice.
Which functionality will be next?
I assume that this is all related to Customer Care...
댓글 보기 · 2024년 2월 16일에 게시됨 · Peter Hochstrasser
0
팔로워
2
투표 수
0
댓글
Peter Hochstrasser님이 에 댓글을 입력함
Hey Zendesk
This new redaction "tool" has to be a very bad joke... It basically makes the user execute manually, step by step, what the old redaction app did automatically.
I just found that I have forgotten to remove an e-mail address from a log snippet.
The address is visible multiple times.
In the old app, I'd type in the address, and it would search and redact everything, so it's GONE EVERYWHERE in the ticket after I click redact.
Now, I have to select manually each and every occurrence of the problematic text.
I think that I'm not the only admin who has better things to do than play search and replace using bad tools.
댓글 보기 · 2024년 2월 08일에 게시됨 · Peter Hochstrasser
0
팔로워
0
투표 수
0
댓글
Peter Hochstrasser님이 에 댓글을 입력함
Zendesk:
Please include some sort of Markup capabilities into the End User Instructions Text.
As it is, it is not even acting upon line ends, so I have absolutely no way to structure my instructions.
This here would be much simpler to understand (and harder to pass over)
If this ticket concerns the Axon Ivy Platform, including Designer, Engine, Portal and Market artefacts, choose Form Axon Ivy Platform.
Only if your company has an Application Support Contract with us should you choose SLA Tickets.
than this here:
If this ticket concerns the Axon Ivy Platform, including Designer, Engine, Portal and Market artefacts, choose Axon Ivy Platform. ONLY if your company has an Application Support Contract with us should you choose SLA Tickets.
Thanks for your consideration.
댓글 보기 · 2024년 1월 30일에 편집됨 · Peter Hochstrasser
0
팔로워
0
투표 수
0
댓글
Peter Hochstrasser님이 에 댓글을 입력함
The problem here is that the Zendesk infrastructure is public, and, to my knowledge, you as a user of a Zendesk subdomain do not have a way to add your own certificates (or trust chains). Therefore, you are required to have a "real" certificate that Zendesk can authenticate against a standard set of CA certificates and intermediate certificates.
A cheap (free) and safe way to get such a certificate is to use Let's Encrypt on your end, so on your local web service. Since Zendesk uses this scheme itself, it is very likely that this will work ;-).
Yours truly
Peter
댓글 보기 · 2024년 1월 19일에 게시됨 · Peter Hochstrasser
0
팔로워
0
투표 수
0
댓글