REACHMINT CONTACT LAUNCHER
ReachMint Contact Launcher compatibility with REEID Translate
ReachMint Contact Launcher compatibility with REEID Translate is being reviewed using official plugin documentation. Provides a privacy-first floating contact launcher widget that reveals available contact options sequentially. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What ReachMint Contact Launcher 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
ReachMint Contact Launcher is documented in the Other category with 7 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 ReachMint Contact Launcher 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
- Provides a privacy-first floating contact launcher widget that reveals available contact options sequentially.
- Supports up to 50 configurable contact buttons including WhatsApp, Messenger, LINE, Telegram, Viber, Instagram, WeChat, email, phone, SMS, and custom links.
- Enables granular visibility controls per button based on device type (mobile/desktop), page context (front page, blog, pages), and weekly availability schedules.
- Implements client-side schedule and device checks using the WordPress site timezone, ensuring compatibility with page-cached sites.
- Operates without external dependencies such as accounts, API keys, hosted dashboards, tracking services, or external icon libraries.
- Includes accessibility features such as keyboard navigation, Escape-to-close behavior, focus styles, and reduced-motion support.
- Stores configuration data locally in the WordPress options table without setting cookies, collecting analytics, or sending telemetry.
TRANSLATION BOUNDARY
ReachMint Contact Launcher 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
ReachMint Contact Launcher and REEID Translate FAQ.
What does ReachMint Contact Launcher do?
ReachMint Contact Launcher has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does ReachMint Contact Launcher 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 ReachMint Contact Launcher?
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 ReachMint Contact Launcher in a multilingual WordPress workflow.
REEID documents ReachMint Contact Launcher 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.