> 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/custom-settings/sdk-customization/prompt-options.md).

# Prompt Options

By default, when the Luciq SDK is shown, a popup appears to your app users with options for them to report a bug ("Report a bug"), share feedback ("Suggest an improvement"), or ask you a question ("Ask a question"). This popup is called the Prompt Options.

All Luciq popups follow the color theme and primary color that you set for the SDK.

<figure><img src="/files/YAbUmHnb1fE82rfHcbdR" alt=""><figcaption><p><br><em>An example of the Prompt Options menu that appears to app users after Luciq is invoked.</em></p></figcaption></figure>

By default, all of your enabled products are listed in the Prompt Options menu. You can control which options appear by disabling and enabling any of the products. Each one can be enabled or disabled separately.

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

```swift
// Disable the Bugs, Feedback, & Questions. If disabled, "Report a problem" "Suggest an improvement" & "Ask a Question" are removed from the Luciq's prompt, and manually showing the bug reporting or feedback doesn't have an effect.
BugReporting.enabled = false

// Specify which of the feedback, bug, or question options appear in the prompt options
BugReporting.promptOptionsEnabledReportTypes = [.bug, .feedback, .question]

// Disable the Replies. If disabled, the chats list button is removed from Luciq's prompt, the in-app notifications are disabled, and manually showing the chats list doesn't have an effect. 
Replies.enabled = false
```

{% endcode %}
{% endtab %}

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

```objectivec
// Disable the Bugs & Feedback. If disabled, "Report a problem" "Suggest an improvement" & "Ask a Question" are removed from the Luciq's prompt, and manually showing the bug reporting or feedback doesn't have an effect.
LCQBugReporting.enabled = NO;

// Specify which of the feedback or bug options appear in the prompt options
LCQBugReporting.promptOptionsEnabledReportTypes = LCQBugReportingReportTypeBug | LCQBugReportingReportTypeFeedback | LCQBugReportingReportTypeQuestion;

// Disable the Replies. If disabled, the chats list button is removed from Luciq's prompt, the in-app notifications are disabled, and manually showing the chats list doesn't have an effect. 
LCQReplies.enabled = NO;
```

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

When only a single option is enabled, it becomes the default invocation mode. If all options are disabled, bug reporting becomes the default invocation mode and the Prompt Options menu won't appear to your users. Instead, they will be shown the bug reporting form.

By default, all three options are enabled if they are available in your current plan.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.luciq.ai/ios/setup-luciq-for-ios/custom-settings/sdk-customization/prompt-options.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.