Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

rajesh
Beigetreten 22. Okt. 2021
·
Letzte Aktivität 17. Juli 2024
Folge ich
0
Follower
1
Gesamtaktivitäten
59
Stimmen
50
Abonnements
3
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von rajesh
rajesh hat einen Kommentar hinterlassen
I too support Jamie Noell 's comment
This is the primary reason, especially in the EU, why we would NOT recommend ZenDesk.
One of my clients lost a large number of customers for this reason.
Kommentar anzeigen · Bearbeitet 17. Juli 2024 · rajesh
0
Follower
0
Stimmen
0
Kommentare
rajesh hat einen Kommentar hinterlassen
Probably after 10 years have passed? What bothers me is the absolutely cavalier approach to a legal problem clients are facing. Sending private information to others is breaking the law.
ZenDesk is a US company and simply does not care about GDPR issues.
Kommentar anzeigen · Gepostet 07. Apr. 2023 · rajesh
0
Follower
1
Stimme
0
Kommentare
rajesh hat einen Kommentar hinterlassen
Hi,
I am helping a client migrate an old support URL which is being redirected to ZenDesk via easyredir [dot] com. Here is the scenario:
Current:
support [dot] myclient [dot] com is CNAME'd to myclienthelp [dot] ssl [dot] zendesk [dot] com
Legacy help [dot] myclient [dot] com goes to easyredir [dot] com which redirects to myclienthelp [dot] ssl [dot] zendesk [dot] com
Any chance we can remove easyredir [dot] com by using the alternate subdomain name?
Kommentar anzeigen · Gepostet 24. Mai 2022 · rajesh
0
Follower
0
Stimmen
0
Kommentare
rajesh hat einen Kommentar hinterlassen
Is there a way to restrict/prevent a merge, for example when the email ID's are different? The merge UI seems to lend itself to errors and CX personnel, no matter how good, are human.
There are GDPR privacy issues, security issues, and plain customer sanity issues that we are worried about.
Kommentar anzeigen · Bearbeitet 10. Nov. 2021 · rajesh
0
Follower
5
Stimmen
0
Kommentare
rajesh hat einen Kommentar hinterlassen
Thank you. I studied your documentation to find a way to quarantine tickets in a way that allowed analysis by our team at leisure but could not find anything that has been released; I believe you are working on some thing like what I really wanted.
I think your proposal may work. I'll advise my client and report back. Thank you for support.
Kommentar anzeigen · Gepostet 23. Sept. 2021 · rajesh
0
Follower
0
Stimmen
0
Kommentare
rajesh hat einen Post erstellt
Background: My client has many levels of CX personnel, some new and some very experienced. We are a security company.
Problem: We noticed that, despite all the training, some CX personnel automatically click on attachments and may even type the passwords supplied in the text. These tickets are shared and many CX people take over from each other.
Thoughts: Is it possible for a CX person to move the ticket to another group, say S (for security). This ticket can now be opened ONLY by members of the S group.
I am looking for a workaround or some feature that will help move these tickets out of the main group. Some of my security experts can then examine the attachments and other text and respond appropriately.
All suggestions welcome.
Gepostet 22. Sept. 2021 · rajesh
0
Follower
3
Stimmen
2
Kommentare