> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.4-changes-overview/send-automated-emails-for-cases.md). # Send Automated Emails for Cases We've added the ability to send automated emails for Cases. At the moment, the only automated email available to send for cases is a Case creation acknowledgement email. To enable this, in the Email Route section of Builder set the 'Send Automated Emails' option to ON when configuring or editing an email route for a Case. ![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2Fypt5BRJHlTVlcMLOktfE%2Fimage.png?alt=media\&token=e68c30ad-0e03-4a0e-ba24-55861d8167bd) #### Acknowledgement Email Template - Important Note As part of this change to support automated Acknowledgement emails being sent out from Cases, the existing 'Ticket Acknowledgement' email template has been modified to also support Case acknowledgements. The following changes have been made to the template as part of this: * The template name and purpose has been changed from 'Ticket Acknowledgement' to 'Request Acknowledgement. * Within the email body content, the term 'Ticket' has been renamed to 'Request' in order to support both Cases and Tickets with the one template. {% hint style="warning" %} IMPORTANT NOTE: The above changes to the Ticket Acknowledgement template will NOT be made to your system if you have manually adjusted its content from the original default content (i.e. to contain your bespoke content). However, you should be aware that this template will still be used as the default email template for Case acknowledgements. Therefore, if you have modified the content of your Ticket Acknowledgement template **it is highly recommended that you review the content to ensure this would be appropriate for Cases as well as Tickets**, and make adjustments accordingly (e.g. altering the content or creating an equivalent dedicated Case-specific template to use for your Cases. {% endhint %} ![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FuEk03ytsEcjBQPLOBgfk%2Fimage.png?alt=media\&token=8d7ae69b-5998-4811-b667-709a7841bafe) Additionally a new option has been added in the Case info screen under Email Settings called 'New Case Logged' where you can select the Email Template you want to use to acknowledge that a Case has been created. The system will automatically select the new 'Request Acknowledgement' email template (or the existing 'Ticket acknowledgement' email template if it has been edited). You are able to choose a different template to use. Note that this field cannot be left blank. ![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2F6kSZ1ZE6qpFka0ahFFMO%2Fimage.png?alt=media\&token=5eced2e6-399a-4425-97c1-b6326a773d22) Furthermore, note that the new setting 'Send Automated Emails' in the Case Screen in Work Manager needs to be set to on by Service Agents in order for the system to send the automated Case acknowledgement email to the primary contact and CC contact(s) when the Case gets submitted i.e. when it has moved from Draft into a To Do state or further. ![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FUyuSyYKXbKKOJRw6oKqB%2Fimage.png?alt=media\&token=545f92d0-b60a-4238-aa48-63912f6180c0) Note also that the automated email that will be sent when a Ticket is converted into a Case will still be the 'Ticket Launched Case' email template, not the 'Request acknowledgement' email template. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.4-changes-overview/send-automated-emails-for-cases.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.