Recherches récentes
Pas de recherche récente

Support Department
Adhésion le 15 avr. 2021
·
Dernière activité le 14 oct. 2024
Suivis
0
Abonnés
0
Activité totale
38
Votes
15
Abonnements
14
APERÇU DES ACTIVITÉS
BADGES
ARTICLES
PUBLICATIONS
COMMENTAIRES DE LA COMMUNAUTÉ
COMMENTAIRES SUR L’ARTICLE
APERÇU DES ACTIVITÉS
Dernière activité effectuée par Support Department
Support Department a ajouté un commentaire,
Ok..so this is an 'intelligent' bot. In this case, is deleting the web-request page 'new_request_page.hbs' be the solution? Or do I have other options?
Afficher le commentaire · Publication le 09 août 2023 · Support Department
0
Abonnés
0
Votes
0
Commentaire
Support Department a ajouté un commentaire,
Shouldn't commenting-out {{request_form}} already do the job?
Afficher le commentaire · Publication le 09 août 2023 · Support Department
0
Abonnés
0
Votes
0
Commentaire
Support Department a ajouté un commentaire,
Thank you for your response. I believe you're referring to the second 'custom theme' section in the linked article. Meaning, I would need to edit the standard theme, e.g. by removing the request-form page? Keeping the request-form page, but 'hiding/commenting-out' the request form {{request_form}} doesn't change the situation. The spam-bot can still send requests via the web-form.
Afficher le commentaire · Publication le 09 août 2023 · Support Department
0
Abonnés
0
Votes
0
Commentaire
Support Department a créé une publication,
We have two reasons why we want to deactivate the request form on the
/hc/en-us/requests/new)
page.
1. We dont want user to submit queries via this channel.
2. Some spam-bot is bombing us via the request-form.
Publication le 08 août 2023 · Support Department
0
Abonnés
2
Votes
6
Commentaires
Support Department a ajouté un commentaire,
Hi Austin,
Thank you for the answer. In our case we have some specific article links embedded and which show up when typical keywords are in the request (used liquid for that).
Haven't tried Google Analytics yet, but will do so. Is this the only option?
Would there also be a HTML option (e.g. an embedded button which 'fires' some actions when clicked by the requester)?
Afficher le commentaire · Publication le 28 juil. 2021 · Support Department
0
Abonnés
0
Votes
0
Commentaire
Support Department a ajouté un commentaire,
I have added links to KB articles in automated replies to customers. But I never know if the requester clicked the link.
Is there any way or trick with liquid to find out whether this link has been clicked (viewed) by the customer?
Afficher le commentaire · Publication le 15 juil. 2021 · Support Department
0
Abonnés
0
Votes
0
Commentaire
Support Department a ajouté un commentaire,
Hi,
I want to use {{answer_bot.article_count}} and {{answer_bot.article_list}} in a Notify Target action.
As I understand all triggers that are to fire upon the same triggering event are evaluated and then fire 'together'.
I have following scenarios:
Scenario 1:
- Event: Ticket is created:
- Action: Trigger 1: add some links and information in email reply+ Suggest AB articles to requester + set Tag ab_fired + Notify Target (internal) of suggested articles (with above placeholders).
- Result: the target doesn't receive the list of suggested articles.
On the other hand if I change the above to:
Scenario1:
- Event: Ticket is created
- Actions:
- Trigger cycle 1:
- Trigger 1: add some links and information in email reply + Suggest AB articles to requester + set Tag 'ab_fired'
- Trigger cycle 2:
- Trigger 2 (fires on tag 'ab_fired'): Notify Target (internal) of suggested articles (with above placeholders)
- Result: Target receives list of suggested articles.
Questions:
- Are there runtime issues that cause the first scenario?
- If the 2nd scenario is the correct way to go, then can you confirm that the suggested list in Trigger 2 is always the same as the list suggested in Trigger 1, i.e. will the placeholder always only return analysed results of the first comment sent by the requester, or will it now (in Trigger 2) also analyse all text in all preceding comments (this would include the links and information added to comments in Trigger 1) in previous trigger cycles?
Afficher le commentaire · Publication le 08 juin 2021 · Support Department
0
Abonnés
0
Votes
0
Commentaire
Support Department a ajouté un commentaire,
It's working! Thanks a lot!
Afficher le commentaire · Publication le 11 juin 2020 · Support Department
0
Abonnés
0
Votes
0
Commentaire
Support Department a ajouté un commentaire,
This sounds way better than closing a ticket.
However, I'm not getting it work. What do I have to set as attribute to get a Private (internal) comment?
Afficher le commentaire · Publication le 11 juin 2020 · Support Department
0
Abonnés
0
Votes
0
Commentaire