Pesquisas recentes
Sem pesquisas recentes

Mike Petersen
Entrou em 19 de jul. de 2023
·
Última atividade em 15 de nov. de 2023
Seguindo
0
Seguidores
0
Atividade total
12
Votos
0
Assinaturas
5
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por Mike Petersen
Mike Petersen comentou,
I understand that you are working on Answer Linking, but can you tell me a bit about it and how it is going to work.
Exibir comentário · Publicado 15 de nov. de 2023 · Mike Petersen
0
Seguidores
1
Votos
0
Comentários
Mike Petersen criou uma publicação,
Is there a way to have the ‘Button Link’ in a Message Step point to another Answer instead of a URL like it requires now?
THE REASON FOR THIS QUESTION
I HAVE RUN OUT OF STEPS, reached my 2000 step limit, and I need at least 1000 more in order to finish.
Each of my Answers contains 18 steps. In those 18 steps there are what I call 3 branch points. A Transfer branch point, a Rephrase branch point, and a Continue branch point. I can make each of those branch points an Answer in an of itself, which cuts the main Answer to 6 steps.
I have found a way to accomplish this, but it involves the customer typing one of those three words, transfer, rephrase, and/or continue. This opens up the chance for errors. That is, the customer misspelling the words. I would like to take that chance away from them, and just have them select something that would then call up the branch answer.
The only way that I can see to accomplish this is using the Button link in the Message step. But in order to use this, it requires the Button link to be a URL. There is no way that I know of the call an Answer using a URL.
Or, is there another way to accomplish this that I am not seeing.
Publicado 10 de out. de 2023 · Mike Petersen
2
Seguidores
3
Votos
2
Comentários
Mike Petersen criou uma publicação,
I have reached my limit! Well not me personally, but the Answer BOT has. It seems there is a 2000 step limit, in total, that you can have. Each of my Answers take 18 steps, some a couple more, some a couple less.
I am told the reason for this is speed and efficiency, and more than that it will cause performance issues. It would help to know what kind of performance issues.
We need somewhere around 3000 steps to in order to implement the BOT. With out that, its a non-starter for us.
Publicado 04 de out. de 2023 · Mike Petersen
5
Seguidores
18
Votos
14
Comentários
Mike Petersen criou uma publicação,
I had ask Support if there was a way to insert a 'Pause' or 'Delay' between Steps in a Answer Bot, to allow the customer some time between 'Show help Center articles' and 'Ask if the question is Resolved'.
They do not have a 'Pause' Step, but offered the following work around;
---------------
One common method involves the use of an informative message to act as a 'pause' before proceeding to the next step.
Here's how:
1. After your 'Show Help' step, add a 'Send Message' action.
2. In the message, you can add any content. Perhaps a statement like, "If you need a moment to go through the help content, take your time. When you're ready, please type 'Continue'."
3. Then add a 'Wait for Response' action and configure it to proceed to the 'Ask if question is resolved' step when the user responds with 'Continue' or similar acknowledgement.
-------------------
My problem is that I see nothing in the Answer Bot Steps that even comes close to a 'Wait for Response' step/action.
I must be missing something.
Publicado 16 de ago. de 2023 · Mike Petersen
1
Seguidor
5
Votos
3
Comentários
Mike Petersen comentou,
It has been a couple of weeks now, and still no feedback from Zendesk!
Exibir comentário · Publicado 02 de ago. de 2023 · Mike Petersen
0
Seguidores
3
Votos
0
Comentários
Mike Petersen comentou,
That is just what I am looking for also.
Exibir comentário · Publicado 02 de ago. de 2023 · Mike Petersen
0
Seguidores
2
Votos
0
Comentários
Mike Petersen comentou,
Still in a holding pattern??? Still do not see any update on this.
Exibir comentário · Publicado 19 de jul. de 2023 · Mike Petersen
0
Seguidores
1
Votos
0
Comentários