Rynex – Free AI Chatbot for WooCommerce (AI Sales & Support Agent)

Description

One plugin instead of five. The AI chat assistant, product recommendations, agentic add to cart, product FAQs with schema, re-engagement journeys and revenue attribution are one connection and one dashboard — not six plugins fighting over your product pages.

Rynex adds an AI chatbot and sales assistant to your WooCommerce storefront — like having ChatGPT trained on your own catalog, minus the API keys. Customers describe what they need in plain language; the AI agent recommends products from your live catalog, answers questions about shipping, sizing and stock — and it doesn’t stop at recommending. When the shopper says “add it”, the assistant puts the product into the WooCommerce cart itself, confirms only after your store actually accepted it, and offers a one-tap path to checkout.

Free plan included: 100 conversations per month at no cost — no credit card, no API key, no AI provider account. Connect and try it on your real catalog in minutes.

Available in 13 languages — the settings screens ship with English, Turkish, German, Spanish, French, Italian, Brazilian Portuguese, Dutch, Polish, Russian, Japanese, Simplified Chinese, Arabic and Indonesian; WordPress picks the one matching your site language. (The shopper-facing assistant answers in whatever language the shopper writes, independently of this.)

See the revenue, not just the chats. Every order driven by a conversation is attributed, so your dashboard answers the only question that matters: how much money is this assistant actually making? Most chat plugins stop at “conversations handled” — Rynex reports attributed orders and revenue per conversation.

It is a conversational commerce layer rather than a scripted chat bot: there are no decision trees to build and no keyword rules to maintain. The assistant reads your real catalog, so recommendations stay correct as prices, stock and products change.

One-click setup — install the plugin, press Connect to Rynex, done:

• Your catalog syncs automatically (products, prices, stock — kept fresh via webhooks).
• The chat widget appears on your storefront instantly. No code, no snippet pasting.
• Orders are attributed to the AI conversations that drove them.
• Manage everything — widget design, analytics, conversations — from your Rynex dashboard (one click away in WP admin).

What the assistant does

• Product recommendations — acts as a product finder, matching shoppers to items from your live WooCommerce catalog.
• Customer support answers — replies to questions about shipping, returns, sizing and availability.
• Order tracking questions — points customers to their order status instead of opening a support ticket.
• Agentic add to cart — shoppers don’t have to click anything: “add it” (or naming a product from the conversation) makes the assistant put the product into the WooCommerce cart, confirm after the store accepts it, and offer a “Go to checkout” button. Ambiguous requests get a clarifying choice, never a guess; you control which products the AI may add, per product.
• Upsell and cross-sell — suggests complementary products inside the conversation.
• Multilingual, for real — replies in whichever language the shopper writes, detected per message (romanized Urdu/Hindi/Arabic included). The assistant’s fixed messages are translated automatically, so an English catalog can serve shoppers in any language.
• Human handover — hands the conversation to a live chat agent when a person is needed.
• AI FAQ on product pages (2.9.0) — product FAQs generated from the questions shoppers actually asked your assistant, approved by you in the dashboard, rendered on the product page server-side with FAQPage schema — so ChatGPT, Perplexity and Google can read and quote them. Theme removed the hooks? Use the [rynex_faq] shortcode.
• Agent readiness out of the box — your site automatically serves the discovery files the AI ecosystem looks for (llms.txt, llms-full.txt, an A2A agent card, auth.md, an API catalog) and declares Content-Signal in robots.txt, so ChatGPT, Claude, Perplexity and shopping agents can find and read your store.
• Revenue attribution — reports which conversations produced orders, not just how many chats happened.

No API keys. No surprise AI bills.

Most free AI chatbot plugins are “bring your own key”: you create an OpenAI or Google account, generate an API key, paste it into WordPress, and then pay the AI provider per message — with a bill that grows with your traffic, and a bot that stops answering when a budget cap is hit. Rynex is hosted: there is no key to create, AI usage is included in your plan, your monthly cost is predictable, and the assistant never disappears from your storefront mid-conversation.

How the free plans actually compare:

• Setup — Rynex: install, press Connect, done. BYO-key chatbots: create an OpenAI/Google account, generate a key, paste it in, keep it valid.
• Who pays for AI — Rynex: included in your plan, fixed monthly cost. BYO-key: you, per message, on a separate AI-provider invoice that grows with traffic.
• When the limit is hit — Rynex: nothing switches off and nothing extra is charged — the assistant keeps answering. BYO-key with a budget cap: the bot can vanish from your storefront mid-day.
• What you can measure — Rynex: attributed orders and revenue per conversation. Typical chatbots: message counts.

