Vitalii Popov

<p>This plugin is an AI chatbot that integrates with ChatGPT via API by OpenAI. After installation and customization, a chat bubble will appear on your website. The plugin will talk to your website visitors like a live person, motivating visitors to take certain actions. This is something like a sales manager, who will help users navigate the site and advise on your products and services.</p>
<p>Our plugin is based on the most advanced AI models from OpenAI. We use the ChatGPT-4o model. Please note that for correct work you need a working account on OpenAI platform site and some funds on your balance.</p>
<p>The plugin has flexible customization, and allows you to define very precisely how it should communicate with your site visitors. You can ask the AI to motivate users to make purchases, visit certain pages, or perform other actions. The AI assistant will try to guide users exactly in such a way that they are maximally active on your site.</p>
<p>The plugin will prompt users with links to various pages on your site. If you sell products through your site, a visitor will be able to ask the plugin to find products based on a given set of criteria. As a response, the AI will be able to return a direct link to specific pages on the site. In other words, you can also think of the plugin as a super-smart search engine for your site that will help the visitor not only find the information they need, but also take the necessary actions on your site.</p>
<h4>Plugin Features:</h4>
<ul>
<li>Communication with visitors in human language ( any languages supported by OpenAI )</li>
<li>Accurate answers based on information from your website</li>
<li>Direct links to pages on your site as answers to questions</li>
<li>Customizable nature of communication. Several unique characters-consultants.</li>
<li>Customizable limits and precise control over API usage</li>
<li>Detailed logging of dialogs with users</li>
<li>Customizable level of humor. A robot that can joke!</li>
<li>Custom instructions on how to communicate with users</li>
<li>Flexible system of training and re-training of AI assistant</li>
</ul>
<h3>External services</h3>
<p>For its operation, our plugin uses the API from the OpenAI platform. This is vital for our plugin to work because our plugin uses ChatGPT to train the AI assistant and then communicate with users. We pass a minimum of necessary information through the API. We call the following API methods for the following needs:</p>
<ul>
<li>https://api.openai.com/v1/chat/completions (POST) – the call is used to test the plugin by validating your API key and initially saving the settings. Usually this call is made at the moment of initial plugin configuration, when you specify your API key. As part of this call, we send your API key as well as a set of test messages, such as “Say this is a test!”.</li>
<li>https://api.openai.com/v1/files (POST) – the call is used to upload a training file with a list of articles from your site, as well as links to the pages of your file. This file has JSON format. The content of the file is created on the basis of the pages that you decided to use for training the AI assistant when working with the “Training” tab. The file contains the texts of articles from the pages of your site, as well as links to the corresponding pages of your site. A copy of this file is stored on your site, in the plugins/talk-to-website/admin/training directory.  As part of this call, we send the file itself, as well as your API key. This function is called when you perform plugin training on the “Training” tab. We only send information about the articles that you have specified in the training process using the checkboxes.</li>
<li>https://api.openai.com/v1/files/file_id (DELETE) – the call is used to delete an old file that was used in past AI training. As part of this call, we send the ID of the file to be deleted in the file_id parameter, as well as your API key. This function is called when you perform training of the plugin on the “Training” tab, in case we found old files used for past training.</li>
<li>https://api.openai.com/v1/vector_stores (POST) – the call is used when training the plugin, after loading a file using the v1/files method. After uploading a training file, we create a vector store where we put the newly uploaded file. Accordingly, this happens only when training the plugin in the “Training” tab. Within this call, we send the ID of the created file, the name of the vector storage, as well as your API key.</li>
<li>https://api.openai.com/v1/vector_stores/store_id (DELETE) – the call is used to delete the old vector store that was created during the past AI training. This only happens when training the plugin in the “Training” tab. As part of this call, we send the storage ID in the store_id parameter, as well as your API key.</li>
<li>https://api.openai.com/v1/assistants (POST) – the call is used when training the plugin, after creating a vector storage using method v1/vector_stores. Also, this call is used when changing the parameters of the AI assistant (e.g. robot name, additional instructions, company contact phone number, company address, prohibited topics for conversation, and so on – text fields from the “settings” tab inside the plugin). As a result of this call, an AI assistant is created on the OpenAI platform, trained according to the specified settings, and associated with a training file with a list of materials from your site. As part of this call, we pass your API key, as well as various textual information from the “Settings” tab: type of GPT model, robot name, instructions on the robot’s character, general textual instructions for training, forbidden topics and words, humor level, language used to communicate with visitors, contact information about your project (Email, phone number, website address, map address), limits on the length of responses, your website address, a brief description of your website, the ID of the associated vector store.</li>
<li>https://api.openai.com/v1/assistants/assistant_id (DELETE) – the call is used to delete old AI assistants on the OpenAI platform that are no longer needed. As part of this call, we send the assistant ID in the assistant_id parameter, as well as your API key.</li>
<li>https://api.openai.com/v1/threads (POST) – the call is used to create a new conversation thread with the AI assistant. It is used when starting a new dialog between a site visitor and the AI assistant. As part of this call, we send your API key.</li>
<li>https://api.openai.com/v1/threads/thread_id/messages (POST) – the call is used to create a new message from the user to the AI. It is used each time a message is sent to the chat room from the user. The “thread_id” parameter in the URL is the identifier of the thread that was created using the v1/threads call. Within this call, we pass the thread id as well as the text of the message entered by the user in the chat window. Also within this call, we pass your API key.</li>
<li>https://api.openai.com/v1/threads/thread_id/messages (GET) – the call is used to get a list of messages that were sent to the AI or received as a reply from the AI. It is used every time when sending messages to the chat from the user, as well as when receiving a list of responses from the AI. The “thread_id” parameter in the URL is the identifier of the thread that was created using the v1/threads call. Within this call we also pass your API key.</li>
<li>https://api.openai.com/v1/threads/thread_id/runs (POST) – the call is used to create a run within the AI thread. In other words, causes the AI assistant to analyze the messages sent, and generate responses to those messages. It is used every time chat messages are sent from a user. The “thread_id” parameter in the URL is the identifier of the thread that was created by the v1/threads call. Also, within this call we pass your API key, and also some service information ( context depth, run temperature ).</li>
<li>https://api.openai.com/v1/threads/thread_id/runs/run_id (GET) – the call is used to get the status of the run ( to understand that the run is complete and we can see the results of the run ).  The “thread_id” parameter in the URL is the identifier of the thread that was created using the v1/threads call. The run_id parameter is the id of the run that was created using the /v1/thread_id/runs (POST) call.  Also, as part of this call we pass your API key.</li>
<li>https://api.openai.com/v1/models (GET) – the call is used to retrieve a list of AI models that are available for your account. This is a rare and optional call that is practically not used by the plugin. Also, within this call we pass your API key.</li>
</ul>
<p>More information about the OpenAI platform: <a href="https://platform.openai.com/" rel="nofollow ugc">homepage</a>, <a href="https://openai.com/policies/" rel="nofollow ugc">tems and policies</a>, <a href="https://openai.com/policies/terms-of-use/" rel="nofollow ugc">terms of use</a>, <a href="https://openai.com/policies/privacy-policy/" rel="nofollow ugc">privacy policy</a>.</p>


