> For the complete documentation index, see [llms.txt](https://docs.maker.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maker.co/maker-greatstore/storefront/text-chat.md).

# Text chat

The chat panel a shopper types into: where it sits, the composer, suggested prompts, image search, and the rich results that stream back.

Text chat is the core of the shopper experience, and it's live the moment the widget is installed. A shopper types a question; the assistant searches, reasons, and streams an answer back, often with product cards, comparisons, or a catalogue rendered right in the thread.

## Where the panel sits

* **Desktop**: a side panel. It anchors on the **left** by default and opens expanded; a shopper can flip it to the **right**, and that choice sticks for them next time.
* **Mobile**: a bottom bar that starts collapsed. Sending a message opens the drawer; the assistant stays reachable while the shopper keeps browsing.
* You can also run the desktop panel as the same floating bar-and-drawer that mobile uses.

You set the default side and whether the mobile bar shows under **Configure → Appearance**. See [Appearance](/maker-greatstore/configure/appearance.md).

## The composer

* The input shows an animated placeholder that cycles through **suggested prompts**. Pressing **Tab** drops the current suggestion into the box so the shopper can send or edit it.
* **Enter** sends, **Shift + Enter** adds a newline.
* The shopper can keep typing while the assistant is still answering: the next message **queues** and sends when the turn finishes, rather than being blocked.
* **Suggested-prompt chips** also appear inline in the conversation, both as openers and as follow-ups; tapping one sends it.

## Image search

A shopper can bring a picture into the conversation:

* **Attach** with the camera button, **paste** an image straight into the composer, or **drag and drop** it onto the panel.
* Up to **three images** at a time (JPEG, PNG, GIF, or WebP).
* Dropping a photo into an empty composer seeds a prompt like *"Find something like this"*, so an image on its own is a valid query.

{% hint style="info" %}
If **visual search** is enabled for your store, attaching a photo also surfaces a live row of visually-similar products as the shopper types.
{% endhint %}

## What streams back

Answers arrive token by token rather than all at once. Beyond plain text, the assistant can render interactive results inline: a single product card, a swipeable catalogue, a side-by-side comparison, a "swipe to checkout" control. Those are **apps**; see [Overview](/maker-greatstore/apps/apps.md) and the [App library](/maker-greatstore/apps/library.md).

## What the shopper sees

| What the shopper sees           | Where it comes from                         |
| ------------------------------- | ------------------------------------------- |
| Panel side / floating bar       | Configure → Appearance → Desktop panel side |
| The mobile bottom bar           | Configure → Appearance → Mobile bottom bar  |
| Colours, fonts, corner style    | Configure → Appearance                      |
| The "AI can make mistakes" line | Configure → Appearance → AI disclaimer      |
| Assistant name and header logo  | Configure → Basic                           |
| Product cards and comparisons   | Apps                                        |
| Visually-similar product row    | Store visual-search setting                 |


---

# 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.maker.co/maker-greatstore/storefront/text-chat.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.