最近搜索


没有最近搜索

Craig Bailey's Avatar

Craig Bailey

已加入2021年4月15日

·

最后活动2024年11月06日

关注

0

关注者

0

活动总数

44

投票

21

订阅

14

活动概览

的最新活动 Craig Bailey

Craig Bailey 进行了评论,

评论Ticket basics

I do agree that auto-tagging tickets from the top 100 tags is strangely not efficient. Most ZD installations are probably very much like us using many custom fields and tags that greatly skew the pool of top tags. That's a very bad design. 

What we really want is to pin a few very specific tags that are always searched and applied on a new ticket. In our case, we're a software vendor. Anytime the word “crash” is seen in a new ticket, we want it auto-tagged by the system and take alternate actions. In fact, it seemed that it used to work this way years ago, but the current method doesn't allow anything like this. I'm not really sure what the value of auto-tagging is today with the current method. 

查看评论 · 已于 2024年11月06日 发布 · Craig Bailey

0

关注者

0

投票

0

评论


Craig Bailey 进行了评论,

社区评论 Feedback - Ticketing system (Support)

Correct, the followers did not receive any emails, and we did not see any events in the ticket event log that they were emailed.

 

Our original trigger (probably out of the box 8 years ago) simply sent a notification email to the assignee. But we'd like to ensure that we can get all followers notified. 

 

 

查看评论 · 已于 2024年10月22日 发布 · Craig Bailey

0

关注者

0

投票

0

评论


Craig Bailey 创建了一个帖子,

帖子 Feedback - Ticketing system (Support)

We recently had a ticket reopened with the original assignee was out of town, and the response was missed by a few days. However, there were followers on the ticket. While reviewing our trigger actions to better address this, we found that the followers are not an option in any of the trigger actions, specifically email to followers. Can this be added to the triggers for full notification functionality?

已于 2024年10月21日 编辑 · Craig Bailey

1

关注者

4

投票

4

评论


Craig Bailey 进行了评论,

社区评论 Feedback - Ticketing system (Support)

We're now the next victim and forced to turn on Agent Workspace which will take us backward with conversation views 30 years. (Email chains have been newest first for at least that long).  This is a non-starter with our agents and I've put it off as long as we could. Very little Zen in our lives now. 

"Zendesk customers who have moved to Agent Workspace are seeing 20% faster response resolutions on average."  -- they'd probably be 40% faster if they weren't scrolling through long email chains to get to the bottom.

We're an email only support shop, and having conversation views upside down old to new is just unacceptable. Zendesk has quite defensively (and arrogantly in my opinion) denied that this is a proper view only because it might involve other channels. What? Scrolling to the bottom of long communication chains is faster? There is no excuse that a configuration can't be made to flip that view when it's only email. I doubt anyone at Zendesk reads their email chains oldest to newest every morning. (Gmail even gives you a choice.) To pretend this is a modern conversation method is pure gaslighting.

This is our last straw after having a grandfathered plan pulled from us this year with a massive price increase (which broke all our trust going forward). We've begun the process of replacing ZD in 2024 if they can't come up with some solution. I won't start on the internal/public comments change either, which will be hated by all my agents. Again, add a simple configuration option and disable the new behavior for those that don't want it. I miss the original Zendesk company.

查看评论 · 已于 2023年11月15日 发布 · Craig Bailey

0

关注者

3

投票

0

评论


Craig Bailey 进行了评论,

评论Ticket management

I used to be able to see the email notification contents. But lately, I'm only seeing the email template? Has this changed? A bug? Do I not remember correctly?? 
For example, clicking the #20079185790995 link shown here, gives the dialog below.

查看评论 · 已于 2023年8月30日 发布 · Craig Bailey

0

关注者

0

投票

0

评论


Craig Bailey 进行了评论,

社区评论 Feedback - Ticketing system (Support)

We're seeing this behavior more and more ourselves. and it's random to the point I've advised all agents to not use it for now as vital communications are being missed.

Just this week I have two critical "mentions" in private notes that  were 

a) Not added as a follower.

b) They were NOT NOTIFIED by email. The mention remains is in the private note, but no record of notification when I look at ticket events.

查看评论 · 已于 2021年3月04日 发布 · Craig Bailey

0

关注者

1

投票

0

评论


Craig Bailey 进行了评论,

评论Managing your email

This is confusing as all get out. I don't understand why this is such an issue or important? It says add our agent's email address to the whitelist? We are configured such that any external emails to an end user ticket are all forced to go through our domain via the ZD interface (not via agent email). So how could they possibly be out of sync with the reply-to? 

I beginning to get agents flagged and no idea why are how after several years of usage. And now attachments blocked. This is all very very will-nilly it seems.

Much more deeper detailed explanations please.

查看评论 · 已于 2021年2月22日 发布 · Craig Bailey

0

关注者

1

投票

0

评论


Craig Bailey 进行了评论,

社区评论 Feedback - Reporting and analytics (Explore)

Yup, we just bumped into this limitation today as well. It is a really important field for us and reports would provide extreme business value.

查看评论 · 已于 2021年1月26日 发布 · Craig Bailey

0

关注者

1

投票

0

评论


Craig Bailey 进行了评论,

社区评论 Feedback - Reporting and analytics (Explore)

We have the same issue. We need to identify organizations whose support renewal is due. However, they may not have submitted any tickets. We could do this with Insights/GoodData. It's frustrating that they've tied the organization/user data exclusively to tickets, when it would be extremely valuable as a separate reporting silo.

查看评论 · 已于 2020年8月04日 发布 · Craig Bailey

0

关注者

0

投票

0

评论