> 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/tools.md). # In-chat tools Beyond answering, the assistant can act: ask the shopper a question, set up a notify-me, and stay aware of what they're looking at and where they are. The assistant doesn't only reply; it can take small actions inside the conversation when they help the shopper decide. These are built in and on by default; the assistant reaches for them on its own. ## Ask the shopper a question When a request is too broad to answer well ("I need a gift," "show me a jacket"), the assistant can ask the shopper a short set of **multiple-choice questions** to narrow it down (size, budget, colour, who it's for) before recommending anything. The shopper gets a clean stepped overlay, one question at a time. Each question is pick-one or pick-several, and there's always a **free-text box** so they're never boxed in by the listed options. If the assistant already knows a preference from [Memory](/maker-greatstore/storefront/memory.md), the matching answer comes pre-selected. The shopper can also skip and just keep chatting. ## Notify me When a shopper wants to hear back about a specific product (*"let me know when this is back in stock,"* *"tell me if the price drops"*), the assistant can set up a **notify-me** on that exact product (and variant, if they named one). It covers back-in-stock, low-stock, a new variant, a price drop, or going on sale. The first time, an **Allow notifications** button appears under the reply; tapping it grants browser notifications and registers the shopper's device. After that it simply confirms they're subscribed. The alert fires once, when the thing they're waiting for happens. {% hint style="info" %} Notify-me needs the shopper to grant browser notification permission. On your first-party storefront it works out of the box. In an **embed**, browser push additionally requires hosting a small helper file (`gs.js`) on your own domain; see [browser push notifications](/maker-greatstore/developer-reference/javascript-api.md#browser-push-notifications) in the JavaScript API. {% endhint %} ## Awareness of the current page In the embed, the assistant knows the page the shopper is currently on: the product they're viewing, the article they're reading. So *"is this in my size?"* or *"tell me about this one"* resolves to exactly what's in front of them, no copy-pasting a link. This reads your page's existing structured data (the schema.org markup search engines already use), takes only the pointers it needs to look the product up properly, and never trusts scraped detail over your real catalogue. It's automatic on any page that publishes that markup, with no shopper action and nothing to configure. ## Awareness of where the shopper is The assistant also has a rough sense of where the shopper is, down to their city, without asking them or requiring any permission. Ask it *"find the nearest store to me"* and it starts from there, then narrows down from whatever detail the shopper adds. Pair this with a store-locations document under **Knowledge** and nearest-store questions answer themselves. See [Adding sources](/maker-greatstore/knowledge/adding-sources.md). ## Showing products Displaying products (a single card, a swipeable catalogue, a side-by-side comparison, a swipe-to-checkout control) is handled by **apps**, which have their own section. See [Overview](/maker-greatstore/apps/apps.md) and the [App library](/maker-greatstore/apps/library.md). --- # 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/tools.md?ask=&goal= ``` `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.