Querzy vs AI Chatbot & Support Agent

Querzy adds an AI shop assistant to your WooCommerce store in under 5 minutes — no feed setup, no developer needed. Your customers ask product questions at 2am and leave when no one answers. Querzy responds instantly, in any language, from your live product catalog. This plugin connects to the Querzy cloud service (querzy.com) to power the AI assistant. A free Querzy account is required — see the External Services section below for full details. How it works Install and activate the plugin Enter your access key from querzy.com — your store domain is detected automatically The plugin syncs your products automatically and adds the chat bubble to your storefront That’s it. No XML feeds to configure. No theme editing. No imports. What customers can ask “Do you have treadmills under $500?” “Show me protein powders without soy” “What’s the difference between these two barbells?” “Do you have this in size L?” The assistant understands natural language in 100+ languages — including Macedonian, Serbian, Albanian, Croatian, Turkish, Arabic, and more. Key features Zero setup friction — products sync automatically on install; no separate feed plugin required Real product cards — answers include product images, prices, and direct links to buy 100+ languages — understands and responds in the customer’s language Always up to date — catalog syncs automatically whenever you add, update, or delete products Lightweight — single script tag, no jQuery dependency, no impact on page speed Privacy-friendly — no customer PII stored; all data processed in the EU (Hetzner, Germany) Works with all WooCommerce themes out of the box — no CSS conflicts, no template overrides, no custom code required. Requirements A Querzy account — free during early access at querzy.com WooCommerce 6.0 or later WordPress 5.8 or later External Services This plugin connects to Querzy (https://querzy.com), a third-party AI-powered product search and chat service. External connections are made in two ways: 1. Product catalog sync (server-side) When the plugin is activated, and whenever a product is saved or deleted in WooCommerce, the plugin sends your store’s product catalog data to the Querzy API at https://querzy.com/catalog/refresh. The data transmitted includes: product IDs, titles, descriptions, prices, SKUs, categories, tags, and image URLs. This request is authenticated with the access key you enter in the plugin settings. No customer data (names, emails, addresses, order history) is transmitted. 2. Chat widget (client-side) A JavaScript file is loaded from https://querzy.com/widget.js on your store’s frontend. This script renders the chat bubble and handles all AI-powered conversations. Visitor messages entered into the chat are sent directly from the visitor’s browser to Querzy’s servers for processing. The plugin itself does not log or store visitor chat messages. Use of this plugin constitutes acceptance of Querzy’s terms and policies: Terms of Service: https://querzy.com/legal/terms Privacy Policy: https://querzy.com/legal/privacy Store owners are responsible for disclosing the use of this service to their customers and for ensuring compliance with applicable data protection regulations (GDPR, CCPA, etc.) in their jurisdiction. Privacy When a store visitor uses the Querzy chat widget, their typed messages are transmitted to Querzy’s servers for AI processing. Store owners using this plugin should disclose the use of Querzy’s AI chat service in their store’s own Privacy Policy. This plugin does not independently collect, store, or process visitor personal data. All data handling is governed by Querzy’s Privacy Policy: https://querzy.com/legal/privacy

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