最近搜索
没有最近搜索

Lydia Forsyth
已加入2023年1月09日
·
最后活动2024年2月13日
关注
0
关注者
0
活动总数
138
投票
66
订阅
39
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Lydia Forsyth
Lydia Forsyth 进行了评论,
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
}
}
}
查看评论 · 已于 2024年2月09日 发布 · Lydia Forsyth
0
关注者
1
投票
0
评论
Lydia Forsyth 进行了评论,
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");
}
查看评论 · 已于 2024年2月08日 编辑 · Lydia Forsyth
0
关注者
1
投票
0
评论
Lydia Forsyth 进行了评论,
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!
查看评论 · 已于 2024年2月08日 发布 · Lydia Forsyth
0
关注者
0
投票
0
评论
Lydia Forsyth 进行了评论,
Will this be used for voicemails too?
Will it be able to assess customer sentiment and provide next steps?
查看评论 · 已于 2023年12月15日 发布 · Lydia Forsyth
0
关注者
0
投票
0
评论
Lydia Forsyth 进行了评论,
Will this be rolling out for a bit? I don't see these changes quite yet and am just curious.
查看评论 · 已于 2023年11月16日 发布 · Lydia Forsyth
0
关注者
0
投票
0
评论
Lydia Forsyth 进行了评论,
Lydia Forsyth 进行了评论,
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?
查看评论 · 已于 2023年10月12日 发布 · Lydia Forsyth
0
关注者
0
投票
0
评论