An AI chat agent that answers in a second.
And it knows who asked.

A visitor-facing assistant that answers questions on your site in plain language. This one answers from your own pages, files and catalogue rather than from general knowledge about your industry, and it already knows who it is talking to, because the platform has been watching the session since the visitor arrived.

From sources you point it at — a web address it crawls, an uploaded file, or text you paste. Everything is cut into passages that keep their own heading, so an answer can show the page it came from. On a shop it also searches your catalogue for price, stock and attributes exactly as stored, and invents nothing around them.

It hands over — to a person, or to an email address — with a subject written from what was actually being discussed rather than a generic “Chat request”. Every question it could not answer is also grouped onto one list, which is the most useful thing it produces.

Yes, and this is the part a bolt-on widget cannot do. The chat is an action inside a campaign, so all the targeting you already use applies to it: audience, page group, cart value, device, referrer, and how often it may appear. Four campaigns can put four different assistants on four parts of the site, each with its own knowledge, tone, colours and handover route.

Yes. Point the ask box at a product catalogue or a content catalogue; it answers in a sentence and then hands back the items themselves, ranked for that visitor by the same engine that orders your recommendations.

It is a paid add-on, priced on the pricing page, with an allowance of 100 to 1,250 conversations depending on your plan, and a seven-day free trial bounded by the same allowance. Cost is also recorded per conversation rather than only per account, so you can see which kind of conversation is the expensive one.

Only the categories you switched on, and every category is off by default. Where they are enabled that means the page the visitor is on and how they got there, their device and rough location, what they have completed before — and a small set of profile fields: industry, account type, lead source, and your own custom fields. Stored contact details are not among them.

No. Email address, first and last name, phone number, birthday, postal code and geographic coordinates sit on the visitor profile and are never included in what the assistant is given. That is enforced in the code rather than left to configuration, and a test fails the build if anybody adds one of those columns to the query.

Three, and they are worth stating plainly. Your own custom fields: if you put an email address in a custom field it is sent, because the whole point of a custom field is that we do not know what is in it. Whatever the visitor types: if somebody types their own address into the chat, it is in the conversation. Handover: when a visitor asks to be contacted, they are asked for a name and email so somebody can reply — optional, given deliberately, and the one place personal data is collected on purpose.

It is never fetched. A category that is off is not read and then removed — it is simply not part of what gets looked up. The switches are the query plan, so “we only send what you allowed” is true of the database traffic and not just of the prompt.

No. Every query is scoped to your account, and conversations are stored in your account like any other Personyze data. Nothing is copied out to a shared store.

No. What it sees describes a browser, not a verified person — it may be a shared desktop or a family laptop. It is told to treat none of it as proof of who it is speaking to, never to accept a visitor’s claim to be someone as confirmation, and never to use any of it to grant access to anything.

Not unless you turn that on. Reciting profile details to the visitor is off by default: the assistant may act on what it knows — “the coat you were looking at” — without reading the record back.

Treat it as an inference. Enrichment of that kind is a guess made from a network or an email domain and is confidently wrong often enough to matter, so the assistant is told to treat it as a hint and never to state it back as fact.

For the retention period you set, 90 days by default and never longer than the platform ceiling of 730. One exception: a handover that is still open is kept until it is closed, so the person replying still has the context.

Those are contractual and infrastructure questions rather than things the software does, so they belong in the privacy policy rather than on a product page. See Security at Personyze for hosting, access and sub-processors, and the privacy policy for the current position.