TWT CHAT
TWT Chat compatibility with REEID Translate
TWT Chat compatibility with REEID Translate is being reviewed using official plugin documentation. Integrates with the external TWT Chat SaaS service via a secure one-time binding callback, requiring administrator authentication through the TWT Accounts system. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What TWT Chat does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
TWT Chat is documented in the Other category with 6 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How TWT Chat compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Integrates with the external TWT Chat SaaS service via a secure one-time binding callback, requiring administrator authentication through the TWT Accounts system.
- Loads an immutable, version-pinned HTTPS visitor loader script (`core.js?version=v1.2`) only when the plugin is bound and enabled, serving the chat interface from `visitorchat.twt.com`.
- Establishes real-time communication using WebSockets (`wss://apichat.twt.com/ws`) for chat features after visitor session initialization, while using REST APIs for authentication and data retrieval.
- Stores site-specific binding credentials (App ID, sign key) in a single WordPress option, retaining local configuration data upon uninstall to allow seamless reactivation without re-authentication.
- Enforces strict security measures including SHA-256 hashed state tokens for OAuth-like flows, opaque sign keys for disconnect requests, and validation of App IDs against a specific ASCII character set.
- Provides administrative shortcuts to external TWT Console resources for conversation management, team settings, and widget customization directly from the WordPress admin interface.
TRANSLATION BOUNDARY
TWT Chat capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility. No specific content shown to visitors is confirmed for translation in this category.
FREQUENTLY ASKED QUESTIONS
TWT Chat and REEID Translate FAQ.
What does TWT Chat do?
TWT Chat has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does TWT Chat have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from TWT Chat?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate TWT Chat in a multilingual WordPress workflow.
REEID documents TWT Chat functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.