> 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/show-replies-list.md).

# Show Replies List

Show the Luciq replies page on demand in your iOS app, and check whether the current user already has chats before you present the page.

### Show Replies

The below API can be used to display the replies page. This page contains a list of any previous chats that were opened for this customer.

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

```swift
Replies.show()
```

{% endcode %}
{% endtab %}

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

```objectivec
[LCQReplies show];
```

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

### Check if User Has Chats

If a user has no pre-existing chats, the previous API won't show the replies page. You can check whether the user has any available chats or not using the below API.

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

```swift
Replies.hasChats()
```

{% endcode %}
{% endtab %}

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

```objectivec
[LCQReplies hasChats];
```

{% 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/show-replies-list.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.