Reads what you already published
Your pages, posts, products and their descriptions. Activate it and the index builds itself. There is no knowledge base to curate, no intents to tag and no embeddings pipeline to wire up.
Features
Most of this list is what other plugins ask you to assemble yourself. DFYe is short for Done For You Employee, and it arrives already assembled, which is also why it costs money.
This is where the personalisation actually happens. The knowledge base builds itself out of what you already published, and rebuilds when you change a page, so what it knows about you is never a version of you from six months ago.
Your pages, posts, products and their descriptions. Activate it and the index builds itself. There is no knowledge base to curate, no intents to tag and no embeddings pipeline to wire up.
Edit a page and the passage behind it updates. You never have to remember to retrain anything.
Anything noindex stays out. Anything behind a login stays out. A per-post switch takes out the rest.
A Dutch visitor gets answered from the Dutch pages, not from a machine translation of the English ones.
The question everybody asks is what happens when it gets one wrong. The answer is that there are three outcomes and no fourth. Above the confidence floor it answers and cites the page. Below it, it says your site does not cover that. Either way, what it will not answer reaches a person rather than a dead end.
Retrieval scores every passage against the question. Below the floor the answer is that it does not have it, and the conversation stays honest.
The page an answer came from is a chip under the answer, and it is a real link. A visitor can check the claim in one click, and so can you.
The prompt is in the settings screen, in full, and you can edit it. Nothing about how the answer is produced is a secret from the person who bought it.
Below the floor it offers your contact form, your email or your existing live chat, and passes on what the customer asked and the pages it looked at, so your reply starts from what they already said instead of asking them to repeat it.
Every declined question lands in a log in your own admin. That list is both a support backlog and a content plan, and your customers wrote it.
A support widget is the one plugin every visitor sees on every page. The default here is meant to belong on a site somebody cared about, and every part of it is one custom property away from being yours.
Not a rounded purple bubble with a cartoon robot. The default is the one on this page, and it is meant to look like it belongs.
Colour, radius, font, shadow, spacing, all CSS custom properties, all in one panel. No stylesheet to override and no !important war with your theme.
Your theme cannot reach into the widget and the widget cannot leak into your theme. That is why it looks the same on every site.
It follows the visitor's system setting, or you pin it. Both themes are designed, neither is an inverted afterthought.
9.7kB gzipped, after paint, from your site to your model provider. Nothing of yours touches our servers.
The build fails if it goes over 20kB. That number is not a target on a slide, it is a gate in the pipeline, and the figure on this page comes straight out of it.
One deferred file. No render-blocking request, no layout shift, no effect on your largest contentful paint.
Conversations go from your site to your model provider. Nothing routes through our servers, so there is no markup, no queue and nothing of yours on our infrastructure.
You never sign into anything of ours. The plugin is the product, not a client for a service.
Ask this site's own widget a question and watch it cite the page, or refuse. It is the same plugin, running on the same content you are reading.