Búsquedas recientes


No hay búsquedas recientes

Lydia Forsyth's Avatar

Lydia Forsyth

Incorporación 09 ene 2023

·

Última actividad 13 feb 2024

Seguimientos

0

Seguidores

0

Actividad total

138

Votos

66

Suscripciones

39

RESUMEN DE LA ACTIVIDAD

Última actividad de Lydia Forsyth

Lydia Forsyth hizo un comentario,

Comentario de la comunidad Developer - Zendesk APIs

I'm so glad I could help out! :D 

Ver comentario · Publicado 09 feb 2024 · Lydia Forsyth

0

Seguidores

1

Voto

0

Comentarios


Lydia Forsyth hizo un comentario,

Comentario de la comunidad Developer - Zendesk APIs

I wanted to post here to let folks know, if you have more than one line that you want to put in the internal note, just add /n to create line breaks. It looks strange but it works! Here is an example code with it, I am using liquid placeholders to pull in field info: 

{
  "ticket": {
    "comment": {
      "body": "Hi {{ticket.requester.first_name}},\nThank you for reaching out to our team!\nHere is a receipt of what you selected in our form:\n{% comment %}Request:{% endcomment %}\n{% if ticket.ticket_field_000000000000000!= "" %}\nEmail: {{ticket.ticket_field_0000000000000000}}\n{% else %}\n{% endif%}",
      "public": false
    }
  }
}

 

Ver comentario · Publicado 09 feb 2024 · Lydia Forsyth

0

Seguidores

1

Voto

0

Comentarios


Lydia Forsyth hizo un comentario,

Comentario de la comunidad Q&A - Objects, workspaces, and rules

ah ha! I was able to figure it out, I needed to filter it by the specific text for it to know what text to change. Code below: 

if (ticketForm == 26011737489683) {
         
          //Change the description for the subject field
          $("#request_subject_hint").filter(":contains('former text here')").text("new text here");

  }

Ver comentario · Editado 08 feb 2024 · Lydia Forsyth

0

Seguidores

1

Voto

0

Comentarios


Lydia Forsyth hizo un comentario,

Comentario de la comunidad Q&A - Objects, workspaces, and rules

Hi Brandon, thank you for letting me know! I'm needing the description to just be different for this one form, but otherwise want it the same across the board and am not sure how to do this. I really appreciate your help! 

Ver comentario · Publicado 08 feb 2024 · Lydia Forsyth

0

Seguidores

0

Votos

0

Comentarios


Lydia Forsyth hizo un comentario,

Comentario de la comunidad Q&A - Objects, workspaces, and rules

I'm needing help, I used the code above to append to the subject description, but I would rather just have that old default description be hidden. What code would I need to do that?

Ver comentario · Editado 06 feb 2024 · Lydia Forsyth

0

Seguidores

0

Votos

0

Comentarios


Lydia Forsyth hizo un comentario,

Comentario de la comunidad Feedback - Ticketing system (Support)

Liquid Markup is a way to also add values to the text field, and would help with automating workflows with macros. +1 for this! 

Ver comentario · Publicado 02 ene 2024 · Lydia Forsyth

0

Seguidores

0

Votos

0

Comentarios


Lydia Forsyth hizo un comentario,

ComentarioManaging Talk

Will this be used for voicemails too?

Will it be able to assess customer sentiment and provide next steps? 

Ver comentario · Publicado 15 dic 2023 · Lydia Forsyth

0

Seguidores

0

Votos

0

Comentarios


Lydia Forsyth hizo un comentario,

ComentarioAnnouncements

Will this be rolling out for a bit?  I don't see these changes quite yet and am just curious. 

Ver comentario · Publicado 16 nov 2023 · Lydia Forsyth

0

Seguidores

0

Votos

0

Comentarios


Lydia Forsyth hizo un comentario,

Comentario de la comunidad Feedback - Ticketing system (Support)

@...

We would definitely like to be part of the EAP for the agent created first time reply SLA. We are finding it difficult to keep track of tickets that are agent created if they don't have an SLA apply.

Ver comentario · Publicado 02 nov 2023 · Lydia Forsyth

0

Seguidores

0

Votos

0

Comentarios


Lydia Forsyth hizo un comentario,

ComentarioUsing Built by Zendesk apps

Dane I see you commented on here before - thus the tag.
I'm wondering if there is a way to limit in a more specific way what groups can view different groups? So I want the Luxury group to not see Support Escalations group and I want the Support group to not see the Luxury Escalations group, however; it seems like if I put the Support Escalations group and Luxury escalations group as the hidden group IDs, and put the Luxury group and Support Group as the targeted groups, then neither will see either of those groups. 

Do you know if Zendesk has on it's roadmap a way to hide specific groups from groups? 

Ver comentario · Publicado 12 oct 2023 · Lydia Forsyth

0

Seguidores

0

Votos

0

Comentarios