ZAVU MESSAGING
Zavu Messaging compatibility with REEID Translate
Zavu Messaging compatibility with REEID Translate is being evaluated from available plugin evidence. Connects a WordPress site to the Zavu messaging platform via a Zavu account (and either a “Connect with Zavu” flow or an API key). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Zavu Messaging.
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
Zavu Messaging 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 Zavu Messaging 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
- Connects a WordPress site to the Zavu messaging platform via a Zavu account (and either a “Connect with Zavu” flow or an API key).
- Sends WooCommerce-related notifications (e.g., confirmed/completed order updates to customers; owner alerts for new orders).
- Sends notifications for form leads from Contact Form 7, WPForms, and Gravity Forms (owner alerts for every form lead).
- Supports SMS and WhatsApp delivery, with WhatsApp requiring a connected WhatsApp Business account and notifications upgrading from SMS once WhatsApp is active.
- Implements an opt-in consent checkbox at checkout (on by default) for messaging consent.
- Queues message dispatch in the background (Action Scheduler when available) to avoid slowing checkout, and uses an idempotency key to prevent duplicate double-messaging from duplicate hooks.
- Provides an activity log with delivery statuses and a dashboard widget showing monthly usage and balance.
CONTENT BOUNDARY
Zavu Messaging 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
Zavu Messaging and REEID Translate FAQ.
What does Zavu Messaging do according to the available plugin evidence?
Zavu Messaging 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 Zavu Messaging?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Zavu Messaging?
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 Zavu Messaging in a multilingual WordPress workflow.
REEID documents Zavu Messaging 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.