MWD AI ASSISTANT
MWD AI Assistant – Local Lead Generation compatibility with REEID Translate
MWD AI Assistant – Local Lead Generation compatibility with REEID Translate is being reviewed using official plugin documentation. Generates visitor responses using a user-provided OpenAI API key, ensuring no vendor account or subscription is required for core functionality. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What MWD AI Assistant – Local Lead Generation 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
MWD AI Assistant – Local Lead Generation 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 MWD AI Assistant – Local Lead Generation 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
- Generates visitor responses using a user-provided OpenAI API key, ensuring no vendor account or subscription is required for core functionality.
- Restricts AI answers to manually approved business facts, instructions, and contact details, preventing unverified external data retrieval in the core plugin.
- Supports multiple display modes including a floating chat widget and inline placement via the `[mwd_ai_assistant]` shortcode.
- Implements privacy controls such as AES-256-GCM encrypted API key storage, automatic masking of common contact details (email, phone, postal codes) in logs, and configurable conversation retention periods.
- Enforces usage limits through daily token safety caps and per-visitor/IP message rate limiting to manage costs and prevent abuse.
- Operates without loading third-party tracking scripts, fonts, or marketing assets, maintaining a minimal dependency footprint.
TRANSLATION BOUNDARY
MWD AI Assistant – Local Lead Generation 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
MWD AI Assistant – Local Lead Generation and REEID Translate FAQ.
What does MWD AI Assistant – Local Lead Generation do?
MWD AI Assistant – Local Lead Generation has 6 documented features listed in its official documentation. See the Plugin Information section for details.
Does MWD AI Assistant – Local Lead Generation 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 MWD AI Assistant – Local Lead Generation?
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 MWD AI Assistant – Local Lead Generation in a multilingual WordPress workflow.
REEID documents MWD AI Assistant – Local Lead Generation 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.