PROXYAI CHAT ASSISTANT
ProxyAI Chat Assistant translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what ProxyAI Chat Assistant does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Hosted AI chat assistant that answers visitor questions using the site’s published posts/pages/products (when the Knowledge add-on is active).
- Human handoff capability: conversations can be passed to a human agent via a shared inbox in wp-admin.
- WooCommerce compatibility: on WooCommerce stores, the assistant can add items to the shopper’s cart in the visitor’s browser session and link to checkout (cart bridge can be disabled via `proxyai_enable_woo_cart`).
- Frontend script injection on page views: visitors load chat widget script from `https://www.proxyai.app/embed.js` (and `woo-cart.js` on WooCommerce stores); support-ticket pages additionally load `ticket-embed.js`.
- Optional support-ticket form integration: a support-ticket block/shortcode renders a ticket form and ticket history in a dialog; it requires the Helpdesk add-on to be active and only signed-in customers can open tickets.
- Order lookup behavior (WooCommerce): when a visitor asks about an order, ProxyAI calls back to the site with an order number and billing email; the plugin answers only if they match an order on the site and returns order details (number/status/date/total/currency/line items/tracking).
- Visitor identity tokenization for logged-in users (Helpdesk add-on only): on pages with the assistant/ticket form, the plugin places a signed token containing the user’s ID/email/display name for the browser to pass to ProxyAI; logged-out visitors receive no token.
Distinctive features
Hosted AI chat assistant that answers visitor questions using the site’s published posts/pages/products (when the Knowledge add-on is active). Human handoff capability: conversations can be passed to a human agent via a shared inbox in wp-admin. WooCommerce compatibility: on WooCommerce stores, the assistant can add items to the shopper’s cart in the visitor’s browser session and link to checkout (cart bridge can be disabled via `proxyai_enable_woo_cart`). Frontend script injection on page views: visitors load chat widget script from `https://www.proxyai.app/embed.js` (and `woo-cart.js` on WooCommerce stores); support-ticket pages additionally load `ticket-embed.js`. Optional support-ticket form integration: a support-ticket block/shortcode renders a ticket form and ticket history in a dialog; it requires the Helpdesk add-on to be active and only signed-in customers can open tickets. Order lookup behavior (WooCommerce): when a visitor asks about an order, ProxyAI calls back to the site with an order number and billing email; the plugin answers only if they match an order on the site and returns order details (number/status/date/total/currency/line items/tracking). Visitor identity tokenization for logged-in users (Helpdesk add-on only): on pages with the assistant/ticket form, the plugin places a signed token containing the user’s ID/email/display name for the browser to pass to ProxyAI; logged-out visitors receive no token.
Dynamic content
Dynamic or runtime content behavior remains limited to what is explicitly documented in the official plugin evidence.
SEO and metadata
SEO and metadata behavior is documented only where it is explicitly established by official plugin information.
URLs and navigation
URL and navigation behavior remains outside translation scope unless explicitly represented by the integration category.
Forms and commerce
Forms and commerce behavior is limited to factual capabilities documented for this plugin.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what ProxyAI Chat Assistant does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
ProxyAI Chat Assistant and REEID Translate FAQ.
Does the current evidence establish translation scope for ProxyAI Chat Assistant?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.