Feature Request: Side conversation - Automatic assignment of the ticket form from the parent ticket
Posted Oct 04, 2023
In order to improve usability, our employees would like the ticket form to be automatically taken over from the parent ticket when creating a side conversation and not have to be taken over separately with the corresponding function, which is hidden for some users or they don't even know about it.
-
What problem do you see this solving?
Users create side conversations and do not assign the correct form.
This leads to statistics being distorted and not providing correct results.
- When was the last time you were affected by this lack of functionality, or specific tool? What happened? How often does this problem occur and how does this impact your business?
The problem occurs several times a week and requires manual monitoring and revision by the team leader - this is both unnecessary and expensive.
- Are you currently using a workaround to solve this problem?
We have created a dummy ticket form as the first form, which is now automatically assigned by Zendesk when a side conversation is created. Additionally, we have created an extra ticket view for the team leaders that filters for tickets that use this dummy ticket form.
We would like to avoid this workaround.
- What would be your ideal solution to this problem? How would it work or function?
There should be a configuration option to automatically copy the ticket form from the parent ticket when creating a side conversation.
In our scenario, 99% of the time the side conversation uses the same ticket form as the parent ticket.
10
10 comments
Sebastian
+1 for this. I wonder about the many negative votes. Maybe the OP should state in the first sentence to have “the option”.
0
Charles
+1 it would be nice to automatically inherit the form and the fields.
0
Harry Springer
+1 for the parameter "Always include the parent ticket form in child tickets" to be effective by default and for agents to only have an opt-out option. It would be even better if we could set which fields should and should not be copied in the child ticket. That way we can exclude certain fields from being copied.
0
Aaron Doane
+1 on this. In addition to adopting the ticket form, it would be helpful to copy the ticket fields as well. It would be a huge time saver for teams that receive escalations via side conversations and would help escalations be more accurate in the process.
0
Josef Prandstetter
1263082356289
In our use case, it would be desirable - as you have outlined - the parameter ""Always include the parent ticket form in child tickets" to be effective by default and for agents to only have an opt-out option.
1
Toby Sterrett
1264020260110 thanks for the feedback! Are you looking for something like a setting in the side conversations admin center that would toggle something like "Always include the parent ticket form in child tickets" that would automatically tick the existing option on side conversations? Then the agent could uncheck it if necessary. Or, do you not want them to be able to uncheck it?
0
Keti
+1 Thank you for mentioning it 1264020260110
0
Shawna James
For others who may be interested in this feature request, please show your support by upvoting the post or adding your specific use case in the comments. Thank you again for taking the time to provide us with your feedback!
0
Sydney Neubauer
+1 or to even have it required to set a form before SC is created (it shows the forms available to the group or recommends the form). We have triggers set up specifically for SC when a ticket is created but it adds an additional trigger to be created for every group we use
0
Torsten Serfling
+1
Next to the ticket form also the ticket fields (system and custom fields) should be inherited to the ticket created by a side conversion or child ticket creation.
1
Sign in to leave a comment.