> For the complete documentation index, see [llms.txt](https://doc.appflow.ai/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.appflow.ai/docs/subscription-analytics/in-app-messages.md).
# In-app Messages
Engage with your users with in-app message using only a remote configuration control
***
In-app messages are created to help you engage with your users even more. Imagine, you want to show a big message, not only [push notification](/docs/subscription-analytics/push-notifications.md).
The greatest advantage of this feature is that you can:
* show it exactly after triggering the event, i.e. refund OR
* schedule one event, i.e. congratulate your user with the holiday OR
* make a recurring campaign, i.e. remind your users to drink water every day.
One more advantage of using it with Appflow\.ai is that you can choose the exact users' segment to send your in-app message. For example, it could be released only for some language groups.
And the coolest thing is, as always, that you don't need your mobile developer to be involved as well as update the app version in the store. Everything is done with the Remote Configuration Control!
---
# 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://doc.appflow.ai/docs/subscription-analytics/in-app-messages.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.
