Add the ticketowner email in an embedded data and try to pipe that in an email task.
You need to set up separate workflows to assign to specific users rather than a group. You can either create in the survey workflows or set up workflows in ticketing when the ticket is an hour old. Survey workflows are a little more user-friendly but any changes to tickets need to be done to each workflow. Ticket workflows mean you’ll need to wait until the ticket is an hour old, which depending on your use case may not work for you.
You need to set up separate workflows to assign to specific users rather than a group. You can either create in the survey workflows or set up workflows in ticketing when the ticket is an hour old. Survey workflows are a little more user-friendly but any changes to tickets need to be done to each workflow. Ticket workflows mean you’ll need to wait until the ticket is an hour old, which depending on your use case may not work for you.
Hi @EmilyErickson … thankyou for your response
As per the qualtrics support they suggested me to go through the approach similar to what @Deepak suggested…
Add the ticketowner email in an embedded data and try to pipe that in an email task.
Hi @Deepak thankyou for your response
we are not populating email ID in the source file itself
hence we are not able to map it directly
qualtrics support has suggested to map the ticket owner with the username and let qualtrics to fetch the email id from the admin data present that will trigger an email to user but seems not to be working as per the requirement as it is more of a static approach and getting a reminder in the notification panel for the ticket but still no email could be seen triggered to the person
can you please suggest any better alternative or alternation in the above approach ?
thanks again! :)
Hi @krbhavya Somewhat related to what I’m pointing to actually
Could you please help to suggest a little more in detail