> 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/ios/setup-luciq-for-ios/setup-in-app-replies/disabling-enabling-in-app-replies.md).

# Disabling/Enabling In-App Replies

Hide the replies page from the Luciq prompt in your iOS app, or bring it back, controlling whether users can browse their chat history with you.

When the Luciq SDK is invoked, a popup appears to your app users with default [Prompt Options](/ios/setup-luciq-for-ios/custom-settings/sdk-customization/prompt-options.md) for them to "Report a problem" (send you a bug report), "Suggest an improvement" (send you feedback), or "Ask a Question" (send you a question). There is also an option to view the chat history, or replies, page.

The API below can be used to hide the replies page from the user as well as disable it. The button in the prompt options will no longer be visible if this API is used. The in-app notifications will also be disabled, and manually showing the chats list won't have an effect.

{% tabs %}
{% tab title="Swift" %}
{% code overflow="wrap" %}

```swift
Replies.enabled = false
```

{% endcode %}
{% endtab %}

{% tab title="Objective-C" %}
{% code overflow="wrap" %}

```objectivec
LCQReplies.enabled = NO;
```

{% endcode %}
{% endtab %}
{% endtabs %}


---

# 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/ios/setup-luciq-for-ios/setup-in-app-replies/disabling-enabling-in-app-replies.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.