{"id":20728,"date":"2023-08-24T09:19:41","date_gmt":"2023-08-24T09:19:41","guid":{"rendered":"https:\/\/help.kanidesk.com\/en\/docs\/automations\/configuring-workflow-rules\/automation-rule-ticket-requester-in-email-contact\/"},"modified":"2026-04-25T10:52:21","modified_gmt":"2026-04-25T10:52:21","slug":"automation-rule-ticket-requester-in-email-contact","status":"publish","type":"docs","link":"https:\/\/help.desk365.io\/en\/articles\/ticket-requester-in-send-email\/","title":{"rendered":"Automation rule: Ticket requester in send email"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t
\n Available with:<\/span>\n \n \n \n <\/circle>\n <\/path>\n <\/svg>\n Standard<\/span>\n <\/span>\n \n |<\/span>\n \n \n \n <\/circle>\n <\/path>\n <\/svg>\n Plus<\/span>\n <\/span>\n \n |<\/span>\n \n \n \n <\/circle>\n <\/path>\n <\/svg>\n Premium<\/span>\n <\/span>\n<\/div>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

We have made significant enhancement in our automation rules, introducing the feature of ‘Ticket Requester’ in ‘Send Email’. This enhancement marks a pivotal step in customizing and automating communication, allowing businesses to reach out to ticket requesters effortlessly.<\/p>

This innovative feature empowers you to not only communicate with specific contacts based on automation triggers but also to directly connect with the ticket requester.<\/p>

By selecting the \u2018Ticket Requester\u2019 option, you can now achieve this. Desk365<\/a><\/span> will then automatically email the Ticket Requester with the email you\u2019ve set up.<\/p>

With this enhancement, you can now email the requester of a ticket (the Contact who created the ticket) based on an automation rule getting triggered. This means that you can easily send targeted and personalized emails to your customers, without having to manually search for their contact information.<\/p>

Here’s how it works:<\/p>

First, you need to set up an automation rule that will trigger an email to be sent. This could be based on a variety of criteria, such as the status of the ticket, the type of issue, or the customer’s location.<\/p>

Next, when setting up the ‘Send Email’ for the automation rule, you can select ‘Ticket Requester’ as the recipient. This will automatically send the email to the customer who created the ticket, using the email address associated with their account.<\/p>

In addition, you have the\u00a0<\/span>option<\/span>\u00a0to include any CC recipients added during ticket crea<\/span>t<\/span>ion, so everyone originally looped into the conversation continues to stay informed.<\/span><\/span>\u00a0<\/span><\/p>

Finally, you can customize the email content to ensure that it is relevant and helpful to the customer. This could include information about the status of their ticket, suggestions for resolving the issue, or links to relevant resources. You can also attach files that were uploaded when the ticket was created or add custom attachments to the email. This ensures that all relevant information is shared with the ticket requester automatically.<\/span><\/span>\u00a0<\/span><\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\"send-email-automation-rule\"\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

By using the ‘Ticket Requester in Send Email’, you can streamline your customer support operations and provide a more personalized experience for your customers. This can help to improve customer satisfaction, reduce response times, and increase overall efficiency.<\/p>\n

By seamlessly integrating automation into the communication process, businesses can nurture relationships, resolve issues promptly, and build a loyal customer base.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"author":5,"featured_media":0,"parent":18821,"menu_order":10,"comment_status":"open","ping_status":"closed","template":"","doc_tag":[],"class_list":["post-20728","docs","type-docs","status-publish","hentry","no-post-thumbnail"],"comment_count":0,"_links":{"self":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/20728","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/comments?post=20728"}],"version-history":[{"count":60,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/20728\/revisions"}],"predecessor-version":[{"id":36537,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/20728\/revisions\/36537"}],"up":[{"embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/18821"}],"next":[{"title":"NULL checks in automation rules","link":"https:\/\/help.desk365.io\/en\/articles\/null-checks-in-automation-rules\/","href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/20738"}],"prev":[{"title":"Using replied content placeholders in automation rules","link":"https:\/\/help.desk365.io\/en\/articles\/using-replied-content-placeholders-in-automation-rules\/","href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/docs\/23707"}],"wp:attachment":[{"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/media?parent=20728"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/help.desk365.io\/en\/wp-json\/wp\/v2\/doc_tag?post=20728"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}