Questions

Is there really no dashboard?

Right. You describe what you sell and how you want it to sound, and I run the rest. If you want something changed, you email me and I change it.

Does it make things up?

It answers only from your content and from the lookups you connect, and it says plainly when it does not know. It will not invent a price, a policy or a spec.

Do we hold an API key?

Only on your own server, inside the proxy I give you. The browser never sees it.

How does the order lookup work?

You expose an endpoint on your side for it to call. Those calls are read-only, go through your server, and are scoped to the customer asking, so no one can pull another customer's details.

What data do you get from us?

The public pages I scrape, whatever the lookups return at the moment they are called, and the conversations customers have with the widget so you can read them back.

How long are conversations kept?

You set the retention period. Anything older is deleted automatically.

What is in the monthly report?

The five things customers were most confused about, the objections turning up before checkout, and complaints as they surface, each with a specific change worth making. Built from the real conversations.

Our site changes often. Will it keep up?

I check for changes as often as every 30 minutes and re-read the site when a page you care about actually changes.

What if it is not answering well?

Tell me and I fix it. That is the arrangement. If it is not right during the sign-off period, you have not paid the setup fee and it has not gone live.

What if our catalogue is huge?

There is a ceiling on how much text I load per site. Past it, a search-based setup fits better than a flat knowledge base, and I say so upfront.