4WP BOOKING
4WP Booking compatibility with REEID Translate
4WP Booking compatibility with REEID Translate is being evaluated from available plugin evidence. Lets visitors pick a service, a date, a time, and submit their details for booking. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for 4WP Booking.
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
4WP Booking 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 4WP Booking 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
- Lets visitors pick a service, a date, a time, and submit their details for booking.
- Requests go through WordPress (server-side), with provider API keys and bot tokens kept on the server.
- Provides a calendar booking template flow: service → date → time → guest details.
- Supports a Gutenberg block, a `[forwp_booking]` shortcode, and an optional Elementor widget for placing the booking interface.
- Sends notifications for bookings via email and Telegram, and can forward form submissions (Contact Form 7, WPForms, Gravity Forms) to Telegram.
- Uses server-side HTTPS requests to deliver booking and notification messages to external services (ClinicCards API and Telegram Bot API).
CONTENT BOUNDARY
4WP Booking 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
4WP Booking and REEID Translate FAQ.
What does 4WP Booking do according to the available plugin evidence?
4WP Booking 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 4WP Booking?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for 4WP Booking?
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 4WP Booking in a multilingual WordPress workflow.
REEID documents 4WP Booking 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.