JewelsStore Chat Widget vs AI Chatbot & Support Agent

JewelsStore Chat Widget adds a floating chat widget to your website. Core free features: * Floating site chat widget. * Widget appearance settings. * Optional JewelsStore hosted AI service connection for reply generation. * Optional direct OpenAI API mode using the site owner’s own API key. * Optional WhatsApp quick-contact button. * Optional Meta WhatsApp Cloud webhook integration. * Agent instructions and knowledge fields. * Basic multilingual interface texts. * Optional aggregate installation insights after explicit opt-in. * Optional concise upgrade-aware assistant mode for the external AI service. * Hosted AI allowance can be limited by your external JewelsStore service without disabling the free widget itself. Premium features such as advanced analytics, conversation history dashboard, lead capture workflows, advanced automation, multi-agent tools, exports, and licensing are provided by a separate premium add-on and are not included in this free plugin. External services This plugin can connect to external services when you enable the related options in the plugin settings. JewelsStore hosted AI service * What it is used for: generating chat replies when the AI reply mode is set to JewelsStore hosted AI. * What data is sent: the visitor message, site URL, plugin slug, plugin version, and the configured runtime agent payload such as agent name, instructions, knowledge, and optional page context. * When data is sent: when a site visitor submits a chat message and the JewelsStore hosted AI mode is enabled. * Extra note: this hosted service may apply a hosted monthly reply allowance per site. If that allowance is reached, the free widget stays active and the site owner can continue with WhatsApp, direct OpenAI mode, or a premium hosted plan. * Service provider: JewelsStore. * Terms of use: https://jewelsstore.shop/terms-and-conditions/ * Privacy policy: https://jewelsstore.shop/privacy-policy/ OpenAI API (direct mode) * What it is used for: generating chat replies directly from the site when the AI reply mode is set to Direct OpenAI API. * What data is sent: the visitor message and the configured runtime agent payload such as agent name, instructions, knowledge, and optional page context. * When data is sent: when a site visitor submits a chat message and the site owner has chosen Direct OpenAI API mode. * Service provider: OpenAI. * Terms of use: https://openai.com/policies/terms-of-use/ * Privacy policy: https://openai.com/policies/privacy-policy/ Meta / WhatsApp Cloud API * What it is used for: receiving and sending WhatsApp messages through Meta when webhook integration is enabled and configured by the site owner. * What data is sent: WhatsApp message payloads and outgoing reply messages to the Meta Graph API. * When data is sent: only when the site owner enables Meta webhook mode and connects their Meta developer credentials. * Service provider: Meta. * Terms of service: https://www.facebook.com/legal/terms * Privacy policy: https://www.facebook.com/privacy/policy/ JewelsStore installation insights service * What it is used for: optionally refreshing aggregate installation insights shown inside the plugin settings page. * What data is sent: site URL, administrator email, plugin slug, plugin version, WordPress version, PHP version, locale, timezone, server name, and a small diagnostics payload. * When data is sent: only after the site owner explicitly enables the optional installation insights setting. * Service provider: JewelsStore. * Terms of use: https://jewelsstore.shop/terms-and-conditions/ * Privacy policy: https://jewelsstore.shop/privacy-policy/