Talk To Website

AI chatbot powered by ChatGPT from OpenAI. Scans the content of your site, then trains an AI assistant that speaks to users like a live person.

hosting.io

<p><strong>Sitewise turns your existing pages into a chat assistant that answers visitors using only your own content</strong> — no hallucinated competitors, no off-brand advice. It also includes the original request-a-call-back form, so visitors who would rather talk can leave their number.</p>
<p>The plugin compiles your published content into a small knowledge corpus (the <code>llms.txt</code> / <code>llms-full.txt</code> pattern) and keeps it in sync as you publish and edit. A lightweight Cloudflare Worker answers questions strictly from that corpus, and falls back to your contact page when it does not know.</p>
<blockquote>
<p><strong>Note:</strong> the grounded chat assistant is in preview while we finish the hosted Worker. Out of the box the public floating widget is the <strong>request-a-call-back form</strong> (no Worker required). Once you connect a Worker and switch the front-end to chat mode, the same launcher becomes the assistant.</p>
</blockquote>
<h4>What you get</h4>
<ul>
<li><strong>Request-a-call-back widget</strong> — a floating launcher (or inline <code>[sitewise]</code> shortcode) that lets visitors leave their number; submissions are stored in your dashboard and emailed to you. <strong>This is the default front-end widget today.</strong></li>
<li><strong>Grounded chat assistant (preview)</strong> — once a Cloudflare Worker is connected, the launcher answers from your pages only.</li>
<li><strong>Self-maintaining corpus</strong> — rebuilt automatically when you publish, edit, trash, or delete content.</li>
<li><strong>Public <code>llms.txt</code> files</strong> — so other AI agents can read your site too.</li>
<li><strong>Hand-curation where it counts</strong> — an orientation block and an FAQ block you write once, plus a per-page “AI summary” box.</li>
<li><strong>Request-a-call-back form</strong> — the original Call-Me-Back feature, rewritten clean. Use the <code>[sitewise_callback]</code> shortcode or the sidebar widget; submissions are stored in your dashboard and emailed to you.</li>
</ul>
<h4>Two ways to run it</h4>
<ul>
<li><strong>BYO Cloudflare (free):</strong> deploy the included Worker to your own Cloudflare account and pay your own (tiny) inference cost. Cleanest privacy story.</li>
<li><strong>Hosted (optional):</strong> paste a site key from a Sitewise account and let us host the Worker, with analytics and stronger models.</li>
</ul>
<h4>Privacy</h4>
<p>By default the Worker logs no chat content — only message counts for rate limiting. Your corpus is built from already-public pages.</p>
<h3>A note on this update (3.x <span aria-hidden="true" class="wp-exclude-emoji">→</span> 4.0)</h3>
<p>This plugin began life as <strong>Call me back widget</strong>. Version 4.0 keeps that call-back form as a built-in feature and adds the Sitewise assistant as the new headline capability. <strong>Existing call-back users keep their widget</strong> — enable it under <strong>Settings <span aria-hidden="true" class="wp-exclude-emoji">→</span> Sitewise <span aria-hidden="true" class="wp-exclude-emoji">→</span> Call-back widget</strong> — and gain the assistant on top. See the upgrade notice below.</p>


Sitewise

Add an on-page assistant that answers only from your own content, plus the classic request-a-call-back form. Grounded, cheap, no SaaS lock-in.

Talk To Website vs Sitewise