NATIVESYNC CHAT
NativeSync Chat compatibility with REEID Translate
NativeSync Chat compatibility with REEID Translate is being evaluated from available plugin evidence. Bidirectional real-time message translation powered by the DeepL API via Supabase Edge Functions. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for NativeSync 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
NativeSync Chat is documented in the Other category with 6 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 NativeSync 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
- Bidirectional real-time message translation powered by the DeepL API via Supabase Edge Functions.
- Lightweight asynchronous chat widget (under 50KB) that renders a floating bubble on frontend pages.
- Centralized reply management through an external NativeSync web dashboard rather than WordPress admin interface.
- Support for online/offline modes with custom offline messages and optional Telegram bot notifications.
- Reliance on an external SaaS backend (Supabase) for data storage, messaging, and translation processing.
- Configuration requires linking a unique Shop ID from the NativeSync account to the WordPress plugin settings.
CONTENT BOUNDARY
NativeSync 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
NativeSync Chat and REEID Translate FAQ.
What does NativeSync Chat do according to the available plugin evidence?
NativeSync Chat has 6 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 NativeSync 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 NativeSync 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 NativeSync Chat in a multilingual WordPress workflow.
REEID documents NativeSync 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.