MSGBOX AI CHAT
MsgBox AI Chat compatibility with REEID Translate
MsgBox AI Chat compatibility with REEID Translate is being evaluated from available plugin evidence. Provides an AI-powered customer support chat widget that generates automated responses to visitor questions. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for MsgBox AI Chat.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
MsgBox AI Chat is documented in the Analytics category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How MsgBox AI Chat compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Provides an AI-powered customer support chat widget that generates automated responses to visitor questions.
- Widget can be enabled/disabled via plugin controls, and can be positioned on the bottom-right or bottom-left of the site.
- Supports hiding the widget on specific pages or posts via an exclusions setting (comma-separated page/post IDs).
- Controls which users can see the widget (everyone, logged-in users only, or guests only).
- Loads its frontend widget script asynchronously using the `defer` attribute to avoid blocking page rendering.
- Integrates with WooCommerce to access the product catalog for recommendations, using a signed, read-only connection and without generating or storing WooCommerce API keys.
- Offers an optional WooCommerce product-page feature (“Ask the AI anything about this product”) that can be placed via WooCommerce hooks, a `[msgbox_ask]` shortcode, or a “MsgBox: Ask the AI” block, with suggested questions generated from product description and switchable off.
CONTENT BOUNDARY
MsgBox AI Chat capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
MsgBox AI Chat and REEID Translate FAQ.
What does MsgBox AI Chat do according to the available plugin evidence?
MsgBox AI Chat has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for MsgBox AI Chat?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for MsgBox AI Chat?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate MsgBox AI Chat in a multilingual WordPress workflow.
REEID documents MsgBox AI Chat functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.