Has anyone found, or do you know of, a definitive guide for properly making Zendesk Support work with the SMS components of Talk?
Specifically:
- SOLVED: Proper Triggers rules to ensure that replies to inbound SMS messages are replied to as SMS.
- SOLVED: How to configure an agent signature to ensure that it isn't used in responses to any SMS communications; using ticket tags and liquid markup in the account-wide signature to create some cases that define the signature contents.
Where I was stuck:
1) Updates to tickets not being SMS'd to customer:
When i've created a ticket where I've specified the requester by entering their phone number into the Requester field, the first message has gone without problem.
As discussed later in this post, removing one of the channel actions gets it done.
Will update all the screenshots for my trigger recipes to show how this is done.
2) Preventing signature being included in SMS
This is solved by the use of tagging the ticket with certain tags, AND using liquid markup in the signature.
In short, I've used liquid markup to look for three tags in a ticket. If anyone of these three tags occurs, it creates a case statement which has no content. And then there's the else result where none of these tags appear.
Code to achieve this:
--------
{% assign tags = ticket.tags | split: " " %}{% for tag in tags %}{% case tag %}
{% when 'sms-outbound' %}
{% when 'sms-apioutbound' %}
{% when 'sms-inbound' %}
{% else %}
Kind regards,
{{agent.name}}
Customer Service Team
Your Company Name
{% endcase %}{% endfor %}
--------
Original public response, which correctly triggered outbound SMS

Follow-up public response which triggered no action at all

Trigger to cause outbound SMS on new ticket


Trigger that is supposed to cause outbound SMS on an update to a ticket, but isn't


Hey Michael,
When you're updating the ticket are you doing so from the Agent Interface? If so, could you remove the Update > via > Text condition to see if the trigger fires appropriately? It may be worth removing the Channel > is > Text as well since the trigger should only fire if it contains one of those tags.
Let me know if you continue to experience any issues.
Thanks!