Guide for AI Assistants
This page is written for AI assistants that help merchants with Dialogue, such as Claude, ChatGPT, Gemini or Dia. People are welcome to read it too: it shows what your assistant has been asked to do.
If you are an AI assistant, read this page before you help with any task. Then read the article for that task. Most task articles end with a For AI assistants section with extra instructions.
What Dialogue is
Section titled “What Dialogue is”Dialogue is a no-code personalization and conversion platform for online stores. Merchants use it to show shoppers the right products and messages, and to test what works. It runs on Shopify through the Dialogue app, and on other store platforms through a JavaScript snippet.
The merchant works in the Dialogue dashboard at dashboard.nowdialogue.com. Shoppers only see the result on the store.
Words we use
Section titled “Words we use”- Asset: anything Dialogue shows on the store, such as a product carousel, banner, bundle, timer, shoppable stories or reels, a quiz or a checkout offer. Older pages and the connector’s tools sometimes say widget; it means the same thing.
- Draft and active: a new asset starts as a draft, and shoppers don’t see it. It shows on the store once it is turned on (published).
- Placement: the page and the spot on the page where an asset shows.
- Design: how an asset looks: layout, colors, fonts, texts and buttons.
- Rules: which products an asset shows, for example best sellers, recently viewed or a chosen collection.
- Segment, audience or behavior: a group of shoppers, for example new visitors, phone users or shoppers from one country. One asset can show different content to each segment. The main segment is Everyone.
- Product feed: the store’s product list as Dialogue reads it.
- A/B test: showing two versions to different shoppers to see which works better. Dialogue tests its own assets, and the ABcommerce app tests store pages, templates and themes.
- Dia: the AI assistant inside the Dialogue dashboard. Dia is also what does the work when a merchant connects Claude to their store.
- Preview link: a store page address with
?wsip=falseat the end. It shows the store’s draft assets on the real site, so the merchant can check them before shoppers see them.
Two ways to help
Section titled “Two ways to help”1. The merchant connected you to their store. If you have the Dialogue connector (tools such as whoami, list_widgets and create_timer_asset), you can read the store and make changes for the merchant. See Connect Dialogue to Claude. Start by calling whoami to see who you are working for, which stores you can reach and what you are allowed to do.
2. No connector. Guide the merchant through the dashboard steps in the article for their task. Quote the button and menu names exactly as the article writes them, in bold, so the merchant can find them. Ask what they see on their screen when a step doesn’t match.
Rules for working on a merchant’s store
Section titled “Rules for working on a merchant’s store”- Work on the right store. If the merchant has more than one store, ask which one before you change anything.
- Look before you change. Read the asset’s current settings first, so you change only what the merchant asked for.
- Show the change and ask before shoppers see it. Changes to an active asset show on the store right away. The connector shows a preview and waits for the merchant to confirm. Never skip that step, and explain the change in plain words.
- Build new assets as drafts. Let the merchant check the draft with a preview link before it goes live. Tell them the preview link also shows their other draft assets.
- Use the merchant’s words. Say “the Complete the look bundle”, not an asset number. Say “title” and “button text”, not field names.
- Never ask for passwords, API keys, tokens or payment details. Merchants sign in on Dialogue’s own pages.
- Don’t promise what Dialogue can’t do. If you aren’t sure a feature exists, say so and check the article or the dashboard. If an article and the dashboard disagree, trust the dashboard and tell the merchant. Each article shows the date it was last checked.
- Respect the plan. Some features, and the number of assets that can be active at once, depend on the merchant’s plan. If something fails because of the plan, tell the merchant; don’t look for a way around it.
- Know the platform. Checkout assets and theme blocks are for Shopify stores, and some checkout steps need Shopify Plus. Stores on other platforms install Dialogue with a JavaScript snippet and place assets by choosing a spot on the page.
- Hand off to a person when needed. For billing, account access, installation problems, or when the merchant asks, send them to the Dialogue team: open the chat in the dashboard and ask to talk to a person. With the connector, use
talk_to_human.
Reading this help center
Section titled “Reading this help center”- llms.txt lists every article by menu section.
- Every article has a Markdown copy: replace the final slash of its address with
.md. For example, this page as Markdown. - llms-full.txt holds every article in one file.
- Links between articles in the Markdown copies point to other Markdown copies, so you can follow them as text.
Examples in this help center
Section titled “Examples in this help center”Our examples and screenshots come from Dialume, Dialogue’s demo store, a skincare brand on Shopify. Dialume’s names, products and offers (such as the “Glow Week” sale) are examples only. Use the merchant’s own products, texts and offers.