From the contact form and article suggestions, customers are able to solve their own tickets. This article provides steps to prevent end users from closing their tickets.
This workflow includes the options below.
Option 1: Create a trigger to automatically reopen tickets
You can create a trigger and automatically re-open tickets solved by your end users.
- In Admin Center, click
Objects and rules in the side bar > then select Triggers
- Click Create trigger
- Name your trigger > add a Category
- Under Conditions, add these options:
- Status > Status category | Changed to | Solved
-
Ticket details > Current user | Is | (end-user)
- Below Actions, select:
- Ticket > Status category | Open
- Click Save
Option 2: Remove article suggestions
Another option is to remove article suggestions from your help center.
- In Admin Center, click
Channels in the sidebar, then select Bots and automations > Bots
- Click Manage autoreplies
- Click the Web form tab
- Toggle off Web form channel enabled
For more information, see this article: Using autoreplies to recommend articles in web forms.
3 comments
Nichole Endline
Hello!
We were also having some operational struggles as a result of customers using the ‘mark as solved’ button (primarily due to our desire to include solution notes in tickets before setting to ‘solved'). When we implemented something similar to what you describe above, we got negative feedback from customers, because the trigger design gave the appearance to customers as if the ‘mark as solved’ button did not work. Given the frustration it generated, we abandoned this approach quite quickly.
So, we changed course: instead of preventing the action from happening, we designed triggers to detect when it DID happen. By doing this, we avoided creating any frustration and were able to add a special tag to have these tickets filter into a specific view. From this view, our engineers/managers were able to review tickets marked as solved by customers and add a solution note before the status moved to a ‘closed’ , uneditable state. We also had the added bonus of improved reporting about customers marking their tickets as solved since we were proactively identifying them via this new flow.
Food for thought :)
1
Adam Vorisek
+1 to Nichole's comment. It would be greatly preferable to be able to remove the button for customers rather than have a button that essentially doesn't work. It's great when customers can mark their tickets as solved based on suggestions, but it is detrimental when customers mark ongoing tickets as solved when they are logged into Zendesk. Removing that option to solve tickets when customers are logged into Zendesk would be greatly preferable to having triggers in place to either nullify it or letting us know when it happens.
0
Dorte Engelund Thybring
Is there no way of changing the look or text on the buttons?
As other users comments, none of the suggested solutions would work for us, but users misunderstand the buttons and end up closing their tickets by mistake. If we could go into the code of the Guide module and change the buttons, then it would be really useful.
1