최근 검색


최근 검색 없음

Allison Sargent's Avatar

Allison Sargent

가입한 날짜: 2021년 4월 15일

·

마지막 활동: 2024년 10월 30일

팔로잉

0

팔로워

0

총 활동 수

141

투표 수

33

플랜 수

80

활동 개요

님의 최근 활동 Allison Sargent

Allison Sargent님이 에 댓글을 입력함

댓글Working with articles in the knowledge base

Are we able to modify the text in each branded article to keep it “on brand” if that makes sense? I often create one copy for my FOUR help centers, but then I have to go in a alter the content where I mention the Brand name. Seems like I wouldn't be able to do that, since it would update across every article, correct?

댓글 보기 · 2024년 9월 30일에 게시됨 · Allison Sargent

0

팔로워

0

투표 수

0

댓글


Allison Sargent님이 에 댓글을 입력함

댓글Working with articles in the knowledge base

Tetiana Gron would semantic search solve for this? 

댓글 보기 · 2023년 8월 11일에 게시됨 · Allison Sargent

0

팔로워

0

투표 수

0

댓글


Allison Sargent님이 에 댓글을 입력함

댓글Web Widget documentation

Hello! Quick question, how is this different from the "Ask for details" step that is currently offered in the Flow Builder UI? 

댓글 보기 · 2023년 8월 09일에 게시됨 · Allison Sargent

0

팔로워

0

투표 수

0

댓글


Allison Sargent님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Help Center (Guide)

Same as Lindsey and others, we NEED the ability to make internal comments on public articles to help agents. This helps to reduce redundancy and minimize content (which therefore makes it easier to surface the RELEVANT content) for agents and users. 

As an app developer, we sometimes need to inform agents about a recent bug or issue, so it would be lovely to copy/paste the bug link in the articles that the user may go to or try to use to self-serve due to said bug. It will help the agent to remember there's a current issue and to let the user know we are aware and working on a fix. 

I also collaborate with people outside of my dept as a KCM, so I work with Product and Marketing teams who do NOT have access to or use Zendesk. While we have updated permissions for those "lite" users, it would be amazing to share the Guide link with them, and then they can essentially "comment" on the article just like a Google doc. Cross-department collaboration is at an all-time high and this feature would really help to streamline the effort. 

댓글 보기 · 2023년 5월 22일에 게시됨 · Allison Sargent

0

팔로워

3

투표 수

0

댓글


Allison Sargent님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Chat and Messaging (Chat)

+1! I accidentally duplicated this request, but we NEED this asap! Being a team of one, this duplication takes so much longer than if I could simply redirect the user to an existing tree and/or branch. 

I also agree with the ability to help nudge the user to a helpful flow or article with the initial interaction, rather than easily pushing to a live agent (when in fact the answer existed in flow builder, it's just that the bot failed to understand the intent from the first interaction)

 

댓글 보기 · 2023년 5월 02일에 편집됨 · Allison Sargent

0

팔로워

1

투표

0

댓글


Allison Sargent님이 에 댓글을 입력함

댓글Using legacy AI agent functionality

Same as Cassie Salgado, We'd like to drill into the tickets where the user marked the flow as "unresolved/not helpful" but that field isn't populating....

댓글 보기 · 2023년 5월 02일에 게시됨 · Allison Sargent

0

팔로워

1

투표

0

댓글


Allison Sargent님이 에 댓글을 입력함

커뮤니티 댓글 Feedback - Chat and Messaging (Chat)

I was not aware of the copy/paste within the same branded chatbot, that's good to know. However, the desire to copy/paste in a separate chatbot would be great! I have 4 branded chatbots, and some of the steps are the same, so it would be great to copy the flow and then just tweak the verbiage and articles linked. Thanks for your consideration Lisa Tam

댓글 보기 · 2023년 4월 04일에 게시됨 · Allison Sargent

0

팔로워

0

투표 수

0

댓글


Allison Sargent님이 에 게시물을 만듦

게시물 Feedback - Chat and Messaging (Chat)

With Flow Builder, I'd like to branch out to a separate answer tree and not have to duplicate the same information on two separate branches. I find myself reusing information in a separate answer, so it would be helpful to be able to redirect a user to a separate Tree ID (Zingtree has this). 

I don't want to have to manually re-create the same information in one tree when it was already created and published in another. On top of that, flow builder does not allow the ability to copy/paste tree branches/steps and insert into a separate tree...the ability to copy/paste only lives inside the current tree you're working on (which is really only helpful for the transfer to agent steps) 

Another feature request: Ability to customize your "closing" flow, aka, if I transfer to an agent, I'd love to somehow store that template, then easily select it and insert (without having to add it in EACH time) I want to transfer. Flow Builder "templated responses" would be pretty helpful to ensure consistent brand voice across all chatbots/flows and help streamline the creation process. 

2023년 3월 27일에 게시됨 · Allison Sargent

3

팔로워

4

투표 수

3

댓글


Allison Sargent님이 에 게시물을 만듦

게시물 Feedback - Chat and Messaging (Chat)

Hi, I'd like the ability to redirect to a separate answer flow. Let's say I have a "Can't login" answer tree, and part of the process is asking if they need to reset their password (one reason why they can't login) or if they forgot their email (a separate scenario, for example) 

In this case, I already have an answer tree for "reset password" so I'd like to push the user (if they select "yes" I forget my password and need to reset it") to the existing RESET PW tree, as opposed to me having to re-create the same Password reset flow within the Can't login flow. 

I'm trying to prevent having to manually re-type the SAME flows, and that brings me to the issue with not being able to clone answer trees within the same bot....

2023년 3월 15일에 게시됨 · Allison Sargent

0

팔로워

2

투표 수

2

댓글


Allison Sargent님이 에 댓글을 입력함

댓글Working with articles in the knowledge base

Liz Tran Unfortunately, there's no feature for adding internal notes to a Guide article. I know this because I (along with many others) have been requesting this for quite some time! 

Here's the feature request that should relate to your request.

댓글 보기 · 2023년 1월 18일에 게시됨 · Allison Sargent

0

팔로워

0

투표 수

0

댓글