最近搜索
没有最近搜索

Shana Blackstone
已加入2021年4月16日
·
最后活动2024年10月21日
关注
0
关注者
1
活动总数
66
投票
21
订阅
24
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Shana Blackstone
Shana Blackstone 进行了评论,
Thank you for getting back to me, Patrycja. Unfortunately, you didn't answer my question. I know how to turn off the AI feature during the EAP. What I want to be clear about is the following: When the EAP is complete, can we still take advantage of the new editor features that are not AI related? We will not be purchasing the AI upgrades and want to be sure we will be able to continue using the non AI advancements to the editor when the EAP is done.
查看评论 · 已于 2024年10月21日 发布 · Shana Blackstone
0
关注者
0
投票
0
评论
Shana Blackstone 创建了一个帖子,
We are currently testing the new article editor in guide. One of the concerns I have is there is AI summaries tied into this feature. We have not been approved to move forward with using any advanced AI features of Zendesk. When the EAP is complete, can we still take advantage of the new editor features that are not AI related? I do not want my team to get excited to use the editor features only to find out because this is tied to AI we won't be able to continue using them. To be clear, we have no interest in the AI summaries in the EAP.
已于 2024年10月17日 发布 · Shana Blackstone
0
关注者
2
投票
3
评论
Shana Blackstone 进行了评论,
I noticed this link at the top of this article loads “The page you were looking for doesn't exist”.
- For a list of known limitations, see Announcing custom fields filtering in the new request list experience.
As this as been in beta for 2 years, I'd like to review any know limitations before we try to implement these changes.
查看评论 · 已于 2024年9月16日 发布 · Shana Blackstone
0
关注者
0
投票
0
评论
Shana Blackstone 进行了评论,
Having this "Collaborative working (supporting multiple users in the document at once)" from Zoe's first post would be game-changing.
We first draft all articles in Google Docs. After SME review and comments, we copy the content to Guide and reformat it (this is now easier with new Zendesk updates).
We also agree the UI wasn't really that bad. There are just so many features missing. We had to purchase an entirely separate tool to get basic features like find and replace in HTML and across multiple articles.
查看评论 · 已于 2023年12月21日 发布 · Shana Blackstone
0
关注者
2
投票
0
评论
Shana Blackstone 进行了评论,
I need clarification on the announcement for Guide. Didn't that feature come out at the beginning of March? This article speaks to the same thing, no?
查看评论 · 已于 2023年4月01日 发布 · Shana Blackstone
0
关注者
0
投票
0
评论
Shana Blackstone 进行了评论,
I posted this before, but we started using this 3rd party app to work alongside Zendesk Guide, which is fantastic. We have been using it for almost an entire year, and it is just an amazing addition. Again, I know it stinks to have another tool to utilize Zendesk, but I can't say enough good things about it. It has find and replace not just for words in your articles but even URLs. It has analytics that tells us who clicked on what article and where they went after that or what tickets they put in after that. We added an option for when a customer downvotes an article to be able to type a reason why. All of this is out-of-the-box stuff from this application. Super affordable as well. I have no affiliation with this application other than we use it. I feel bad every time I see someone add another post here waiting for a Zendesk enhancement, so I decide to add our recent feedback.
查看评论 · 已于 2023年3月15日 发布 · Shana Blackstone
0
关注者
2
投票
0
评论
Shana Blackstone 进行了评论,
Does anyone know if there is a 3rd party app in the Zendesk Marketplace that would accomplish this? While I'd rather have this addressed by Zendesk, this is now the one issue holding us back from going multibrand. I'd be interested in trying a 3rd party app in the meantime.
We offer 30+ applications that span across a diverse group of customers. Many of those customers use a wide range of our applications. We want to go multibrand to support catering our help centers to what a user would need to see and not clutter the main page with information not pertinent to every customer. But we know customers will complain if they have to go to multiple help centers to see all of their activities.
查看评论 · 已于 2023年3月15日 发布 · Shana Blackstone
0
关注者
5
投票
0
评论
Shana Blackstone 进行了评论,
We are about to rollout multibrand with our company to give customers a better Help Center experience.
Are there any plans with these enhancements to see tickets across brands by an organization and perhaps filter by brand?
We provide a wide range of software options that not all of our customers utilize. By breaking into brands, we are better able to control how much they have to search to find answers to what they might be working with. These customers might be using any number of brands, and it would be beneficial for their admins to see any tickets for all brands open for their organization in a centralized place.
查看评论 · 已于 2023年3月01日 发布 · Shana Blackstone
0
关注者
0
投票
0
评论
Shana Blackstone 进行了评论,
When reading this article I was wondering, do you mean instead of
- For articles/posts, you will receive email notifications for new articles/posts only in the section or topic.
you mean:
- For sections, you will receive email notifications for new articles/posts only in the section or topic.
I ask because I read this as if I follow a section I WOULD get emails for when new articles are added, but for following an article I would get new emails ONLY when comments are added. Just ensuring we understand this. (We don't allow comments which is why I want to confirm)
查看评论 · 已于 2022年11月11日 编辑 · Shana Blackstone
0
关注者
0
投票
0
评论
Shana Blackstone 创建了一个帖子,
This is currently how Content Cues work
- Content Cues algorithm checks once a day for matching tickets
- Tickets in less-than-Closed status get a tag applied for the 'View tickets' button
- Three of the tickets identified by the algorithm (although unsure of how it chooses which three) are populated under the 'Related tickets' dropdown
Because of bullet number 2 the number displayed stating the number of tickets contributing to the content cue is deceiving. The number displayed might be 12 but when clicking to view the tickets that were used by the algorithm to create the cue you might only see 5 tickets.
As a user I would like to access all of the tickets that contributed to the content cue to be able to fully understand what next steps we need to take to address this cue.
已于 2022年10月20日 发布 · Shana Blackstone
2
关注者
1
投票
0
评论