
ANNONA BOT
Annona Bot — AI Customer Support compatibility with REEID Translate
Annona Bot — AI Customer Support compatibility with REEID Translate is being evaluated from available plugin evidence. Frontend widget script injection: When the plugin is active, it loads a JavaScript file from `annonabot.com` on the site’s frontend pages. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Annona Bot — AI Customer Support.
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
Annona Bot — AI Customer Support is documented in the Analytics category with 5 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 Annona Bot — AI Customer Support 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
- Frontend widget script injection: When the plugin is active, it loads a JavaScript file from `annonabot.com` on the site’s frontend pages.
- Message-based data transmission: Visitor messages are sent to Annona Bot’s servers for processing only after the visitor actively interacts with the chat widget.
- Analytics/measurement: The plugin provides analytics to see what customers ask, which questions go unanswered, and a resolution rate.
- Asynchronous loading behavior: The widget script loads asynchronously and does not block page rendering.
- Privacy-first data handling: The plugin states that visitor data is never used for model training and that no visitor data is collected or transmitted until a visitor sends a message through the widget.
CONTENT BOUNDARY
Annona Bot — AI Customer Support 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
Annona Bot — AI Customer Support and REEID Translate FAQ.
What does Annona Bot — AI Customer Support do according to the available plugin evidence?
Annona Bot — AI Customer Support has 5 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 Annona Bot — AI Customer Support?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Annona Bot — AI Customer Support?
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 Annona Bot — AI Customer Support in a multilingual WordPress workflow.
REEID documents Annona Bot — AI Customer Support 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.