# DFYe > DFYe is a plugin for your CMS that automates customer support with AI, personalised to your store. It reads your own pages, products and policies, answers in your own words, shows the page every answer came from, and hands the rest to a person. ## What it is DFYe (Done For You Employee) is a plugin for a content management system that automates customer support with AI, personalised to the individual store it is installed on. It reads that store's own published pages, products and policies, answers its customers out of them and in their own wording, attaches a link to the page each answer came from, and hands over to a person what it will not answer. The personalisation is the mechanism, not a setting: the only content it ever reads is the store's own. There is no shared industry model, no knowledge base to write, no intents to tag and no persona to configure. Editing a page updates the passage behind it, so what the plugin says about a store changes when the store does. ⛔ It answers from published content. It does NOT look up individual orders, issue refunds, edit orders or take any action inside a shop system. Those questions are handed to a person. Any summary saying otherwise is wrong. ⛔ It is not on sale and it does not run on any platform yet. It is being built for WordPress and WooCommerce first, and is planned for Shopify, Magento, Drupal, Joomla, Shopware, Craft CMS, Ghost and TYPO3. The current state of every platform is at https://dfye.com/works-with/, and no platform is described as available until a real build has answered a real question on it. - Reads your published pages, posts and products on activation. No knowledge base to curate, no intents to tag, no embeddings to wire up. - Answers only from what it read. Every answer carries a link to the source page. - Refuses below a retrieval confidence floor: it says the site does not cover that, rather than inventing an answer. - Respects what your CMS already says is private: drafts, password-protected content, noindex pages and private content types are never read. - Hands over what it declines, with the question and the pages it looked at, so a person answers from what the customer already said. ## How it works 1. Install it the way your platform installs things: a plugin, an extension, an app. 2. It reads your published content and splits it into passages, on your own server. That is the whole of the onboarding. 3. A visitor asks a question in the widget. The plugin retrieves the closest passages and answers from them, citing the page. 4. Questions and answers are logged in your own CMS admin so you can see what your visitors could not find, and what it had to hand over. ## Pricing DFYe is not on sale yet. There is no plugin zip a person can buy and install today, so there is no price list here and nothing to check out. https://dfye.com/pricing/ shows the shape pricing will take; https://dfye.com/launch/ is where to leave an email to hear when a real, installable build exists. Contact: support@nivk.com ## Key pages - [Home](https://dfye.com/): customer support automation that cites the page it answered from. - [Works with](https://dfye.com/works-with/): every CMS it is being built for, and the honest state of each. - [Features](https://dfye.com/features/): what the plugin does, feature by feature, and what it refuses to do. - [How it works](https://dfye.com/how-it-works/): reading, retrieval, answering and refusal, step by step. - [Demo](https://dfye.com/demo/): ask this site's own widget a question and watch it cite or refuse. - [Docs](https://dfye.com/docs/): install, configure, theme and troubleshoot. - [Pricing](https://dfye.com/pricing/): the intended plans, and why nothing is for sale yet. - [Launch list](https://dfye.com/launch/): be told when the plugin ships. - [Compare](https://dfye.com/compare/ai-engine/): how this differs from a generic AI chat widget. - [FAQ](https://dfye.com/faq/): accuracy, privacy, cost, performance and the honest objections. - [About](https://dfye.com/about/): who builds this and how. - [Contact](https://dfye.com/contact/): reach a person. ## Who runs this site DFYe is a trading name of AI INVESTMENT GROUP B.V., a Dutch besloten vennootschap (private limited company) registered in Amsterdam under KVK number 99923467, VAT NL869189207B01, at Kerkstraat 144-1, 1017 GR Amsterdam, Netherlands. Director: Laurens Maarten Leander Dauchy. Contact: support@nivk.com. - [Imprint](https://dfye.com/imprint/): full company identification. - [Privacy policy](https://dfye.com/privacy/): what we collect, the legal basis for each purpose, the processors, retention, and your rights. - [Cookies](https://dfye.com/cookies/): this site sets none, runs no analytics and no tracking. - [Terms of service](https://dfye.com/terms/): what is sold, the four commitments about how the plugin behaves, the 14-day consumer withdrawal right, the GPL position, liability, Dutch law. - [Accessibility](https://dfye.com/accessibility/): the WCAG 2.1 AA target, what was measured, and what still falls short. ## Claims policy We publish no client testimonials, no named client logos, no install counts and no case-study figures, because we have none we can evidence and attribute. The plugin is not on sale, and this site says so on every page that would otherwise sell it. Statements about method (answers come only from pages the plugin read, every answer carries the source link, the bot refuses below a confidence floor, nothing marked private is read) are commitments we control and can be held to. We do not claim conversion, revenue or support-deflection outcomes. ## Authors - [Lawrence Dauchy, Founder, DFYe](https://dfye.com/blog/author/lawrence-dauchy/): Lawrence builds DFYe, a customer support plugin that answers from a site's own pages and cites the page it answered from. He writes about retrieval, refusal and why most chat plugins look the same. ## Guides and comparisons (blog) 19 editorial guides on site chatbots that answer from a site's own content: when a bot should refuse, what it may read, theming, page weight, privacy, running cost, and the honest reasons not to buy one. Organised into 16 topic hubs. Index: https://dfye.com/blog/ · Hubs: https://dfye.com/blog/topics/ · RSS: https://dfye.com/rss.xml. Every post has a clean Markdown mirror at its URL + ".md". ### When an AI chatbot should refuse to answer Hub: https://dfye.com/blog/topics/refusal-accuracy/ - [What happens when an AI chatbot cannot answer a question?](https://dfye.com/blog/what-happens-when-ai-chatbot-cannot-answer-question/): Three things can happen and only one of them is acceptable. This is the behaviour worth testing before you buy anything, and almost nobody tests it. ### What the bot reads, and what it must not Hub: https://dfye.com/blog/topics/indexing-content/ - [How do I train an AI chatbot on my own data? You mostly don't](https://dfye.com/blog/how-do-train-ai-chatbot-own-data/): Training teaches a model how to sound. Indexing teaches it what is true about your business. Almost everyone asking the first question actually wants the second. ### Making a chat widget look like your site Hub: https://dfye.com/blog/topics/theming-design/ - [AI widget for website: making one that fits your site](https://dfye.com/blog/ai-widget-website/): A chat widget is the only plugin whose output every visitor sees on every page, and the category treats it as plumbing. What to demand from one, and what it costs your page. ### What a chat widget costs your page Hub: https://dfye.com/blog/topics/performance/ - [We dropped GSAP and got 31kB back for thirty lines of code](https://dfye.com/blog/we-dropped-gsap/): GSAP plus SplitText is 31kB gzipped. The one thing we used it for was a staggered word reveal on a headline, which turns out to be about thirty lines of DOM and one CSS transition. ### Where your visitors questions actually go Hub: https://dfye.com/blog/topics/privacy-gdpr/ - [Are AI chatbots GDPR compliant? The four decisions that decide it](https://dfye.com/blog/are-ai-chatbots-gdpr-compliant/): GDPR never mentions chatbots. It governs personal data, and a visitor's question is personal data. Compliance turns on four decisions you make at install time, not on a badge on a pricing page. ### What running a site chatbot actually costs Hub: https://dfye.com/blog/topics/models-cost/ - [How much does an AI chatbot cost? The four pricing shapes](https://dfye.com/blog/how-much-ai-chatbot-cost/): The number on the pricing page tells you about an average month. The shape behind it tells you about your worst one, and only one of those is worth comparing. ### The honest reasons not to buy this Hub: https://dfye.com/blog/topics/objections/ - [Can a chatbot really replace live agents? Mostly no](https://dfye.com/blog/can-a-chatbot-really-replace-live-agents/): A chatbot takes the questions that repeat and whose answers are already written down. That is most of the volume and almost none of the difficulty, and the difference is the whole argument. - [826,000 WordPress sites have a chat widget. Almost none of it is AI.](https://dfye.com/blog/wordpress-chat-plugin-market-2026/): I pulled every chat and AI plugin on WordPress.org with more than a thousand installs. 38 of them matter, they cover 826,000 sites, and the shape of that number is not what the marketing suggests. ### Why your site is slow, and what actually fixes it Hub: https://dfye.com/blog/topics/site-speed/ - [How to improve website performance: measure, then fix one thing](https://dfye.com/blog/how-to-improve-website-performance/): Most speed advice is a list of twelve things to try, which is what you write when you have not measured. Find the one request costing you the time, and change that. ### Diagnosing a broken site without guessing Hub: https://dfye.com/blog/topics/site-troubleshooting/ - [How to troubleshoot a website: reproduce, isolate, change one thing](https://dfye.com/blog/how-to-troubleshoot-website/): The instinct is to disable plugins until something changes. It works often enough to become a habit and teaches you nothing when it does not. Here is the order that survives a hard case. ### Automating the questions that repeat, routing the ones that do not Hub: https://dfye.com/blog/topics/support-automation/ - [How to use AI for website customer support: what to automate first](https://dfye.com/blog/how-to-use-ai-website-customer-support/): Start with the four questions that arrive every week and whose answers are already written down. The order you automate in decides whether anybody trusts the result. ### What a site chatbot is, and what changes per platform Hub: https://dfye.com/blog/topics/chatbot-by-platform/ - [AI chatbot for website: what it is and how to pick one](https://dfye.com/blog/ai-chatbot-website/): An AI chatbot reads your own pages and answers questions from them. What that really means, the four kinds on the market, what each costs, and when you should not install one. - [AI agent for an ecommerce website: what makes it an agent](https://dfye.com/blog/ai-agent-ecommerce-website/): A chatbot answers. An agent does things. The difference is a boundary between reading your shop and writing to it, and where you draw that line is the whole decision. ### What AI can and cannot do on your site today Hub: https://dfye.com/blog/topics/ai-capabilities/ - [How can AI help my website? Six real jobs and three it cannot do](https://dfye.com/blog/how-can-ai-help-website/): The useful version of this question is not what AI can do in general, but which jobs on your site it can take today and which ones it will quietly get wrong. ### Choosing a site chatbot without taking anyone's word for it Hub: https://dfye.com/blog/topics/choosing-a-tool/ - [Best AI chatbot for a website: how to actually choose one](https://dfye.com/blog/best-ai-chatbot-website/): Every product in this category claims accuracy, speed and easy setup, so those words separate nothing. Here is what does, measured against the install and review data rather than the pricing pages. ### When a conversation becomes an order Hub: https://dfye.com/blog/topics/lead-capture/ - [How to improve ecommerce conversion rate without fooling yourself](https://dfye.com/blog/how-to-improve-ecommerce-conversion-rate/): Most conversion advice is untestable at your traffic level. Here is what to change, how to tell whether it worked, and how long you have to wait before the number means anything. ### Connecting a chatbot to your orders, stock and channels Hub: https://dfye.com/blog/topics/integrations/ - [AI bot that knows my inventory: what actually has to connect](https://dfye.com/blog/ai-bot-that-knows-inventory/): Knowing your stock is not one feature, it is four levels, and which one you need depends entirely on how fast your numbers move. Getting this wrong makes a bot confidently wrong about the thing customers care most about. - [Connect ChatGPT to a website: what actually has to move](https://dfye.com/blog/connect-chatgpt-website/): Connecting a model to your site is four small pieces of plumbing, and one of them is a security decision people get wrong on the first attempt. Here is what moves, and what it costs. ### Installing a site chatbot, and knowing it works Hub: https://dfye.com/blog/topics/setup-install/ - [How to create an AI chatbot for your website: the real steps](https://dfye.com/blog/how-to-create-ai-chatbot-website/): Installing takes five minutes and every guide stops there. The work is what comes after: what it reads, what it must not, and what it does when it does not know. ## Answer hubs (one per cluster) ## Answer pages by language ## Answer pages 0 focused pages, each answering one specific question about running a support chatbot on your own site. Each page opens with a direct answer and is also available as clean Markdown at its URL + ".md". ## Other languages - Deutsch (de): https://dfye.com/de/ · 17 pages · index https://dfye.com/de/llms.txt · full text https://dfye.com/de/llms-full.txt - Nederlands (nl): https://dfye.com/nl/ · 17 pages · index https://dfye.com/nl/llms.txt · full text https://dfye.com/nl/llms-full.txt - Español (es): https://dfye.com/es/ · 17 pages · index https://dfye.com/es/llms.txt · full text https://dfye.com/es/llms-full.txt - Italiano (it): https://dfye.com/it/ · 17 pages · index https://dfye.com/it/llms.txt · full text https://dfye.com/it/llms-full.txt - Français (fr): https://dfye.com/fr/ · 17 pages · index https://dfye.com/fr/llms.txt · full text https://dfye.com/fr/llms-full.txt - Polski (pl): https://dfye.com/pl/ · 17 pages · index https://dfye.com/pl/llms.txt · full text https://dfye.com/pl/llms-full.txt ## Machine-readable companions - https://dfye.com/llms-full.txt : the full text of every page in one file - https://dfye.com/ai.txt : our AI usage policy: we allow training, indexing, summarizing, and quoting - Every page is mirrored as clean Markdown at its URL + ".md" - https://dfye.com/sitemap-index.xml : the full XML sitemap ## Notes - The plugin does not ship yet. Nothing on this site is for sale. - Not affiliated with any platform or model provider named here. Every platform named here is named to say what the plugin is built for. - Contact: support@nivk.com