• Customer Experience
    Customer Experience
  • Employee Experience
    Employee Experience
  • Brand Experience
    Brand Experience
  • Product Experience
    Product Experience
  • Core XM
    Core XM
  • Design XM
    Design XM

Ticket Events

What's on This Page:

Was this helpful?


This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

The feedback you submit here is used only to help improve this page.

That’s great! Thank you for your feedback!

Thank you for your feedback!

About Ticket Events

Have you ever wished you could get an email when someone makes a sub-ticket on one of your tickets? Maybe you want your colleagues to receive an email if you change the priority of their ticket to high. Or maybe you want to know right away if a ticket’s been deleted.

Ticket Events allow you to set different tasks into motion (such as emails, Salesforce triggers, or Slack messages) when something happens to a ticket in Qualtrics.

the ticket event in the task selection window

Qtip: This feature is not currently available to everyone. If you do not have access to this feature and are interested in learning more, reach out to your Customer Success Representative or your Account Executive.

Types of Ticket Events

The following can be used to define a Ticket Event:

the types of ticket events

  • Comment added: Someone added a comment to a ticket.
  • Status changed: Someone changed the status of a ticket.
  • Priority changed: Someone changed the priority of the ticket.
  • Ticket teassigned: The ticket owner was changed to someone else.
  • Sub-ticket created: A sub-ticket was created for the ticket.
  • Sub-ticket deleted: A sub-ticket was deleted.
  • Ticket deleted: A ticket was deleted.
  • Root cause changed: Someone changed the root cause they initially picked for the ticket.
  • Email sent: An email was sent from the ticket using the Send Email button.
  • Email received: There was a response to an email sent through the ticket.
  • Follow-up details changed: Any information changed in a follow-up detail (additional questions on the ticket).
  • Assigned from queue: Someone picked up a ticket from a ticketing queue they belong to.
  • Ticket name changed: The ticket’s name was edited.
  • Ticket data changed: Ticket data was edited.
Qtip: You can select multiple types of Ticket event at once!

Setting Up a Ticket Event

  1. In the Actions section, click Create an Action.
    creating an event-based action
  2. Select Event-based.
  3. Choose the Ticket Event.
    choosing the ticket event in the event window
  4. Choose the types of ticket events that trigger the action. You may select multiple events.
    choosing the ticket event type and clicking finish
  5. Click Finish.
  6. Click the plus sign (+) and choose to add Conditions and a Task to your action. Conditions determine when your action fires, and the task determines what happens as a result of your action.
    choosing to add conditions and a task to the action

    Qtip: It is highly advised you add conditions. Check out the setting conditions for a ticket event section for more details.
    Qtip: Visit this page for an explanation of every available task

Setting Conditions for a Ticket Event

Conditional statements apply All or Any to drive filtering criteria. In All conditions, every condition listed below must be met. It is similar to joining statements by “and.” In Any conditions, any of the conditions can be met, but not all have to be. It is similar to joining statements by “or.”

Example: In this example, only one of the two conditions has to be met for the action to the triggered.

a condition for when the ticket priority is high and the status is open

The conditions you set for a ticket event can be based off of various ticketing features and actions.

Attention: If your survey has multiple ticket tasks, the condition editor will not be able to differentiate between tickets created by each task. Conditions created here will apply to all tickets for your survey that fit the selected ticket event types.
  • Priority: The priority of the ticket.
  • Owner: The person who owns the ticket.
  • Status: The status of a ticket.
  • Team: The team that owns the ticket.
  • Root Cause: The root cause assigned to a ticket. This will be empty if a root cause wasn’t set when creating the original ticket task.
Qtip: If you don’t set conditions for a Ticket Event, the task will be triggered every time the event happens to a ticket from the same survey. You do not have to worry about triggering an action every time it happens in the organization.
Example: You have a CSAT survey for 2018. You create an action and set your Ticket Event to Priority Changed. This action has an Email Task attached, however, you forgot to add a condition. Every time someone changes the priority on a ticket from the 2018 CSAT survey, you get an email. But priority changes to 2017 CSAT tickets do not affect you.