Give it your feed’s address
The file your shop already makes for Google Shopping or a Meta catalog: XML, TSV or CSV, compressed or not. It is read at once, then again every day, for up to 20,000 products.
For shops
Your products, answered
Give the assistant the product feed your shop already makes, and visitors can ask what to buy — by budget, brand or specification — and get the products themselves, with their pictures, prices and links. It is the platform’s application for shops.
Visitors ask in their own words
“A cordless drill under 150, in stock?” By budget, brand, category or specification, and with how many matched: when twenty-seven do, it says so and shows the cheapest.
The products, as cards
Each product the answer names is drawn under it with its picture, name, price, availability and a link to its page, which opens in a new tab so the conversation stays where it was.
The product on the page
“Is this one in stock?” needs no name
On your own site, the assistant knows which of your products the visitor has open, so they can ask about it without naming it. The page’s address is used for that one question to find the product, then dropped. A page we host has no product of yours open, so there it is asked by name.
Read-only, here too
It recommends; your shop sells
It recommends and links. It never adds to a cart and never checks out.
A recommendation says what it was chosen by and the budget or need it assumed, and asks one question when the need is unclear. Delivery, warranty and returns come only from your manuals and business context.
What it will not do
As of the last reading, and nothing made up
Prices and stock are as of the last reading, and when they are the point, the answer says so. A specification the feed does not hold is never invented; when it compares products, it names what one of them lacks. A feed that cannot be read to its end changes nothing: visitors keep the catalog read before.
Wherever it answers
On your website and inside your app
Your public assistant reads it too, and so does every key you make, the API included; a key switched to knowledge base answers from your documents alone. The products a search finds reach the AI provider answering the question: yours if you bring your own key, Sonela’s if you run on ours.
What is kept
Your catalog lives in your workspace
Like the written material you upload, the catalog is kept in your workspace, and only your workspace reads it. Products from a product feed you add are kept the same way: each product’s name, description, price, availability, link, picture address, brand, product codes, categories and specifications, replaced whole at each reading and deleted with the feed or the workspace. Pictures load from your shop’s own address and are never copied, and the address of the page a visitor has open is used for that one question to find its product, then dropped.
Plans
On every plan, the trial included
On every plan, the trial included. Add the feed on the Products tab of your dashboard’s Context page; the product catalog guide walks through it, from finding your feed’s address to the first question.
Your feed is already written
Open a workspace, give it your feed’s address, and ask it for something you sell.
14 days, 320 question credits, no card. No AI key to supply — trials run on Sonela's key.