> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/care/communication/inbox/inbox-internal-notes.md).
# Internal Notes
Internal Notes allow care team members to leave private messages within a patient conversation in the Inbox. These notes are visible only to users with access to that communication — patients and external parties never see them.
Internal Notes are useful when team members need to share context, flag something for a colleague, or document an observation alongside a patient conversation without it appearing in the patient-facing message history.
***
## Adding an Internal Note
To add an Internal Note, open a conversation in the Inbox and switch the composer to **Add internal note** mode. Type your message and send it. The note is added to the conversation thread immediately.
Internal Notes are visually distinct from outbound messages — they are highlighted in **purple** and clearly labeled, making it easy to distinguish team notes from patient-facing communications at a glance.
***
## Visibility and Privacy
Internal Notes are only visible to users who have access to the communication. Patients, contacts, and any external parties cannot see Internal Notes — they are strictly internal to your care team.
All Internal Notes are saved as part of the conversation history and appear in chronological order alongside other messages in the thread.
***
## Using @Mentions in Internal Notes
Internal Notes support **@mentions**, allowing users to tag a specific colleague within a note. When a user is mentioned, they receive a notification and the conversation appears in their **Mentions** tab. See Inbox: @Mentions for full details.
***
## Related Topics
* [Inbox](/care/communication/inbox.md) — Inbox overview and general usage
* Inbox: @Mentions — tagging colleagues in Internal Notes
---
# 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://docs.welkinhealth.com/care/communication/inbox/inbox-internal-notes.md?ask=&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.
