> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/faq/faq-about-the-application-app/untitled-1.md).

# Communication (App)

## Do I have to be connected to other users to be able to message them? <a href="#do-i-have-to-be-connected-to-other-users-to-be-able-to-message-them" id="do-i-have-to-be-connected-to-other-users-to-be-able-to-message-them"></a>

No you don't, anyone is able to start a chat and send a message to anyone else regardless of whether you are or aren't connected.

## What's the difference between a chat, a message, and a push notification? <a href="#whats-the-difference-between-a-chat-a-message-and-a-push-notification" id="whats-the-difference-between-a-chat-a-message-and-a-push-notification"></a>

**Chat:** These are messages between two attendee's/users. \
**Message:** A message is sent from an organiser directly to an individual user or users. \
**Push notifications:** A [push notification](https://knowledge-base.letsgetdigital.com/the-admin-panel/communication/application/push-notifications) appears like any other notification from an app (Such as a news, gaming, or social media application). It can be from the organiser to notify/remind you of something, or generated by the app to let you know of something happening inside the application, such as a received message or request for feedback.

**​**


---

# 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://knowledge-base.letsgetdigital.com/faq/faq-about-the-application-app/untitled-1.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.