> For the complete documentation index, see [llms.txt](https://readme.dhee.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://readme.dhee.ai/getting-started/train-your-bot/configure-workflow/acknowledge-user.md).

# Acknowledge User

### Notify User

Once we have recorded the information (leave details), we need to notify the user that he has successfully applied for leave. The *Speak* action could be used for this purpose. The *Speak* action accepts a single parameter, the name of the previously added *Agent Response*.

![Speak Action](/files/SN8hsXYHCWKkNi9H7X3F)

In this case, we will add the previously added Agent Response, which we had named *leaveRegisteredMLT*.

### Stop

The final action, as mentioned earlier is to indicate the workflow is completed. This is done using the *Exit* action.

![Exit Action](/files/Gm9qtBagQa3LxCKA5RCm)

&#x20;The complete workflow at this point looks like the following.

![Complete workflow for no-code approach](/files/SdL6mAFlkvNF6URpFIsR)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://readme.dhee.ai/getting-started/train-your-bot/configure-workflow/acknowledge-user.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