On-site AI recommendations (“You may also like”)

Beyond the chat, Rynex can embed an AI-picked product block natively on your product pages — personalized from what each shopper browses, styled to match your theme automatically, positioned by drag & drop from the dashboard. Clicks on the block flow into the same revenue attribution as the chat.

Product FAQs for your whole catalog

Every product page should answer the questions shoppers actually ask. Writing those answers for a 1,200-product catalog by hand is why most stores never do it.

The same connection also generates a product FAQ for each item in your catalog and renders it on the product page as a clean accordion plus valid FAQPage structured data — server-side, so Googlebot, GPTBot and PerplexityBot read it without running JavaScript.

Where the questions come from. The FAQ is written from your own product data — title, description, attributes, categories. If shoppers have already chatted on that product page, their real questions are used too, so the FAQ answers what people actually asked instead of what a template guessed. It works from day one on a store with zero traffic.

How it works

1. Press Connect to Rynex (free account, no credit card, no AI provider key).
2. Open Product Content in your Rynex dashboard, select products, and generate.
3. Review and edit the drafts, then publish the ones you like.
4. Published FAQs appear on the matching product page automatically, with FAQPage schema.

Generation and review happen in the Rynex dashboard, not in WP admin. This plugin connects your catalog and renders the published result on your storefront.

What the free plan covers: 50 product FAQs when you start, then 10 more each month. That is enough to cover your best sellers and see the result on real product pages; larger catalogs need a paid plan. There is no separate AI bill and no API key to bring — generation runs on Rynex.

You stay in control. Nothing is published automatically: every FAQ is a draft until you approve it. You can edit any question or answer, unpublish at any time, and turn the whole display off with one switch. If your theme removed the standard WooCommerce product hooks, place the [rynex_faq] shortcode wherever you want the block.

No duplicate schema. If the chat widget is on the same page, it detects the server-rendered block and does not emit a second FAQPage — so you never ship two competing schemas to search engines.

No WooCommerce? It still works. On a plain WordPress site Rynex runs as an AI chatbot for WordPress: press Connect and the assistant answers from your own content — your home page is indexed automatically, and you add pages, posts, PDFs or plain text from your Rynex dashboard. Product recommendations, add to cart, the on-site recommendations block and revenue attribution need WooCommerce; install it later and one button turns them on.

Requirements: HTTPS and WordPress 6.2+, with the WordPress REST API reachable. WooCommerce stores additionally need WooCommerce 8.0+; pretty permalinks are recommended but not required, and subdirectory installs connect too.

External services

This plugin connects your store to the Rynex platform (api.rynex.io), operated by Rynex. It is required for everything the plugin does — without a Rynex connection the plugin is inert.

What is sent and when:

