TELECAST
teleCast compatibility with REEID Translate
teleCast compatibility with REEID Translate is being evaluated from available plugin evidence. 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 visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for teleCast.
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
teleCast 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 teleCast 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
- 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.
CONTENT BOUNDARY
teleCast 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
teleCast and REEID Translate FAQ.
What does teleCast do according to the available plugin evidence?
teleCast 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 teleCast?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for teleCast?
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 teleCast in a multilingual WordPress workflow.
REEID documents teleCast 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.