> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/kmp/setup-luciq-for-kmp/setup-in-app-replies/managing-notifications.md).

# Managing Notifications

Control in-app reply notifications in your KMP app, plus Android notification sound, FCM token registration, and showing a reply from a push payload.

### In-app notifications

Enable or disable in-app notifications when a new reply arrives:

{% code title="Kotlin" %}

```kotlin
RepliesKmp.setInAppNotificationsEnabled(true)
```

{% endcode %}

### In-app notification sound (Android)

On Android, enable or disable sound for in-app reply notifications:

{% code title="Kotlin" %}

```kotlin
RepliesKmp.setInAppNotificationSound(true)
```

{% endcode %}

No-op on iOS.

### Push notifications (Android)

**Registration token**

Set the FCM token so the backend can send push notifications for new replies:

{% code title="Kotlin" %}

```kotlin
RepliesKmp.setPushNotificationRegistrationToken(fcmToken)
```

{% endcode %}

**Showing a notification from payload**

When you receive a push payload for a reply, pass it to the SDK to show the notification:

{% code title="Kotlin" %}

```kotlin
RepliesKmp.showNotification(data)  // data: Map<String, String>
```

{% endcode %}

**Notification icon and channel**

{% code title="Kotlin" %}

```kotlin
RepliesKmp.setNotificationIcon(R.drawable.ic_notification)
RepliesKmp.setPushNotificationChannelId("luciq_replies")
RepliesKmp.setSystemReplyNotificationSoundEnabled(true)
```

{% endcode %}

All of the above are Android-only; they are no-ops on iOS.


---

# 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.luciq.ai/kmp/setup-luciq-for-kmp/setup-in-app-replies/managing-notifications.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.