One thing you could consider doing would be for your CS reps to tag the ticket with a custom property, like "Exclude CES" and choices "yes" or "no" which would allow them to mark the tickets that shouldn't get the survey.
Then you can create a second pipeline as a home for these closed tickets, you'd only need one stage.
With these two items in place, you then create a workflow that says if "CES Exclude" = Yes, move to new pipeline and stage = closed.
For these tickets, it should be their last step - so instead of moving to closed, this would be the step they complete to close out the ticket.
Effectively this closes the ticket and moves it out of the pipeline that gets the CES survey.
You would have to update any reporting, etc. to include these tickets in your data/dashboards.
If my reply answered your question please mark it as a solution to make it easier for others to find.
One thing you could consider doing would be for your CS reps to tag the ticket with a custom property, like "Exclude CES" and choices "yes" or "no" which would allow them to mark the tickets that shouldn't get the survey.
Then you can create a second pipeline as a home for these closed tickets, you'd only need one stage.
With these two items in place, you then create a workflow that says if "CES Exclude" = Yes, move to new pipeline and stage = closed.
For these tickets, it should be their last step - so instead of moving to closed, this would be the step they complete to close out the ticket.
Effectively this closes the ticket and moves it out of the pipeline that gets the CES survey.
You would have to update any reporting, etc. to include these tickets in your data/dashboards.
If my reply answered your question please mark it as a solution to make it easier for others to find.
Any input from the experts? 😊 We have the same issue, where our support team is fielding tickets from both customers and partners/suppliers, and we need to be able to exclude partners/suppliers from receiving the CES survey.