You already know the old kind. A visitor asks a real question, the bot replies with a link to your FAQ page, and the visitor leaves. This is the other kind. Ultimo Bots puts a real AI support agent on your WordPress site. It answers from your own content, and then it does the actual work: books the meeting, looks up the order, saves the lead, and pulls you into the conversation when it matters. You describe it. It builds itself. There is no canvas to drag boxes around on. You open the builder and type what should happen, in your own words: “When someone asks about pricing, explain the plans and offer a demo call. If they want one, book it in my Cal.com and send the lead to HubSpot.” That is the entire build step. The agent is configured from that sentence. No code, no flowcharts, no developer, no agency. Changed your mind? Tell it. That is the edit step too. It doesn’t just answer. It acts. Connect the tools you already run, and the agent uses them mid-conversation: Books appointments in Cal.com, including reschedule and cancel, or hands over your Calendly link Takes payments and manages subscriptions through Stripe links. It can list, change, or cancel a subscription. Card details never enter the chat Saves and finds contacts in HubSpot, and subscribes visitors to Mailchimp with proper double opt-in Answers from your product catalog, with prices and stock, so “do you have this in blue” gets a real answer Calls your own API with your own credentials when you need something nobody else offers Captures leads inside the conversation and emails them to you the second they land Before the agent touches anything private, it emails the visitor a six-digit code and waits for it. Verified first, every time. One agent. Every channel. The same agent runs on your WordPress site, on a shareable chat link, in Facebook Messenger, Instagram DMs, Telegram, and Slack. You train it once and it shows up everywhere. Nothing to duplicate, nothing to keep in sync. It knows your business, and it will not invent Point it at your WordPress site and it reads it. Add PDFs, Word files, spreadsheets, Google Drive, OneDrive, Notion. Every answer is built from your material, and one click re-scans your site whenever it changes. When it does not know something, it says so and offers you instead. That one habit is why people trust it on a live site. It detects the language your visitor is writing in and answers in it. You configure nothing. You stay in control Write your rules in plain words and the agent holds them, even when a visitor pushes back. Watch conversations as they happen and jump in yourself with one click. The agent goes quiet the moment you start typing and picks up again when you leave. Get pinged in Slack, Telegram, Teams, or email whenever someone wants a human. Everything is included Every capability above is on every plan. Plans differ in volume, not in what your agent can do. No per-seat pricing, no per-resolution fees, no “contact sales”. Start with a free trial, then from $19 a month. Live in about two minutes Activate the plugin, answer a few questions, and your agent is on your site. That is the whole setup. External services This plugin connects to external services operated by Ultimo Bots to function. The integration is required to register your site securely and render your AI assistant. Below are the services, what they are used for, and what data is transmitted. Policies for all of them: Terms of Service: https://www.ultimo-bots.com/terms – Privacy Policy: https://www.ultimo-bots.com/privacy 1) Ultimo Bots Portal API – site registration What: https://portal.ultimo-bots.com/api/auth/wordpress/save_secret When: On plugin activation (and retried if the first attempt failed). Purpose: Register your WordPress site and exchange a site-specific identifier used for secure operations. Data sent: site_id (random UUID generated in your WordPress site), site_url (your WordPress home URL), site_secret (random secret generated in your WordPress site), and the admin user’s email, first_name, last_name (used only to prefill the onboarding form; transferred server-side, never placed in a URL). Data received: wordpress_secret_id (an internal identifier) and a one-time connect code (valid 15 minutes, single use). 2) Ultimo Bots Portal API – connect code What: https://portal.ultimo-bots.com/api/auth/wordpress/connect_code When: When you click “Connect to Ultimo Bots” in the plugin settings, and right before the one-time onboarding redirect. Purpose: Mint a fresh one-time connect code so the onboarding can be opened without any personal data in the URL. Data sent: site_id, site_secret, and the admin user’s email, first_name, last_name (prefill, server-side only). Data received: a one-time connect code. 3) Ultimo Bots Portal API – assistant lookup What: https://portal.ultimo-bots.com/api/wordpress/my_bot When: On WP-Admin page loads (throttled to once per 5 minutes), on the plugin settings page, and once daily via WP-Cron. Purpose: Fetch the ID of the assistant connected to this site, so the assistant activates automatically after onboarding. Data sent: site_id, site_secret. Data received: bot_id and its creation status. 4) Ultimo Bots Widget Configuration API What: https://portal.ultimo-bots.com/api/widget_configuration/{bot_id} When: On public page views where the assistant is displayed, and on activation to check whether an existing Bot ID is active. Purpose: Retrieve the widget configuration for your Bot ID (colors, sizes, welcome messages). Data sent: bot_id (path parameter); optionally host_url when provided by the widget for basic operational analytics. Data received: widget configuration JSON. 5) Ultimo Bots Widget Script Host – static asset What: https://robert-kloepsch.github.io/ultimo-bots-widget/dist/bundle.js When: On public page views where the assistant is displayed. Purpose: Load the widget client code. Data sent: standard CDN/HTTP request metadata (IP, user agent) as with any static asset request. Important: This plugin does not accept or store arbitrary HTML/JS/CSS from users. It only stores a Bot ID and generates safe markup internally. The widget script is properly enqueued via WordPress functions. Privacy This plugin communicates with Ultimo Bots services as described in External services. Please review: – Terms of Service: https://www.ultimo-bots.com/terms – Privacy Policy: https://www.ultimo-bots.com/privacy