Placeholder Format for Dropdown Fields in Zendesk
What is the correct placeholder format for dropdown fields in Zendesk email notifications?
For dropdown fields in Zendesk email notifications, use the placeholder format{{ticket.ticket_field_option_title_<field ID number>}}. This format will display the customer-facing text or label associated with the dropdown field option.
If you use the placeholder{{ticket.ticket_field_<field ID number>}}, it will display the tag associated with the field option instead. This distinction is important for ensuring the correct information is shown in your email notifications.
More related questions
How can I add custom ticket field values to email notifications in Zendesk?
You can add custom ticket field values to email notifications by using placeholders. To do this, first, open the Admin Center and navigate to Objects and rules > Tickets > Fields. Locate your custom ticket field and copy the Field ID number. Then,…
Can I use placeholders for checkbox values in Zendesk email notifications?
Yes, you can use placeholders for checkbox values in Zendesk email notifications. The placeholder format for a custom checkbox field is{{ticket.ticket_field_id}}. This will display the value associated with the checkbox in the notification….
Is it possible to increment a custom number field in a Zendesk trigger action?
Yes, you can use custom number fields in Zendesk trigger conditions and actions. However, the help documentation does not provide specific details on incrementing these fields directly within a trigger action. For more complex operations like…
Can I update ticket comments using Zendesk triggers?
No, Zendesk triggers do not have the capability to update or create comments on a ticket directly. Triggers are designed to send notifications or perform actions based on ticket events, but they cannot modify ticket comments. However, there are…
Interested indeflectingover 70% of your Zendesk support tickets?
Zendesk Support Tickets
Zendesk Messaging (live chat)
Join1,000+ companies reducing their support costs and freeing up support agents for more important work
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
“We needed an AI agent integrated within our current tools. My AskAI was the only solution that wasn't going to disrupt our operations.”
Zeffy
“At the end of last year I was given the challenge - how can we provide the same or better service, without hiring anyone?”
Zinc
“My AskAI blew everybody else out of the water. It made the selection process very easy for us.”
Customer.io($50M+ ARR)
“It now resolves 71% of queries (over 35,000 every month), meaning more time solving complex issues and improving UX.”
Freecash
Reduce support costs.Spend more time on customer success.
