最近搜索
没有最近搜索

Riah Lao
已加入2021年4月16日
·
最后活动2025年2月11日
关注
0
关注者
0
活动总数
200
投票
28
订阅
118
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Riah Lao
Riah Lao 进行了评论,
Hi,
1. When will this be available outside signed-in end users?
2. When will the quick answers results be available via API?
查看评论 · 已于 2025年2月03日 发布 · Riah Lao
0
关注者
0
投票
0
评论
Riah Lao 进行了评论,
Is it possible to retrieve the KB quick answer result via API?
查看评论 · 已于 2025年1月23日 发布 · Riah Lao
0
关注者
0
投票
0
评论
Riah Lao 进行了评论,
What API can we use to retrieve the Quick Answer result section for KB search?
查看评论 · 已于 2025年1月23日 发布 · Riah Lao
0
关注者
0
投票
0
评论
Riah Lao 进行了评论,
Hi,
Zendesk's current metrics, "First Reply Time" and "Requester Wait Time," provide a limited view of total customer wait time.
- First Reply Time only considers tickets that have received a reply, excluding those still pending.
- Requester Wait Time is calculated only after a ticket transitions out of "New," "Open," or "On-hold" status, potentially missing long wait times for unresolved tickets.
This limitation hinders our ability to accurately measure and improve overall customer wait times.
Are there any native Zendesk features or workarounds to track more accurate measure of total customer wait time, encompassing both First Reply Time and the time spent waiting for an initial response. Have other Zendesk users encountered this issue and found effective solutions?
查看评论 · 已于 2024年11月04日 发布 · Riah Lao
0
关注者
0
投票
0
评论
Riah Lao 进行了评论,
Is it in your roadmap for AI to summarize overall contacts (not just on ticket level) and not just by grouping intents?
Example:
“User are frustrated with delayed delivery issues. xxxxxxx”
Subtopics:
80% users are experiencing xxxxxx
20% users are exeperiencing xxxxxx
查看评论 · 已于 2024年10月24日 发布 · Riah Lao
0
关注者
0
投票
0
评论
Riah Lao 进行了评论,
Hi,
Our agents reported that the notifications do not work when we had auto accept enabled. They have notifications enabled already.
查看评论 · 已于 2024年5月02日 发布 · Riah Lao
0
关注者
0
投票
0
评论
Riah Lao 进行了评论,
Hi Amy Dee
Just want to clarify something regarding what you mentioned on SLA badge rounding up: "SLA badges round their numbers to hours (or days) when the target is far enough away. This means two tickets could both have a "2 business hours" badge, but one is due Friday at 4:50pm while the other is due Monday at 9:10am. Agents should prioritize the Friday ticket, but they need an easy way to know which is which."
Our FRT SLA is set to 3hrs. We have 2 tickets and SLA shows as:
Ticket#1: Received 40mins ago and FRT Next SLA badge is displayed as 2h (2h 20min to be exact but shows as 2h)
Ticket#2: Received 20mins ago and FRT Next SLA badge is displayed as 3h (2h 40min to be exact but shows as 3h)
How does the system round the SLA to be displayed?
Thanks!
查看评论 · 已于 2024年5月01日 发布 · Riah Lao
0
关注者
0
投票
0
评论
Riah Lao 进行了评论,
Hi, does {{ticket.description}} includes the customer's attachment?
查看评论 · 已于 2024年3月01日 发布 · Riah Lao
0
关注者
0
投票
0
评论
Riah Lao 进行了评论,
Hi,
Thanks for your inputs Sydney Neubauer. We actually did not use the trigger anymore as we changed requirements. Instead of checking for ticket group, we want to fire it only for top agent performers so we used the agent organization field instead (as a workaround) to identify that:
We moved the if condition from the email notify trigger to the DC instead. However, if we check for agent.organization == "XYZ", it does not work. But if we do it like this below, it works:
查看评论 · 已于 2024年2月27日 发布 · Riah Lao
0
关注者
0
投票
0
评论