MDL LOCAL SERVICE LEAD VALIDATOR
MDL Local Service Lead Validator compatibility with REEID Translate
MDL Local Service Lead Validator compatibility with REEID Translate is being evaluated from available plugin evidence. Validates phone number area codes against configured service areas to block out-of-area leads No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for MDL Local Service Lead Validator.
Official documentation did not establish a visitor-facing content item within the supported scope for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
MDL Local Service Lead Validator is documented in the Forms category with 8 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 MDL Local Service Lead Validator 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
- Validates phone number area codes against configured service areas to block out-of-area leads
- Supports Contact Form 7, WPForms, Gravity Forms, Elementor Pro Forms, and generic HTML forms
- Provides two-layer validation using client-side JavaScript for instant feedback and server-side PHP for security
- Offers NANP and International parsing modes with country-specific overrides
- Includes per-form allowed code list configuration via Form Overrides
- Logs blocked submissions with masked phone numbers and supports CSV export
- Features accessible warning UI with role="alert" and keyboard focus management
- Operates locally without external API calls and cleans up data on deletion
CONTENT BOUNDARY
MDL Local Service Lead Validator 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
- No visitor-facing translation surface was established for this integration.
COMMON QUESTIONS
MDL Local Service Lead Validator and REEID Translate FAQ.
What does MDL Local Service Lead Validator do according to the available plugin evidence?
MDL Local Service Lead Validator has 8 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 MDL Local Service Lead Validator?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for MDL Local Service Lead Validator?
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 MDL Local Service Lead Validator in a multilingual WordPress workflow.
REEID documents MDL Local Service Lead Validator 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.