OOMATES
oomates translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what oomates 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
- Embeds a front-end chat widget on every page load (widget loader/UI served via oomates CDN).
- Sends widget configuration to the oomates backend API on every page load.
- Processes AI chat conversations via the oomates backend API; for signed-in visitors, includes a signed token with WordPress user details (ID, display name, email, roles) and, if LearnDash is active, course titles and completion percentage; logged-out visitors send none of this.
- Integrates with WooCommerce cart operations in real time (add/update/remove items) and logs cart events to the oomates backend API.
- Tracks WooCommerce order status and triggers notifications/automation webhooks via the oomates backend API (order details such as email, items, totals are sent).
- Supports analytics via Mixpanel by collecting anonymous widget usage metrics (e.g., widget opens and searches) when the widget is loaded on front-end pages.
- Provides lead capture and scheduling flows (e.g., booking appointments via an integrated calendar) and syncs results to a CRM (as described in the plugin’s feature list).
Distinctive features
Embeds a front-end chat widget on every page load (widget loader/UI served via oomates CDN). Sends widget configuration to the oomates backend API on every page load. Processes AI chat conversations via the oomates backend API; for signed-in visitors, includes a signed token with WordPress user details (ID, display name, email, roles) and, if LearnDash is active, course titles and completion percentage; logged-out visitors send none of this. Integrates with WooCommerce cart operations in real time (add/update/remove items) and logs cart events to the oomates backend API. Tracks WooCommerce order status and triggers notifications/automation webhooks via the oomates backend API (order details such as email, items, totals are sent). Supports analytics via Mixpanel by collecting anonymous widget usage metrics (e.g., widget opens and searches) when the widget is loaded on front-end pages. Provides lead capture and scheduling flows (e.g., booking appointments via an integrated calendar) and syncs results to a CRM (as described in the plugin’s feature list).
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 oomates 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
oomates and REEID Translate FAQ.
Does the current evidence establish translation scope for oomates?
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.