Chatessa is a live chat that answers with AI when your team is offline and learns from every conversation. This plugin embeds the Chatessa widget on your WordPress site and - for a true enterprise integration - can:<\/p>\n\n
user_hash<\/code>), computed on your server so it cannot be forged in the browser.<\/li>\n- WooCommerce context<\/strong> \u2013 on login, the plugin sends the customer's order count and lifetime value to Chatessa so your agents see who they're talking to.<\/li>\n
- Consent gating (GDPR)<\/strong> \u2013 optionally load the widget only after your cookie-consent banner is accepted.<\/li>\n
- Inbound webhooks<\/strong> \u2013 receive Chatessa events (new leads, escalations) in WordPress and react via the
chatessa_webhook<\/code> action hook (HMAC-verified).<\/li>\n- Performance-first<\/strong> \u2013 the widget script loads asynchronously and never blocks rendering.<\/li>\n<\/ul>\n\n
The widget key is public by design (it lives in client HTML). The API key and identity secret are server-to-server only and are never printed into the page.<\/p>\n\n
External services<\/h3>\n\n
This plugin is a client for Chatessa<\/strong>, a third-party hosted live-chat and AI\nchatbot service. The plugin does not work on its own: a Chatessa account is\nrequired, and the chat itself runs on Chatessa's servers. By installing this\nplugin you are sending the data listed below to that service.<\/p>\n\nService provider: Chatessa (https:\/\/chatessa.com)\nTerms of Service: https:\/\/chatessa.com\/terms-of-service\nPrivacy Policy: https:\/\/chatessa.com\/privacy-policy<\/p>\n\n
By default the plugin talks to the Chatessa cloud at https:\/\/chatessa.com<\/code> and\n https:\/\/api.chatessa.com. If you self-host Chatessa you can point the plugin at\nyour own installation under Settings \u2192 Chatessa \u2192 Advanced<\/strong>, in which case the\ndata below goes to your own server instead.<\/p>\n\nThe plugin contacts the service in these situations, and only these:<\/p>\n\n
\nLoading the chat widget (every page view, front end)<\/strong>\nThe widget script widget.js<\/code> is loaded from the Chatessa app host so the chat\ncan render. As with any hosted chat widget, the visitor's browser therefore\ncontacts Chatessa directly, which makes the visitor's IP address, user agent\nand the page URL visible to the service. Chat messages the visitor types are\nsent to Chatessa to be answered and to be shown to your agents.\nNot loaded at all when the plugin is disabled, when no widget key is set, or -\nif you enable consent gating - until your cookie-consent cookie is present.<\/em><\/p><\/li>\nConnecting your site (once, when an administrator clicks \"Connect\")<\/strong>\nSends your site's host name and site title so Chatessa can provision a widget\nkey restricted to your domain and return it to this plugin.<\/p><\/li>\nCompleting the \"Connect with Chatessa\" authorization (once, on approval)<\/strong>\nExchanges the single-use authorization code returned by Chatessa for your\nworkspace's widget key, API key and identity secret.<\/p><\/li>\nIdentifying a logged-in user to your agents (optional, on each login)<\/strong>\nOnly when \"Secure identity\" is enabled. The user's WordPress user ID, email\naddress and display name are signed on your server and passed to the widget so\nyour agents can see a verified identity instead of an anonymous visitor.<\/p><\/li>\nSending WooCommerce customer context (optional, on each login)<\/strong>\nOnly when \"WooCommerce context\" is enabled and WooCommerce is active. Sends the\ncustomer's email address, display name, order count, lifetime value and last\norder (number, date, total, status) so agents can see purchase history while\nchatting.<\/p><\/li>\n<\/ol>\n\nItems 4 and 5 are switched off by unchecking them on the plugin's settings screen;\nitems 1-3 are inherent to using the service.<\/p>\n\n\n
\n- Upload the
chattora-live-chat-ai-chatbot<\/code> folder to \/wp-content\/plugins\/<\/code>, or install via the Plugins screen.<\/li>\n- Activate the plugin.<\/li>\n
- Go to Settings \u2192 Chatessa<\/strong>.<\/li>\n
- Enter your API URL<\/strong> (e.g.
https:\/\/api.chatessa.com<\/code>) and an API key<\/strong> (create one in Chatessa under Settings \u2192 Developer), then click Connect<\/strong>.<\/li>\n- Done - the chat widget is now live on your site.<\/li>\n<\/ol>\n\n
You can also skip Connect and paste a Widget key<\/strong> manually.<\/p>\n\n\n\nDo I need a Chatessa account?<\/h3><\/dt>\nYes. Create a workspace at chatessa.com, then generate an API key to connect.<\/p><\/dd>\n
Is the identity verification secure?<\/h3><\/dt>\nYes. The user_hash<\/code> is an HMAC-SHA256 of the user's id AND email together, signed on your server with a secret shared only server-to-server. A visitor cannot impersonate another user - or swap in a different email address - from the browser.<\/p><\/dd>\nDoes it work with WooCommerce?<\/h3><\/dt>\nYes. When enabled, order count and lifetime value are sent to Chatessa on login.<\/p><\/dd>\n
Will it slow down my site?<\/h3><\/dt>\nNo. The widget script is loaded asynchronously and is fully isolated (Shadow DOM).<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.2<\/h4>\n\n\n- Documented every third-party (Chatessa) service call in the readme, including exactly what data is sent, when, and how to switch the optional ones off, with links to the service's Terms of Service and Privacy Policy.<\/li>\n
- Corrected the plugin's
Contributors<\/code> list.<\/li>\n<\/ul>\n\n1.0.1<\/h4>\n\n\n- Removed the self-hosted update checker (
pre_set_site_transient_update_plugins<\/code> \/ plugins_api<\/code>) and the \"License key\" setting - WordPress.org hosts updates for this plugin directly, and hosted plugins may not ship their own updater.<\/li>\n- Fixed the plugin's text domain to match its WordPress.org slug.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release: one-click Connect, secure identity (HMAC), WooCommerce context, consent gating, async loading, multisite-safe uninstall.<\/li>\n<\/ul>","raw_excerpt":"Add the Chatessa live chat + AI chatbot to your site in one click, with secure user identity and WooCommerce customer context.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/337845","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=337845"}],"author":[{"embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/platkadigital"}],"wp:attachment":[{"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=337845"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=337845"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=337845"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=337845"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=337845"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/azb.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=337845"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}