REPLAI

Replai – CRM Forms compatibility with REEID Translate

Replai – CRM Forms compatibility with REEID Translate is being evaluated from available plugin evidence. Embeds REPLAI CRM forms on WordPress pages using a dedicated Elementor widget named "REPLAI Form". No specific visitor-facing translation surface is currently confirmed.

Visit Replai – CRM Forms ↗

AWAITING VERIFICATION

What the available evidence establishes for Replai – CRM Forms.

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
Replai – CRM Forms is documented in the Forms 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 Replai – CRM Forms 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

  • Embeds REPLAI CRM forms on WordPress pages using a dedicated Elementor widget named "REPLAI Form".
  • Requires a project-scoped API key (“Project API Key”) generated inside REPLAI (Sales > Configuration > WordPress Plugin) to connect WordPress to the REPLAI platform.
  • Provides a built-in connection test (“Test connection”) to fetch the catalog of available forms for the connected project.
  • Supports multilingual behavior by letting the form output be locked to a chosen language or follow the page locale.
  • Caches the form catalog locally and provides a manual refresh option (and/or a connection test from the admin screen).
  • Submits visitor form entries to the REPLAI project (embedded via an iframe served by REPLAI) so submissions are processed inside the REPLAI platform.

CONTENT BOUNDARY

Replai – CRM Forms 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

Replai – CRM Forms and REEID Translate FAQ.

What does Replai – CRM Forms do according to the available plugin evidence?

Replai – CRM Forms 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 Replai – CRM Forms?

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

What would establish translation scope for Replai – CRM Forms?

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 Replai – CRM Forms in a multilingual WordPress workflow.

REEID documents Replai – CRM Forms 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