> For the complete documentation index, see [llms.txt](https://xoops.gitbook.io/contact-tutorial/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://xoops.gitbook.io/contact-tutorial/waiting-module-support.md).

# Waiting Module Support

The Contact module includes native support for the Waiting module v0.97+. This support is enabled automatically and the Contact module will show up in the Waiting block: 

![Module Waiting](/files/-LD6N22bemEoLcho_x90)

The Waiting module is available through XOOPS at <http://www.xoops.org>.

**Note:** *The Waiting module is not the same as the XOOPS native (core) “Waiting Contents” block. The XOOPS core “Waiting Contents” block is not extensible and so contents from the Contact module will not be visible in this block.*

The Contact module supplies information on messages which do not have a reply so site administrators can address any messages needing attention.


---

# 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://xoops.gitbook.io/contact-tutorial/waiting-module-support.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.