Búsquedas recientes
No hay búsquedas recientes

David
Incorporación 10 nov 2023
·
Última actividad 15 may 2024
Seguimientos
0
Seguidores
0
Actividad total
105
Votos
0
Suscripciones
49
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de David
David hizo un comentario,
Hi Dave,
can you try this curl?
curl -u /token: -O
We'll work on updating the documentation
Ver comentario · Publicado 15 may 2024 · David
0
Seguidores
1
Voto
0
Comentarios
David hizo un comentario,
Hi Dave,
Have you noticed anything in the developer console? Any Javascript problems that might just point to a UI issue?
Ver comentario · Publicado 15 may 2024 · David
0
Seguidores
0
Votos
0
Comentarios
David hizo un comentario,
Hi Sharon,
This can be viewed on a per/agent or per/team basis in the Time Off Management page.
Ver comentario · Publicado 12 abr 2024 · David
0
Seguidores
0
Votos
0
Comentarios
David hizo un comentario,
Hi Farventure,
It looks like you're running in to a limitation with Whatsapp where you can't actually close out a conversation.
I would suggest creating a trigger that will close a ticket if there's a "close" tag (as an example). Once a messaging ticket is closed, it will give the customer an option to start a new conversation.
Article for reference
Ver comentario · Publicado 27 mar 2024 · David
0
Seguidores
0
Votos
0
Comentarios
David hizo un comentario,
Hi Helen,
Zendesk's Facebook integration does not automatically create tickets from @mentions on other pages or in comments/posts not directly on your Page.
The integration primarily focuses on direct interactions on your Page itself, such as direct messages (DMs), comments on your Page's posts, and visitor posts to your Page.
This is due to limitations in Facebook's API and how third-party services can access and interact with Facebook data.
Ver comentario · Publicado 27 mar 2024 · David
0
Seguidores
0
Votos
0
Comentarios
David hizo un comentario,
@Cloudhuset A/S
The issue you're facing with Zendesk's webhook activity/invocations tracking, especially regarding the inability to see the full URL invoked by a webhook, including dynamic elements like {{ticket.id}}, is indeed challenging.
Given the current limitations, you may want to look in to:
External Logging Service: Use an intermediate service or a serverless function (AWS Lambda, Azure Functions, Google Cloud Functions) that your webhook calls first. This service would log the full URL (including the {{ticket.id}} replacement) and then make the API call to Zendesk on your behalf. This approach allows you to implement detailed logging according to your needs.
Embedded Identifiers in Payload: Include additional identifiers or logging information within the webhook payload itself. While this doesn't solve the visibility of the URL directly, it can help correlate the invocation with specific actions or tickets.
Ver comentario · Publicado 27 mar 2024 · David
0
Seguidores
0
Votos
0
Comentarios
David hizo un comentario,
Efrat Barak Zadok
In the Filters section, look for the attribute you used to create your set. This could be Assignee Name or a similar field.
Once you find the appropriate filter, you'll need to apply your set. Since Zendesk Explore doesn't directly allow filtering by sets in the query builder, you will manually select the values that match your set. If your set was created based on agent names, manually select these names under the Assignee Name filter.
- If the exact mechanism to directly apply a "set" as described doesn't match with Zendesk Explore's UI due to its limitations or updates, the goal remains to replicate the set's conditions by manually applying the same filters that define your set.
Ver comentario · Publicado 27 mar 2024 · David
0
Seguidores
0
Votos
0
Comentarios
David hizo un comentario,
Ver comentario · Publicado 22 mar 2024 · David
0
Seguidores
1
Voto
0
Comentarios
David hizo un comentario,
Steve Musial
It looks like the only CSS official documentation we have is this right here.
I can pass that info along to see if our documentation team can add more to this.
Ver comentario · Publicado 12 mar 2024 · David
0
Seguidores
0
Votos
0
Comentarios
David hizo un comentario,
Steve Musial
The "lighten" and "darken" functions you mentioned are actually part of the Sass preprocessor.
Regarding the available functions in Sass, there are several built-in functions beyond just "lighten" and "darken" that can manipulate colors, perform mathematical operations, and more. Some examples include "rgba", "mix", "scale-color", "invert", and "adjust-hue". You can find detailed documentation for Sass functions on the official Sass website.
Ver comentario · Publicado 11 mar 2024 · David
0
Seguidores
0
Votos
0
Comentarios