TELECAST
teleCast compatibility with REEID Translate
teleCast compatibility with REEID Translate is being reviewed using official plugin documentation. Telegram bridge via shortcode: connects a Telegram group to a WordPress site chat widget placed using the `[telecast]` shortcode (including required `token` and `channel` parameters). No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What teleCast 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
teleCast 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 teleCast 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
- Telegram bridge via shortcode: connects a Telegram group to a WordPress site chat widget placed using the `[telecast]` shortcode (including required `token` and `channel` parameters).
- Real-time bi-directional messaging: uses a persistent WebSocket connection for instant delivery, relaying messages between website visitors and the Telegram group without polling or page reloads.
- Service-hosted relay and translation pipeline: chat messages and visitor display names are transmitted to `thesaasfactory.net` servers; when translation is needed, message content is sent to `thesaasfactory.net` for translation via DeepL Pro before relaying to Telegram (and replies back).
- Widget JavaScript loaded from vendor service: the plugin loads the widget JavaScript from `https://thesaasfactory.net/telecast/assets/telecast.js` on pages where the shortcode is used.
- Widget style isolation via Shadow DOM: the widget runs inside a Shadow DOM to isolate it from the theme’s CSS, with light/dark theme selection via a shortcode `theme` attribute (default light).
- Telegram bot requirement for operation: requires creating a Telegram bot via @BotFather and adding it to the target Telegram group as an admin.
TRANSLATION BOUNDARY
teleCast 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 context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
teleCast and REEID Translate FAQ.
What does teleCast do?
teleCast has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does teleCast 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 teleCast?
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 teleCast in a multilingual WordPress workflow.
REEID documents teleCast 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.