MULTICONTACT BUTTONS

MultiContact Buttons compatibility with REEID Translate

MultiContact Buttons compatibility with REEID Translate is being evaluated from available plugin evidence. Context-aware contact routing that can prioritize or isolate a configured channel based on current page type, WooCommerce product category, and business-hours status No specific visitor-facing translation surface is currently confirmed.

Visit MultiContact Buttons ↗

AWAITING VERIFICATION

What the available evidence establishes for MultiContact Buttons.

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
MultiContact Buttons is documented in the Other category with 7 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 MultiContact Buttons 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

  • Context-aware contact routing that can prioritize or isolate a configured channel based on current page type, WooCommerce product category, and business-hours status
  • Supports multiple front-end presentation modes including separate direct buttons, an expandable launcher, an always-open contact card, a Gutenberg block, an optional Elementor widget, and a prefixed shortcode
  • Provides click-to-action contact channels via standard URL schemes/links (e.g., wa.me for WhatsApp, tel: for calls, sms: for SMS, mailto: for email, t.me for Telegram, m.me for Messenger, plus a configurable custom HTTP/HTTPS link)
  • Smart routing fallback behavior: can fall back to the normal configured channel order when a preferred channel is unavailable
  • Configurable targeting and scheduling for when output appears, including desktop vs mobile visibility, logged-in vs logged-out targeting, post/page/product/custom-content inclusion/exclusion, hiding on specific views (e.g., front page, archives, search, 404), and business-hours evaluation using the WordPress site timezone
  • Message templating placeholders for WhatsApp/SMS/email that can include page/post and site fields (and WooCommerce product fields when on a WooCommerce product page)
  • Security/privacy-conscious front-end behavior: uses local CSS/JavaScript/SVG icons, does not load remote fonts/icon libraries, does not set visitor cookies or record click analytics, and only opens external services after a visitor actively clicks a configured button

CONTENT BOUNDARY

MultiContact Buttons 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

MultiContact Buttons and REEID Translate FAQ.

What does MultiContact Buttons do according to the available plugin evidence?

MultiContact Buttons has 7 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 MultiContact Buttons?

No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.

What would establish translation scope for MultiContact Buttons?

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 MultiContact Buttons in a multilingual WordPress workflow.

REEID documents MultiContact Buttons 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.

Shopping Cart
Scroll to Top