최근 검색
최근 검색 없음

Rachel Montgomery
가입한 날짜: 2021년 4월 15일
·
마지막 활동: 2023년 1월 23일
팔로잉
0
팔로워
0
총 활동 수
47
투표 수
24
플랜 수
18
활동 개요
배지
문서
게시물
커뮤니티 댓글
문서 댓글
활동 개요
님의 최근 활동 Rachel Montgomery
Rachel Montgomery님이 에 게시물을 만듦
We have ~600 articles in our Help Center and we want to one day leverage federated search. We're supporting a product so many terms are similar which is making it more difficult to find content best suited for the situation at hand with keyword search.
Suggestion: Differentiate suggested search results by visibility setting: public vs. internal and differentiate external articles pulled in via federated search. Highlighting could be done with shading, colour-coded section/category titles, etc.
2021년 12월 30일에 게시됨 · Rachel Montgomery
1
팔로워
3
투표 수
0
댓글
Rachel Montgomery님이 에 댓글을 입력함
Agreed! Would love to see this functionality. Our use case is that we've documented our manual processes and host them in our help center, but they aren't particularly helpful for offering product support and our agents are misusing them. We're coaching against it but with our growth this will continue to pose a problem for us.
댓글 보기 · 2021년 12월 30일에 게시됨 · Rachel Montgomery
0
팔로워
6
투표 수
0
댓글
Rachel Montgomery님이 에 게시물을 만듦
I'd like to hyperlink guide articles into our macro 'descriptions' (the short summary visible to agents) to lead agents to learn more about the use case/topic the macro applies to and escalation processes that may follow. HTML isn't currently supported.
The 'workaround' is to include a URL as plaintext but that isn't user-friendly, doesn't promote usage, and equates to more clicks slowing agents down.
I also have use cases where I'd like to point to a specific section of an article (URLs are much longer) but that would just create a wall of text.
Allowing HTML or links to guides would be great to promote Guide usage directly from Support.
2021년 9월 17일에 게시됨 · Rachel Montgomery
7
팔로워
5
투표 수
1
댓글
Rachel Montgomery님이 에 게시물을 만듦
We have a couple of article verification rules set up and it'd be helpful to know which one caused an article to be unverified.
For example:
Rule 1 - general audit every 60 days.
Rule 2 - every two weeks, unverify any public articles to check that all media is up to date.
This second rule should be pretty quick to complete, but we can't identify the 'level of review' needed without knowing which rule fired. To take it a step further, being able to filter the unverified articles by the rule that fired would help us sort workload by level of effort and get things reviewed by the right teams.
2021년 5월 04일에 게시됨 · Rachel Montgomery
1
팔로워
2
투표 수
1
댓글