For online shops
I search your live catalogue, not a copy of it. Then I show the dress in your own shop.
People don't search the way your search box wants them to. They don't have the right keyword or the right three filters; they have a sentence. I take the sentence, ask your catalogue, and open what I found where it belongs: in your storefront, as a filtered list, a product card, the cart. Delivery and returns I answer from your pages, and I walk the person to checkout.
What happens in a shop once I'm in it.
- «Something like this, but cheaper.»
I ask your catalogue API with the visitor's own words and show what came back — in your own product grid, not in a chat bubble. Ten thousand items or a million; I read none of them in advance.
→ - «When would it arrive in Lviv?»
From your delivery page, with the link. «Can I return it?» From your returns page. The questions your operators answer forty times a day — answered before they're asked of a person.
→ - «Add it to my cart.»
When your shop lets me, I press the button. Before anything that charges a card, I ask.
→ - «Where's my order?»
If you give me an order-status endpoint, I look it up for that customer — their login goes along with the question, so I only see what they'd see.
→ - «I need to talk to someone.»
A contact form in the chat, or your support channel, with the conversation's context passed along. And in your panel: which channel people actually use.
→
</>
One endpoint, described once. Your developer's part takes an afternoon.
In your panel you describe one HTTP call: the address of your catalogue search, the parameter I fill with the visitor's words, where the token lives. I add the language myself. You tell me what the response means — «a list of products with a name, a price and a link» — and from then on I know when to ask it.
Want the results drawn in your shop rather than described in chat? Name an event — «show these products» — and your page listens for it. One listener, one afternoon.
Your catalogue stays yours: I call it live, with your token, from one place, and I reuse an answer only if your server tells me I may.
What a month of this looks like.
Fewer searches that end nowhere.
People who typed a sentence and got a product, not «0 results».
Fewer delivery questions for your support team.
Your panel shows how many conversations ended without a person — and in which ones a customer still needed your team.
The questions your shop couldn't answer.
«Do you have it in petite?» — grouped, so you know what to add to the page or the catalogue.
«Where are my customers' conversations kept?»
On servers in Frankfurt, in the EU, for as long as your plan says. To be answered, a question goes to the provider of the language model you picked in the panel — in the USA.
«Can you see my customers' accounts?»
Only what your API returns about them, and only if your site hands me their sign-in — I pass it on with each request and never store it.
«And their card details?»
Not by default: I don't read what people type into fields, and a payment form usually opens on the payment provider's side, where I can't reach. Data and control →
Growth
For a shop, it's Growth.
Your own catalogue, events in your storefront and the «add to cart» press come with Growth: $29 a month, 7,000 credits, 2,000 pages. A big catalogue is served through your API, so it never counts as pages.
Let people shop in sentences.
