> 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/change-in-behaviour-automated-ticket-acknowledgement.md).

# CHANGE IN BEHAVIOUR - automated Ticket acknowledgement

{% hint style="warning" %}
We've made a change in Ticket settings which you need to be aware of, relating to the sending out of automated emails. This affects the default behaviour of the Ticket:
{% endhint %}

Previously the system defaulted to sending out automated emails. If you wanted to stop this on a specific ticket, you would need to set the 'Disable Automated Emails' setting to ON.

Now, the default behaviour has switched - the system will NOT send out automated emails from Tickets as a default. **IF YOU DO WISH AUTOMATED EMAILS TO BE SENT OUT FROM A TICKET, YOU WILL NOW NEED TO SET THE (RENAMED) 'SEND AUTOMATED EMAILS' SETTING TO ‘ON’.**

![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FAa1F96GSEyxOFVESFmUY%2Fimage.png?alt=media\&token=967db05d-0cc8-485a-b30f-7393955a670b)

This change in behaviour has also been made on the screen used for creating a new linked Ticket.

![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FJV3TU43RueCQ2mP1cf6S%2Fimage.png?alt=media\&token=abaebc38-2216-4b66-8ea9-afb883bb09bf)

Additionally, when you now launch a Ticket from the Contact Activity page, the 'Send Automated Emails' option will now be defaulted to off, but you can manually switch it on in the Ticket screen. 

This behaviour change has also been applied in the Email section of Builder - when setting up an Email Route, the option controlling sending of Automated Emails has now been changed - default behaviour is to NOT send such automated mails, so if you wish automated emails to be sent you will need to set the 'Send Automated Emails' setting to ON.

![](https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FvQdftWvT69BcfjyqvHxC%2Fimage.png?alt=media\&token=0fdd0027-5fac-42f0-b9af-9d6e9c713a4f)


---

# 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/change-in-behaviour-automated-ticket-acknowledgement.md?ask=<question>&goal=<user_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.