Vor Kurzem aufgerufene Suchen
Keine vor kurzem aufgerufene Suchen

Phil Holcombe
Beigetreten 15. Apr. 2021
·
Letzte Aktivität 27. Okt. 2021
Folge ich
0
Follower
0
Gesamtaktivitäten
16
Stimmen
3
Abonnements
9
AKTIVITÄTSÜBERSICHT
BADGES
BEITRÄGE
POSTS
COMMUNITY-KOMMENTARE
BEITRAGSKOMMENTARE
AKTIVITÄTSÜBERSICHT
Neueste Aktivität von Phil Holcombe
Phil Holcombe hat einen Kommentar hinterlassen
The list of countries is our specific pain point. Is there any workaround, perhaps using Javascript?
Kommentar anzeigen · Gepostet 10. Jan. 2020 · Phil Holcombe
0
Follower
5
Stimmen
0
Kommentare
Phil Holcombe hat einen Kommentar hinterlassen
Hi David,
I imagine it would be possible through the API, if you have development resources.
Alternatively, have you considered using a trigger that sends an email, that then creates a support ticket? I'm not 100% sure it would work, because Zendesk might catch it as spam, or have some other filters in place. Worth a try.
Phil @ Nexmo
Kommentar anzeigen · Gepostet 05. März 2016 · Phil Holcombe
0
Follower
0
Stimmen
0
Kommentare
Phil Holcombe hat einen Kommentar hinterlassen
Hi Colin,
Interesting suggestion, thanks.
Am I right in thinking that the internal content would be visible to any customer that was curious enough to go and look for it, by viewing the page source?
If so, that would not be appropriate for anything really confidential, but might help in some circumstances.
Phil
Kommentar anzeigen · Gepostet 22. Jan. 2015 · Phil Holcombe
0
Follower
0
Stimmen
0
Kommentare
Phil Holcombe hat einen Post erstellt
The current Help Center permission model seems to restrictive. Rather than having an article that is entirely public, or entirely internal, we'd like to be able to have both types of content.
Just like a ticket has public and private comments.
The benefits are:
- Have the same structure for internal and external content.
- Add internal notes about the same content, within the context of the external document.
- Make it easier to maintain both internal and external content at the same time.
Gepostet 21. Jan. 2015 · Phil Holcombe
21
Follower
26
Stimmen
27
Kommentare