
OOMATES
oomates compatibility with REEID Translate
oomates compatibility with REEID Translate is being evaluated from available plugin evidence. Embeds a front-end chat widget on every page load (widget loader/UI served via oomates CDN). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for oomates.
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
oomates 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 oomates 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
- 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).
CONTENT BOUNDARY
oomates 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
oomates and REEID Translate FAQ.
What does oomates do according to the available plugin evidence?
oomates 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 oomates?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for oomates?
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 oomates in a multilingual WordPress workflow.
REEID documents oomates 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.