# Patient chat

Patient chat lets a **Growth** (or Enterprise / eligible trial) practice exchange messages with a patient who has **linked** the Associhealth **patient mobile app**. The same capability is available from the sidebar [**Chats**](/associhealth-docs/practice-setup/chats.md) hub or from a patient profile—see below.

## Requirements

* Your practice must be on **Growth**, **Enterprise**, or an active Growth-level trial.
* The patient must be linked to the mobile app from their patient profile invite section.
* The patient must remain assigned to a branch your practice can access.

## Where to message from the web app

* **Chats** (main navigation) — branch-scoped list of all linked-patient threads; see [Chats (Growth)](/associhealth-docs/practice-setup/chats.md).
* **Patients →** open a patient **→ Patient chat** on the profile — same conversation as Chats for that patient.

Messages appear in the patient mobile app under **Chats**. Replies sync to the web; new messages usually show up without a full page reload.

## Patient app

Patients use **Chats** on mobile to read and reply. **Online / Away** for your clinic reflects recent use of the practice web app for that branch (approximate). The practice sees **Online / Away** for the patient based on recent patient app activity—see [Chats (Growth)](/associhealth-docs/practice-setup/chats.md#presence-from-the-patients-perspective).

## Notes

Patient chat is for lightweight coordination such as appointment questions and record follow-ups. Keep clinical decisions and formal treatment documentation in the patient record, treatment records, attachments, and informed consent flows.


---

# Agent Instructions: 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:

```
GET https://associhealth.gitbook.io/associhealth-docs/patients/patient-chat.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.

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.