{"id":11263,"date":"2026-05-28T20:29:46","date_gmt":"2026-05-28T12:29:46","guid":{"rendered":"https:\/\/aeosub.com\/global-ai-chat\/"},"modified":"2026-05-28T20:29:46","modified_gmt":"2026-05-28T12:29:46","slug":"global-ai-chat","status":"publish","type":"post","link":"https:\/\/aeosub.com\/zh\/global-ai-chat\/","title":{"rendered":"Global AI Chat"},"content":{"rendered":"
\"Global<\/div>\n
\n\n\n\n\n\n\n\n
Developer<\/th>\nGlobal AI<\/a><\/td>\n<\/tr>\n
Version<\/th>\nv3.6.7<\/td>\n<\/tr>\n
Active Installs<\/th>\n0 +<\/td>\n<\/tr>\n
Requires \/ Tested<\/th>\n6.0 \/ 7.0<\/td>\n<\/tr>\n
Last Updated<\/th>\n2026-05-28 12:15pm GMT<\/td>\n<\/tr>\n
Official Link<\/th>\nView Details \u2192<\/a><\/td>\n<\/tr>\n<\/table><\/div>\n
AI-powered chat widget for WordPress using OpenAI. Bring your own OpenAI key, fully functional out of the box, no license required.<\/div>\n

Global AI Chat adds an AI-powered chat widget to your WordPress site. Visitors interact with a chatbot backed by OpenAI’s models; you use your own OpenAI account (and are billed directly by OpenAI for the usage).<\/p>\n

All features are free and fully functional.<\/strong> The plugin does not lock, limit, or time-restrict any built-in functionality.<\/p>\n

Features included:<\/p>\n

    \n
  • Floating chat widget with customizable colours, icons, position and animation<\/li>\n
  • Shortcode [growthai_chat]<\/code> to embed the chat inline on any page<\/li>\n
  • Gutenberg block, Elementor widget, Divi module, Beaver Builder module, WPBakery element<\/li>\n
  • One agent profile (SDR, Support or FAQ) with custom prompt<\/li>\n
  • Lead collection tool calls (name, email, phone, company and custom fields)<\/li>\n
  • Visitor request for human contact triggers an admin notification (no live takeover in Free)<\/li>\n
  • GDPR-ready: optional cookie consent banner and opt-in uninstall data deletion<\/li>\n
  • Multi-language chat \u2014 widget auto-detects the visitor’s browser locale<\/li>\n<\/ul>\n

    Want multi-agent setup, live chat takeover from wp-admin, page\/post auto-sync, Google Calendar booking, webhooks, AI prompt generator, mobile app, managed tokens, auto-updates or analytics?<\/strong> The companion Pro addon is distributed separately at https:\/\/globalai.software\/. It layers extra UI and SaaS-backed services on top of the free plugin without replacing it \u2014 if you ever deactivate Pro, the free plugin keeps working.<\/p>\n

    External services<\/h3>\n

    This plugin relies on one<\/strong> third-party service: the OpenAI API. No other external endpoint is contacted by the free plugin.<\/p>\n

    OpenAI API (required)<\/h4>\n
      \n
    • What it is:<\/strong> OpenAI provides the language model that generates chat replies and, when you upload knowledge-base documents, runs the file search against them.<\/li>\n
    • What is sent:<\/strong> Every chat message the visitor submits, plus the system prompt your agent is configured with, is sent to https:\/\/api.openai.com\/v1\/responses<\/code> using your own API key. When you upload training documents, the file bytes are sent to https:\/\/api.openai.com\/v1\/files<\/code> and registered with https:\/\/api.openai.com\/v1\/vector_stores<\/code> so the agent can search them.<\/li>\n
    • When:<\/strong> On every user message (chat completion) and only when an admin manually uploads\/deletes a knowledge-base document (vector store).<\/li>\n
    • Terms of service:<\/strong> https:\/\/openai.com\/policies\/terms-of-use<\/li>\n
    • Privacy policy:<\/strong> https:\/\/openai.com\/policies\/privacy-policy<\/li>\n<\/ul>\n

      Not contacted by this free plugin<\/h4>\n

      The companion Pro addon (separate download, not on wp.org) introduces additional endpoints under https:\/\/saas.globalai.software\/<\/code> for license verification, managed token billing, mobile-app push notifications, plugin auto-updates, Google Calendar OAuth, outbound webhooks, page\/post auto-sync, and the AI prompt generator. None of those endpoints are reached from this free plugin’s code \u2014 they are documented here only so admins know what changes if they later install the Pro addon.<\/p>\n

      Security<\/h3>\n

      Visitor session token (`session_id`)<\/h4>\n

      Every chat conversation is bound to a session_id<\/code> token generated client-side, in the visitor’s browser<\/strong>, using window.crypto.getRandomValues<\/code> (a 128-bit cryptographically random value rendered as 32 hex characters with the prefix gai_<\/code>). The token is stored in localStorage<\/code> after the visitor accepts the cookie consent banner; without consent, an in-memory ephemeral token is used and discarded when the tab closes.<\/p>\n

      The session_id<\/code> is the access key for the chat REST endpoints (\/wp-json\/growthai\/v1\/chat<\/code>, \/wp-json\/growthai\/v1\/live-chat\/poll<\/code>). These endpoints are intentionally public (permission_callback => __return_true<\/code>) so that anonymous site visitors can chat without needing a WordPress account \u2014 knowing the token is what authorises the request, the same security model used by mainstream chat \/ support widgets (Crisp, Tawk, Intercom).<\/p>\n

      Implications:<\/p>\n

        \n
      • The token is not<\/strong> derived from the IP, User-Agent, cookies the server sets, or any sequential \/ predictable scheme. A third party cannot guess another visitor’s token.<\/li>\n
      • The plugin never logs full session_id<\/code> values in plaintext outside the database row that owns the conversation.<\/li>\n
      • If the visitor clears their browser storage, the next page load gets a fresh token and a fresh conversation.<\/li>\n
      • Old browsers without the Web Crypto API fall back to Math.random()<\/code> \u2014 a worse entropy source. We surface this in the JS for transparency; if your audience relies on legacy browsers, factor that into your threat model.<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

        AI-powered chat widget for WordPress using OpenAI. Bring your own OpenAI key, fully functional out of the box, no license required.<\/p>","protected":false},"author":1,"featured_media":9317,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[252],"tags":[550,1456,556,616,558,555],"class_list":["post-11263","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-trends","tag-ai","tag-assistant","tag-chat","tag-chatbot","tag-openai","tag-wordpress-plugin"],"_links":{"self":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11263","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/comments?post=11263"}],"version-history":[{"count":0,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/posts\/11263\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media\/9317"}],"wp:attachment":[{"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/media?parent=11263"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/categories?post=11263"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/aeosub.com\/zh\/wp-json\/wp\/v2\/tags?post=11263"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}