SMART BOOKING
Smart Booking compatibility with REEID Translate
Smart Booking compatibility with REEID Translate is being evaluated from available plugin evidence. Smart Booking is a free WordPress booking plugin for consultation-style appointments with a 3-step flow (input → confirmation → done). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Smart 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
Smart Booking is documented in the Forms 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 Smart 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
- Smart Booking is a free WordPress booking plugin for consultation-style appointments with a 3-step flow (input → confirmation → done).
- It supports multi-store and multi-staff management for scheduling and booking steps.
- It provides a booking form via the `[smart_booking]` shortcode (including an optional `store_id` attribute).
- It supports custom form fields beyond built-in name/email/phone fields (text, email, phone, textarea, select, radio, checkbox).
- It sends email notifications to the customer and administrator when a booking is received, and sends a confirmation email to the customer on approval.
- It integrates with Google Tag Manager by pushing each booking step (e.g., `store_select`, `staff_select`, `date_select`, `time_select`, `form_input`, `confirm`, `complete`) to `window.dataLayer`.
- It can optionally integrate with external services (Google Calendar and ChatWork notifications) after administrator enablement and configuration.
CONTENT BOUNDARY
Smart 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
Smart Booking and REEID Translate FAQ.
What does Smart Booking do according to the available plugin evidence?
Smart Booking 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 Smart 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 Smart 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 Smart Booking in a multilingual WordPress workflow.
REEID documents Smart 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.