# Page Not Found

The URL `support/solutions/articles/72000576097-send-a-message-to-guests` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [Send a Message to Guests](https://support.evite.com/products/invitations/manage-and-edit-guest-list/send-a-message-to-guests.md)
- [Message Guests](https://support.evite.com/products/invitations/mobile-apps/android-app/message-guests.md)
- [Send Message](https://support.evite.com/products/invitations/mobile-apps/ios-app/send-message.md)
- [Guest - Edit Name on Guest List](https://support.evite.com/products/invitations/manage-and-edit-guest-list/guest-edit-name-on-guest-list.md)
- [How to Send Evite SignUp Sheets](https://support.evite.com/products/signup-sheets/organizer/how-to-send-evite-signup-sheets.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://support.evite.com/products/invitations/manage-and-edit-guest-list/send-a-message-to-guests.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://support.evite.com/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://support.evite.com/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/products/invitations/manage-and-edit-guest-list/send-a-message-to-guests.md`).

You may also use `Accept: text/markdown` header for content negotiation.