Vor Kurzem aufgerufene Suchen


Keine vor kurzem aufgerufene Suchen

bgoossens's Avatar

bgoossens

Beigetreten 16. Okt. 2021

·

Letzte Aktivität 22. Nov. 2021

Folge ich

0

Follower

0

Gesamtaktivitäten

21

Stimmen

0

Abonnements

9

AKTIVITÄTSÜBERSICHT

Neueste Aktivität von bgoossens

bgoossens hat einen Kommentar hinterlassen

KommentarCustomer management and profiles

Article is not up to date (new admin section).

How can I enable agents to create end users?

Kommentar anzeigen · Gepostet 22. Nov. 2021 · bgoossens

0

Follower

1

Stimme

0

Kommentare


bgoossens hat einen Kommentar hinterlassen

KommentarUsing AI agents for messaging

Is it possible to disable the chat bot in the messenger?

Is it also possible to enable dynamic content for messenger? Automatic translations are just not good enough. Looks silly from customer point of view. 

Kommentar anzeigen · Gepostet 04. Nov. 2021 · bgoossens

0

Follower

3

Stimmen

0

Kommentare


bgoossens hat einen Kommentar hinterlassen

Community-Kommentar Q&A - Objects, workspaces, and rules

Hi, what is the best way to trigger the API target (put) to change the requester?

I would also like to change the requester of an incoming ticket based on the phone number that is provided in the title of the ticket. Our Voip solution automatically creates tickets for everyone taken phone call. 

Kommentar anzeigen · Gepostet 20. Okt. 2021 · bgoossens

0

Follower

0

Stimmen

0

Kommentare


bgoossens hat einen Post erstellt

Post Developer - Zendesk Apps Framework (ZAF)

We face an obstacle when integrating the authenticate that Zendesk support suggest for custom apps. We always getting 422 error code (Unprocessable Entity) with any api we call when enabling the secure:true which is documented in zendesk support website. Does someone has an explanation why this is happening?

The error message is: “failed to get installation and oauth information for app”

https://developer.zendesk.com/documentation/apps/app-developer-guide/using-the-apps-framework/#encoding-and-sending-json-web-tokens

We understand that you can't get the authenticated user token within the Custom App, currently the App framework's client.request() method supports supports encoding and sending JSON Web Token (JWT) that should suffice to authenticate and authorize the Agent on your back-end.

Gepostet 15. Sept. 2021 · bgoossens

0

Follower

4

Stimmen

4

Kommentare


bgoossens hat einen Kommentar hinterlassen

KommentarTicket automation and collaboration

That's correct, thanks. This makes side conversations a better solution.

What is also possible is to assign the ticket to a group of light agents. You can make groups of light agents as long as there is one real agent part of the group. 

 

 

Kommentar anzeigen · Gepostet 24. Aug. 2021 · bgoossens

0

Follower

0

Stimmen

0

Kommentare


bgoossens hat einen Kommentar hinterlassen

KommentarTicket automation and collaboration

Thanks. By setting triggers where condition comment = private I should be able to set some proper notifications. 

If i assign a ticket directly to an agent and subsequently I make a internal note, then it arrives also as a TO mail (due to trigger set). Or will it arrive as a CC when I allocate it to a group of agents?

 

 

Kommentar anzeigen · Gepostet 23. Aug. 2021 · bgoossens

0

Follower

0

Stimmen

0

Kommentare


bgoossens hat einen Kommentar hinterlassen

KommentarTicket automation and collaboration

In the situation that all my colleagues have access to zendesk (as light agents) why should I use side conversations instead of internal notes?

Kommentar anzeigen · Gepostet 23. Aug. 2021 · bgoossens

0

Follower

0

Stimmen

0

Kommentare


bgoossens hat einen Kommentar hinterlassen

KommentarFormatting and customizing your email

Yes it makes no sense at all to do it like this and it is insane that its not possible to change this.

Also, the welcome email is triggered from an action in the helpcenter of the brand, so the system should know where the end user is coming from. 

 

 

 

Kommentar anzeigen · Gepostet 05. Juli 2021 · bgoossens

0

Follower

2

Stimmen

0

Kommentare


bgoossens hat einen Kommentar hinterlassen

KommentarFormatting and customizing your email

Hi Audrey, the subject of the welcome email has the following format: "[account name] welcome email".

The account name is in our case the name of the parent company which has multiple brands. I had to change the account name to "[]" just to make sure that not the name of the parent company is shown in the title of the welcome email to end users of "Brand X "

Anyway, the welcome email reflects as such not the brand name, so I don't understand your comment. 

Kommentar anzeigen · Gepostet 05. Juli 2021 · bgoossens

0

Follower

0

Stimmen

0

Kommentare


bgoossens hat einen Kommentar hinterlassen

Community-Kommentar Feedback - Ticketing system (Support)

Same need. In addition, the brand used in the title is even incorrect!

Kommentar anzeigen · Gepostet 01. Juli 2021 · bgoossens

0

Follower

3

Stimmen

0

Kommentare