# Three steps. About a minute.

> Source: https://dfye.com/how-it-works/
> Language: en
> Part of https://dfye.com/ (DFYe). This file is the Markdown twin of the page above; the page is the canonical document.

How it works

No onboarding wizard, no knowledge base to build, no intents to tag, no styling session before it looks acceptable. The install is short because the work happens after it, without you: DFYe reads the store you already built and personalises itself to it.

## The install, step by step

1. Step 1
   
   ### Install it the way your platform installs things
   
   On WordPress that is Plugins, Add New, Upload, and the same three clicks as anything else. On the platforms being built after it, it is that platform own way in: an extension, a module, an app. One product, one job, per platform.
2. Step 2
   
   ### Paste your model key
   
   One field on the settings screen. The key is stored in your own database and used from your own server, so it never reaches us and neither does any conversation.
3. Step 3
   
   ### It learns your store
   
   Every published page, post and product is read and split into passages, each one kept with the page it came from. Anything noindex, private or in draft is skipped. A few hundred pages takes under a minute; a large catalogue finishes in the background. There is no training step and no knowledge base to write first: this is the whole of the onboarding.
4. Step 4
   
   ### The widget goes live
   
   It appears on your site with a default that is meant to belong there. Every colour, radius, font and shadow is a custom property, so making it look like your store is one panel, not a stylesheet fight.
5. Step 5
   
   ### It answers, declines, or hands over
   
   Answers come from your pages with the source page attached as a link. Below the confidence floor it says the site does not cover that, and passes the customer to your contact form or inbox rather than guessing.
6. Step 6
   
   ### You read what they asked
   
   Every question lands in a log inside your own admin, including the ones it could not answer. That list of gaps is a support backlog and a content plan, written by your own customers.

The part everyone fears

## It answers from your pages, or not at all.

The reason people distrust a chatbot on their own site is that it invents things. This one answers from what it read, links the page it read, and declines when nothing scores.

- Answers built out of your own pages, in your own wording
- Every answer carries a link to the page it came from
- Below the confidence floor it declines instead of guessing
- What it declines goes to a person, with the question attached
- Nothing noindex, private or in draft is ever read
- Every question logged in your own admin, including the unanswered ones

20 kB

budget the build enforces on the widget, or it fails

0

conversations of yours stored on our servers

100 %

of answers taken from your own published pages

## Put a real answer on every page.

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.

[Join the launch list](https://dfye.com/launch/) [Try the live demo](https://dfye.com/demo/)

---
*Published by [DFYe](https://dfye.com/). Free to read, index, quote and cite with attribution and a link.*