• Product FAQ generation (dashboard-side): FAQs are generated by Rynex from the catalog data your store already synced on connect (product title, description, attributes, categories) and, where they exist, the questions shoppers asked the assistant on that product page. Generation is started by you from the Rynex dashboard; this plugin sends nothing extra for it and no product content leaves your site beyond the catalog sync described below.
• Product FAQ display (2.9.0+, WooCommerce stores): when you publish a product FAQ from your Rynex dashboard, the plugin fetches that FAQ content from Rynex (authenticated with the plugin secret) and caches it locally, so it can render the FAQ and its FAQPage schema on the matching product page. Only product IDs are sent; you can turn the display off with the “Show AI FAQ on product pages” switch.
• On connect (WooCommerce store): your store URL, a WooCommerce REST API key the plugin creates for Rynex (read/write — used to sync your catalog and register webhooks), your WordPress/WooCommerce version numbers, and (2.7.1+) the connecting administrator’s email address (falling back to the site admin email) — used as your Rynex account contact so Rynex can reach you about your assistant. Service communication only; it is never sold or shared. Since 2.12.0 the connect request also carries your site’s REST API base URL, whether permalinks are plain or pretty, and the HTTP status your own REST API returned to a local check — diagnostics that let Rynex tell you exactly why a connection failed. Since 2.13.0 it also carries your site’s language setting (the WordPress locale, e.g. de_DE) so the assistant’s default proactive message is created in your language.
• On connect (WordPress site without WooCommerce): your site URL, your site’s REST API base URL, your WordPress and plugin version numbers, the administrator email as above, the same permalink/REST diagnostics as above (2.12.0+), your site language (2.13.0+), and a one-time pairing token — the plugin publishes only the token’s SHA-256 hash at /wp-json/rynex/v1/pair-verify for five minutes so Rynex can verify you control the site. No API key is created. Rynex then fetches your home page once to seed the assistant’s knowledge.
• While connected (both modes): your site loads the Rynex widget script; conversations are processed by Rynex to power the assistant and analytics. The widget stores an anonymous visitor ID in the browser and sends it with conversation events; on pages it recognizes as product pages it also reports the page URL and product identifier, so Rynex can personalize the assistant and the optional on-site “You may also like” recommendations. Setting ShopAgentConfig.trackingConsent = false disables both the stored ID and the browsing signal. WooCommerce stores only: order and product webhooks are sent to Rynex for catalog freshness and revenue attribution.
• Visitor audiences (both modes): to let you show a welcome message, coupon or other widget screen only to certain visitors, the widget also reports page views and widget opens (page URL, referrer, UTM parameters, device type, language) together with the anonymous visitor ID and a session ID stored in the browser under shopagent_visitor_id and shopagent_session_id. From this Rynex derives five coarse labels across visits within 30 days — returning visitor, opened the widget before, chatted before, came from a paid campaign, browsed 3+ products — and returns only those labels to the widget; no browsing history leaves Rynex. Labels are computed only when one of your widget rules targets an audience. Setting ShopAgentConfig.trackingConsent = false (or calling window.ShopAgent.optOut()) sends page views and widget opens without any visitor or session identifier (aggregate counts only) and disables audience labels for that shopper; if a shopper withdraws consent later, the widget dispatches the shopagent:consent-changed event and Rynex erases the behavioural data derived from that visitor ID (product views, interest profile, visitor/session identifiers on traffic events). Conversations are kept for service delivery. Because this is behavioural targeting, describe it in your privacy policy and wire your consent tool to the setting above.
• Signed-in shoppers (2.11.0+, both modes): when a logged-in customer opens a page, the widget tag carries a signed customer token (the WooCommerce/WordPress customer ID, e-mail address and name) that expires after 24 hours; it is sent to Rynex with the shopper’s chat requests so your inbox can show who is talking. Nothing is emitted for guests.
• Store admins browsing the storefront (2.13.0+, both modes): when a logged-in user who can manage the plugin (manage_woocommerce, or manage_options without WooCommerce) views a page, the widget tag carries data-internal="1" and the widget marks its page-view and widget-open telemetry as internal, so your own visits are excluded from the traffic statistics Rynex computes. The flag identifies no person — it is a boolean on events that already exist. For these requests the plugin asks page caches not to store the page (DONOTCACHEPAGE, plus no-cache headers sent early in the request) so the flag is not served to a shopper from a cached copy; caching layers that ignore both signals for logged-in users are outside the plugin’s control.
• On the settings page: a status check identifying your store; from 2.7.1 it also carries the administrator email above so existing connections gain an account contact without reconnecting, and from 2.13.0 your site language. The response includes your Rynex plan and trial end date, which the settings page shows.
• Event bridge (2.6.0+, both modes): Rynex delivers signed event notifications (contact captured, order attributed, handover requested…) back to your site’s REST API at /wp-json/rynex/v1/events so other plugins can react via WordPress hooks. Deliveries are HMAC-signed and contain no message content. You can pause this any time from the settings page.

Rynex terms of service: https://rynex.io/terms — privacy policy: https://rynex.io/privacy

Developer hooks

Since 2.6.0 the plugin fires WordPress actions for Rynex events, so automation plugins (FluentCRM, Uncanny Automator…) and custom code can react to what happens in the assistant — no polling, no API key.

Add a captured shopper to FluentCRM in three lines:

add_action( 'rynex_contact_captured', function ( $data, $meta ) {
    FluentCrmApi( 'contacts' )->createOrUpdate( array( 'email' => $data['email'] ) );
}, 10, 2 );

Every event also fires the generic hook: add_action( 'rynex_event', fn( $type, $data, $meta ) => ..., 10, 3 ). Event types: contact.captured, consent.granted, consent.revoked, order.attributed, order.reversed, conversation.completed, handover.requested, handover.completed, journey.email_sent. Deliveries are HMAC-signed by Rynex and verified before any hook fires; $meta['delivery_id'] deduplicates retries. Pause the bridge any time from the settings page.