最近搜索
没有最近搜索

Support Department
已加入2021年4月15日
·
最后活动2024年10月14日
关注
0
关注者
0
活动总数
38
投票
15
订阅
14
活动概览
标记
文章
帖子
社区评论
文章评论
活动概览
的最新活动 Support Department
Support Department 进行了评论,
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.
查看评论 · 已于 2023年8月09日 发布 · Support Department
0
关注者
0
投票
0
评论
Support Department 创建了一个帖子,
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.
已于 2023年8月08日 发布 · Support Department
0
关注者
2
投票
6
评论
Support Department 进行了评论,
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)?
查看评论 · 已于 2021年7月28日 发布 · Support Department
0
关注者
0
投票
0
评论
Support Department 进行了评论,
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?
查看评论 · 已于 2021年7月15日 发布 · Support Department
0
关注者
0
投票
0
评论
Support Department 进行了评论,
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?
查看评论 · 已于 2021年6月08日 发布 · Support Department
0
关注者
0
投票
0
评论