Automating SMS support with Text triggers (Talk Team, Professional, and Enterprise)

Important: You are responsible for using the call and text features in Zendesk Talk in compliance with all applicable laws. Zendesk does not control the content of your telephonic communications, when they are made, or the recipients of the communications. Certain jurisdictions may require end-user consent prior to initiating telephonic outreach. By enabling these features, you agree that you have received the required consent.

Just like with tickets from other Zendesk channels, you can set up triggers to manage your Text tickets. In addition to the actions and conditions available for all tickets, there are a few Text-specific options you can use. For step-by-step instructions and ideas, see Sending outbound texts: Recipes and tips.

Warning: If your Zendesk account has a high ticket turnover and you are using text triggers, this will generate a high number of outgoing text messages. When a high number of text messages are sent from the same number, they might be marked as spam by the mobile networks. Before you configure text triggers, consider if this is the right solution for you.

• The Ticket: Channel condition with value SMS
• Two actions that send Text notifications:
  • Notifications: Text group. Select a group to send a Text notification to from the drop-down list of groups in your account.

    

  • Notifications: Text user. Select (current user), (requester), (assignee), or a specific user from the drop-down menu.

    

    • In the From field, select the SMS number to send the message from.

      

    • Enter the SMS message to send in the Body field.

Keep in mind the following when using triggers to send Text messages:

• Keep the body text short, or it might be broken into multiple messages. Remember that placeholders will be expanded.
• You'll be limited to approximately 250 notifications a day before a carrier's spam detectors might blacklist your number, so avoid using these for mass outbound notifications.
• The end-user's phone number should be set as their direct line (see Identifying the caller and handling new user accounts). If this isn't set, a new user will be created when the end-user replies.
• We will capture replies to these notifications as tickets for processing by agents.
• You don't need to set up a trigger to send updates to requesters when updates to a ticket are made. This is built into Text and happens automatically.

For general information about setting up triggers, see the following articles:

• About triggers and how they work
• Creating and managing triggers
• Triggers resources

Understanding responses to notifications

Responses to notifications are placed into a Text ticket, like other inbound Text messages. If the end-user's number doesn't currently have an open ticket, a new ticket is created. If the end-user's number does already have an open ticket, the response is added to that existing ticket.

When the last message sent to a customer in a ticket is a Text notification, the notification appears in the ticket as a private comment. This way, agents addressing the ticket can get the appropriate context from the Text conversation.