Vegax Support

Description

Vegax Support puts a support agent on your WooCommerce store. It reads your product catalogue and policy pages, so it answers from what you actually sell and how you actually do business — never on guesses.

• Answers product, price, stock, shipping and returns questions.
• Lets a customer check their own order status right in the chat (WISMO).
• Replies in the language the customer writes in.
• Chat bubble appears on your storefront without editing your theme.
• Works with WooCommerce High-Performance Order Storage and the legacy post tables.

The Vegax service is required. The plugin itself is open-source (GPL) and is never locked or broken: you see the settings screen, the connect screen, the notices and the uninstall flow with or without a subscription. Only the answering engine lives outside your site.

A 7-day free trial is included. After the trial you can choose a plan to keep the service running. See vegaxclaw.com/woocommerce for current plans and pricing.

External services

This plugin relies on the Vegax service, a third-party hosted service, to generate support answers and order-status replies.

• Service: Vegax — https://vegaxclaw.com
• Base endpoint: https://office.vegaxclaw.com
• Service terms of use: https://vegaxclaw.com/terms
• Privacy policy: https://vegaxclaw.com/privacy

What the plugin sends and when

Each request identifies the store it belongs to — the two connection requests use the site URL instead, since the store is not connected yet. The catalogue, heartbeat and token-refresh payloads also carry the plugin version, and the catalogue, heartbeat and order-status payloads carry the time they were sent. None of those fields adds personal data.

The plugin contacts the Vegax service in two situations. (1) When an administrator starts the connection — pressing Connect with Vegax, or sending a one-time pairing code — the plugin asks the service for this store’s credentials. That call is made by the administrator, through an action protected by a capability check and a nonce, and it is what the connection itself needs. (2) Once the store is connected and the data-sharing consent checkbox on the settings screen is ticked, the plugin sends the data listed below. Connecting ticks that box for you; untick it, or press Disconnect, and no further data request leaves your site — the only remaining calls are those two connection requests, and they happen only when an administrator triggers them (Disconnect also deletes the stored credentials and removes every scheduled job).

• Catalogue sync (separate from the heartbeat, triggered by an administrator or by the daily sync cron — never on heartbeat): product id, name, SKU, type, prices (regular, sale and current), on-sale flag, stock status, in-stock flag, stock quantity, categories, product link, image link, description (up to 600 characters: the short description, or the start of the full description when the short one is empty), attributes, weight, dimensions, variant data (options, price, sale price, stock) for up to 12 variations together with the total number of variations, plus the store key, the platform (woocommerce), the product count (with a note of how it was counted) and a site metadata block (site name, site URL, currency, locale, timezone, WooCommerce version, WordPress version, HPOS flag).
• Policy pages and custom rules (shipping, returns, warranty and similar—named pages found on your own site), plus the FAQs and store rules the administrator types into the settings, as plain text: sent on the same sync.
• Order status events (order number, status, status label, order date, total, currency, item count, shipped flag, shipment tracking numbers, providers and URLs, plus the ship date when the tracking entry carries one) and a hashed customer e-mail: sent when an order status changes. The clear-text e-mail is only sent if the administrator enables the “Send the customer e-mail with order events” option.
• Daily heartbeat (a small status payload sent once a day): store key, site URL, site name, WordPress version, WooCommerce version, PHP version, currency, HPOS flag, order-lookup enabled flag, widget enabled flag, product count.
• Token refresh (only for stores connected with the expiring-token connection, only when the access token is close to expiry, and only while the data-sharing consent checkbox is ticked): the store key, the refresh token and the plugin version, so the service can issue a fresh token pair. This runs in the background and is never triggered by a shopper’s page view.
• Pairing request (only when the administrator uses the one-time pairing code or the Connect with Vegax authorization): the site URL, the one-time code and the plugin version; the Connect with Vegax authorization also sends the OAuth state value.
• Identity token (only when the administrator switches on Identity verification, and only for a signed-in customer): a short-lived signed token carrying the customer id and the store key, and an expiry. It is a signature, not personal data — no name, e-mail or address is included.

The storefront chat widget script is loaded from the Vegax service so replies can be generated. It is only loaded when (a) the widget is enabled in the settings, (b) the store is connected to the service, and (c) the data-sharing consent checkbox is ticked. Turning consent off removes the script from the storefront on the next page view.

What is never sent

Customer names, addresses, phone numbers, order addresses and payment details are never transmitted. Your WordPress or WooCommerce credentials are never transmitted. No order data leaves your store in bulk: an order lookup answers either the single order a customer identified (when they supply the order number) or, when they only give the e-mail address they ordered with, at most the five most recent orders for that address.

Developers

The plugin exposes these filters, so a site can adapt the integration without editing the plugin:

• vegax_ais_widget_tag_attributes — change the attributes printed on the chat widget tag.
• vegax_ais_widget_should_render — decide whether the widget is printed on the current request.
• vegax_ais_widget_on_checkout — print (or keep away from) the widget on the checkout page.
• vegax_ais_knowledge_product — add, rename or drop fields for a product in the catalogue sync.
• vegax_ais_heartbeat_payload — add or remove fields in the daily heartbeat.
• vegax_ais_order_event_payload — add or remove fields in the order-status event.
• vegax_ais_tracking_items — change the shipment tracking items read from an order.