Arno (EMEA Partner)
-
Actividad total121
-
Última actividad
-
Miembro desde
-
Siguiendo0 usuarios
-
Lo siguen0 usuarios
-
Votos32
-
Suscripciones48
Comentarios
Actividad reciente de Arno (EMEA Partner)-
Ashwin, sounds interesting, can clarify a bit. I was not able to add a lookup field in organization, that would only include users from that organization. When you have tens of thousands of users a...
-
I am studying the same problem. Zendesk Guide site includes CookieBOT, and unless "Statistics" is accepted, only forms selection is visible, but nothing happens after selection. Accepting "Statisti...
-
I assume this cannot be done at least yet? Have an organization profile field with lookup for users of that organization? Use case would be able select one user of organization as "primary contact"...
-
Seems like the app inserts the signature into the editor before saving, and editor not supporting the table element strips out necessary style definitions for the table. Just a guess. Tried all tri...
-
Thanks for confirming this. Yes, this question was especially about use with multiple brands. This the case where account name causes unnecessary confusion. Noting that triggers are not really requ...
-
Viktor Osetrov I am not sure I understand correctly? Are you saying that whether we use Customer Profile Page some how affects whether we have Requester available as visible column on the Organizat...
-
Finding: Email based side conversations do not apply the same logic with attachments as normal tickets do. There is incorrect information above in this discussion. If you attach a large file to sid...
-
Has Requester column been intentionally removed from Organization tickets view? I could not find a way to add it back. It is necessary for a organization's user to see who of collegues created the ...
-
In some cases it is possible that might want to include some additional content in the trigger, that you would like to show right after your last comment. Example would be an included satisfaction ...
-
Anyone found a workaround for this in Agent Workspace? When working with multiple brands "incorrect" receiver information on ticket causes unnecessary confusion for agents. For some reason also wit...