| 开发者 | aivastark |
|---|---|
| 更新时间 | 2026年11月9日 19:52 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
[aivastark key="..."] shortcode on individual pages.
Run it without leaving WordPress. Click Connect once to securely link your site to your Aivastark project. Aivastark then opens as a full-screen app inside wp-admin, with its own navigation: the Widget editor, the Inbox, the Knowledge base, Leads, Analytics, AI agent settings and more, already signed in. No second login each time.
Decide where it shows. Display rules choose the pages (by type, by page or by URL path), the devices, the visitors (everyone, logged out, logged in, or not certain roles) and how early the widget loads, all without code.
AI chatbot for WooCommerce
Connect your WooCommerce store from the Aivastark dashboard: enter your store URL, then approve the connection in your own WordPress admin. There are no API keys to copy. The chatbot then answers from live store data:
https://www.aivastark.com/widget.js and chat conversations are processed by the Aivastark backend. Full disclosure of every endpoint and the data sent is in the External services section below.
By installing this plugin you agree to the Aivastark Terms of Service and Privacy Policy.
.zip file to /wp-content/plugins/ or install it via Plugins → Add New → Upload Plugin.[aivastark key="YOUR_WIDGET_KEY"] where you want the widget to load.Yes. The Free plan costs nothing, needs no card and includes 300 credits a month, with the chat widget, knowledge base and 80+ languages. Paid plans are Solo ($12), Starter ($39), Growth ($129) and Scale ($319) a month, each with a 7-day trial (card required, cancel before day 8 at no cost). Plans include monthly credits, not per-conversation or per-resolution fees. See pricing.
Yes. Connect your store from the Aivastark dashboard by entering its URL and approving the connection in your WordPress admin. The agent then answers product, stock and order-status questions from live WooCommerce data. This plugin puts the chat on your site; the WooCommerce connection gives the agent your store data. Most stores use both.
Yes. A customer gives the order number and the billing email used at checkout, and the agent reads the order's status. Asking for both keeps one customer from looking up another's order.
Yes, on Solo and above. Switch on human handoff and the agent passes the chat to your team when the customer asks for a person, sounds upset or still isn't helped. You reply from the Aivastark inbox, inside wp-admin or in the dashboard.
Yes, on Starter and above. The same agent and knowledge base answer WhatsApp, Instagram, Facebook Messenger, Telegram and email, and every conversation lands in the same inbox as your website chats.
80+ languages, on every plan. The agent detects the language from the visitor's first message and replies in it, from Arabic, Spanish and French to German and English, in the script the customer used (Arabic script or Arabizi, Urdu script or Roman Urdu).
No. Version 2.0 collapsed the old four-field config into a single Widget Key. Everything else (API endpoint, project settings, theme) is resolved automatically from the key.
No. The AI is included in your Aivastark plan and paid for in credits, so there is no API key to bring and no separate AI bill. Aivastark picks and monitors the model behind standard answers; from Starter you can switch a project to one of seven others, including Claude, Gemini and GPT models.
Yes. It answers from your pages, files and FAQs on any WordPress site: clinics, law firms, real estate agencies, SaaS documentation and more. From Starter it can also book meetings into Google Calendar or Cal.com. The WooCommerce tools only switch on when you connect a store.
It covers the front line: the AI answers first and your team handles the rest from one inbox. From Starter you also get tickets with SLA targets, and tickets can sync to Zendesk, HubSpot, Freshdesk, Salesforce or ClickUp. There is no phone line, so if you need a full helpdesk with calls, keep it and connect Aivastark to it.
Yes. The agent captures name, email and phone in the chat, and from Solo it sends each new lead to your own endpoint or to HubSpot by webhook, with automatic retries. Leads also show under Aivastark → Leads inside wp-admin.
No, your data isn't used for training. It is isolated to your organisation, and Aivastark doesn't train or fine-tune AI models on it. Connections use TLS, data is encrypted at rest, and a GDPR Data Processing Agreement is included on every plan. There is no third-party security audit or certification yet.
Post in this plugin's support forum on WordPress.org and we'll answer there, or contact us at aivastark.com/contact.
Create a free account at aivastark.com, create a project, and copy the Widget Key from the Integrations page in your dashboard.
The widget script is served from the Aivastark CDN (https://www.aivastark.com/widget.js) by default. You can self-host by filtering aivastark_widget_script_url.
Yes. Add this to your theme or a custom plugin: add_filter( 'aivastark_widget_script_url', function () { return 'https://your-cdn.com/widget.js'; } );
No. The widget script is registered with WordPress, loaded in the footer, and never blocks rendering. If you want it out of the first page load entirely, Aivastark → Display rules → When it loads can start it after a delay or on the visitor's first scroll, tap, click or key press.
By default: only conversation messages typed by visitors who open the widget, plus the Widget Key (to identify your project) and the visitor's session ID. No page content, no cookies on the host site, and no visitor tracking beyond what is needed for the chat session itself. If you switch on Know your logged-in visitors (off by default, see below), the logged-in user's WordPress user ID, display name, email address and role are also included. See the External services section for the full breakdown.
An optional setting — off unless you turn it on — that tells the assistant who is signed in, so it can greet them by name, recognize them across devices, and stop asking for details your site already has. Turn it on from Aivastark → Home (one click) or Aivastark → Settings. Nothing is sent for visitors who are not logged in. The values are the user's WordPress ID, display name, email address and primary role. Two things to know before enabling it:
aivastark_widget_user_context filter (for example to add a membership tier, subscription plan, or lifetime value).
Yes. The widget config is inlined per-request; caching plugins that preserve <script> tags in wp_footer are fully compatible.
When Know your logged-in visitors is on and a logged-in user is being served, the plugin also defines DONOTCACHEPAGE for that request, so a page containing one person's name can never be cached and served to somebody else. WP Rocket, LiteSpeed Cache, W3 Total Cache and WP Super Cache all honour this. Anonymous page views are untouched, so your page cache keeps working normally.
Yes. Go to Aivastark → Home and click Connect, approve the connection in your Aivastark account (one time), then open Aivastark → Widget editor. The full editor (Content, Style, AI, Designer) loads right inside wp-admin and your changes save to your project. The Inbox, Knowledge base, Leads, Analytics and the other sections in the app's menu work the same way. You can disconnect anytime from Home or Settings.
Aivastark opens full screen so the inbox and editor get the room they need. Click the menu button at the top left to bring WordPress's menu back; WordPress remembers your choice.
Yes, in Aivastark → Display rules: every page, only on chosen pages, or everywhere except chosen pages. Choose by page type (home page, posts, pages, archives, search, 404, and WooCommerce shop, product, cart, checkout and account pages when WooCommerce is active), by specific page, or by URL path with * as a wildcard. The same screen limits it to desktop or phones, to logged-out or logged-in visitors, hides it from chosen roles, and sets when it loads. Developers can overrule any decision with the aivastark_widget_should_render filter.
No. Connecting is optional — it adds the in-WordPress app (editor, inbox, knowledge base, leads, analytics) and Knowledge sync. Display rules work without it. If you prefer, paste your Widget Key in Aivastark → Settings (or use the shortcode) and skip Connect entirely; the widget works exactly as before.
Use Plugins → Delete in WordPress. The bundled uninstall.php removes the plugin's options (aivastark_widget_options, and if you connected, aivastark_widget_secret with the scoped token and aivastark_widget_signing_secret) and any queued Knowledge sync event. No tables, no extra rows. Disconnecting first also revokes the token on the server.
aivastark_widget_should_render filter.aivastark_widget_capability filter for who may open the app.DONOTCACHEPAGE, so a page containing one person's details can never be cached and served to another visitor. Anonymous page views still cache normally.aivastark_widget_user_context filter, so developers can add a membership tier, subscription plan, or any custom attributes to what the assistant knows.includes/ and admin/ files. Front-end behavior is unchanged — the [aivastark] shortcode and site-wide rendering work exactly as in 2.1.x, and an unconnected site behaves identically to before.currentColor resolved to the theme's text colour. Wrapped the entire widget in a Shadow DOM so host-page styles can no longer reach widget elements. The widget now renders identically across WordPress, Shopify, and bare HTML pages.WIDGET_SKINS const had been initialised, throwing a temporal-dead-zone ReferenceError ("Cannot access 'se' before initialization") that aborted the rest of the customisation. The apply call is now deferred to a microtask, so it runs after every const/function declaration in the IIFE has initialised.wp_footer priority 100, which fires after WordPress prints footer scripts at priority 20, so the script was enqueued too late to render. Moved the auto-enqueue to wp_enqueue_scripts. The shortcode form was unaffected.Plugin URI (now aivastark.com/wordpress-plugin) from Author URI to satisfy WordPress.org submission requirements. No functional changes.uninstall.php to clean up the plugin's option when deleted.$_POST handling on the settings page (unslash + sanitize before any comparison or use).wp_enqueue_script and wp_add_inline_script for WP.org compliance.aivastark_widget_script_url filter for self-hosted widget scripts.aivastark-widget).widget.js — the CDN copy is now always used by default.