最近の検索
最近の検索はありません

Elizabeth Toy
参加日2021年10月16日
·
前回のアクティビティ2025年2月12日
フォロー中
0
フォロワー
0
合計アクティビティ
27
投票
16
受信登録
3
アクティビティの概要
バッジ
記事
投稿
コミュニティへのコメント
記事へのコメント
アクティビティの概要
さんの最近のアクティビティ Elizabeth Toy
Elizabeth Toyさんがコメントを作成しました:
also commenting to upvote this as something we'd like to have the option to configure. we do a lot to customize our email templates to improve our end user experience, so the lack of customization of these emails makes these emails feel entirely disjointed from our other emails, and I'm shocked that y'all leave 0 options for them.
(fwiw I'd think that this could be really easily made available to customize in the same place and way as the followers emails are able to be configured. it'd make a ton of sense to me too, as this is a really close comp to what the end users are doing.)
コメントを表示 · 投稿日時:2025年2月12日 · Elizabeth Toy
0
フォロワー
0
投票
0
コメント
Elizabeth Toyさんがコメントを作成しました:
+1 to getting the actual numeric values of the CSAT scores available to report on.
it's so odd to me that you would allow a numeric rating scale as a change from the previous good/bad CSAT options, and then just translate the scores to use the same good/bad outcome as the metric for reporting. if someone gives a 3/5, in my opinion that's a 60% score, not 0.
コメントを表示 · 投稿日時:2024年11月26日 · Elizabeth Toy
0
フォロワー
3
投票
0
コメント
Elizabeth Toyさんがコメントを作成しました:
I agree with a lot of folks who'd like to edit ticket fields and more. reporting on tags in Explore via custom metrics and attributes is viable, but a lot of time and upkeep (not to mention it's not easy to manage these in Explore w/o having a centralized list…)
one piece of feedback not yet mentioned that I'd certainly find helpful would be the ability to bulk edit closed tickets from the Search page. there will likely be certain tags or other search operators I'll be able to use to identify tickets I want to edit and it would be so much more convenient to do that here vs. creating an equivalent report in Explore, exporting the resulting ticket IDs, and updating them in bulk via the API.

コメントを表示 · 投稿日時:2024年10月25日 · Elizabeth Toy
0
フォロワー
2
投票
0
コメント
Elizabeth Toyさんが投稿を作成しました:
Please give a quick overview of your product feature request or feedback and note who in your org is affected by this issue [ex. agents, admins, customers, etc.].
This affects agents. When searching in the Knowledge context, we often don't need to see/reference Community posts, but the default filter options in the Contextual workspaces (described here) don't allow for us to set a default filter on the content type. Relatedly, any filters applied to a search in the Knowledge context aren't sticky (if an agent added a content type filter for a search on one ticket, the same filter isn't set when they open a new ticket).
What problem do you see this solving?
Agents don't need to repeatedly apply a content type filter in the Knowledge context to filter out generally irrelevant results.
When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business?
This comes up at least on a weekly basis when searching for an article to add a link to in our ticket reply.
Are you currently using a workaround to solve this problem?
- Sifting through all the results.
- Applying the filter to the Knowledge context searches.
- Using the front-end KB search (where we have disabled Community posts as a search source).
What would be your ideal solution to this problem? How would it work or function?
If the default filters allowed for a filter on the content type. Or potentially if an agent's own applied filters were sticky.
投稿日時:2024年7月08日 · Elizabeth Toy
1
フォロワー
1
投票
0
コメント
Elizabeth Toyさんが投稿を作成しました:
Feature Request Summary:
The Community dataset in Explore should be expanded to include information about the User and their Organization.
Description/Use Cases:
We have a lot of information that we keep on the Organization records in Zendesk, which we'd like to be able to reference when reporting on who is posting in our Community (Gather). For example, we'd like to be able to report on how many customers beneath a certain ARR value are engaging/posting. The ARR value is stored on the Org record in Zendesk (and users are part of Organizations based on their email domain) so if we could have Community users' Organization attributes in the dataset, we'd be able to build a report for this in Explore.
Business impact of limitation or missing feature:
If we wanted to get any information about the Organizations of the users who are posting, we would have to do this in a different tool to cross-reference the user ID info that we do have in the Community dataset with their associated Organization's ARR (or other) information.
投稿日時:2024年4月24日 · Elizabeth Toy
1
フォロワー
2
投票
2
コメント
Elizabeth Toyさんがコメントを作成しました:
コメントを表示 · 投稿日時:2023年2月08日 · Elizabeth Toy
0
フォロワー
2
投票
0
コメント
Elizabeth Toyさんがコメントを作成しました:
+1. While I can understand the reasoning to only be able to link to a single problem ticket, the reality is that sometimes a requester will bring up multiple issues during the course of a single ticket. It would be great for the incident/problem functionality in Zendesk to be a little more flexible to handle this use case. As it currently stands, we'd have to spin up a new ticket (also, no built-in way to do this in Zendesk, at least that I'm aware of) and then both us and the requester have 2 ticket conversations in our inboxes/queues to keep track of.
コメントを表示 · 投稿日時:2022年12月02日 · Elizabeth Toy
0
フォロワー
0
投票
0
コメント
Elizabeth Toyさんがコメントを作成しました:
wanted to check/confirm something... if a webhook was created by user A, and then down the line user A is no longer an agent in Zendesk, does that webhook they created still remain?
コメントを表示 · 投稿日時:2022年2月09日 · Elizabeth Toy
0
フォロワー
0
投票
0
コメント