
CREAVI APPOINTMENT BOOKING CALENDAR
Creavi Appointment Booking Calendar Forms integration with REEID Translate.
Creates an appointment booking flow with step-by-step steps: Date → Time → Details REEID has reviewed the available plugin evidence for multilingual compatibility, but no specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for Creavi Appointment Booking Calendar.
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
Creavi Appointment Booking Calendar 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 Creavi Appointment Booking Calendar 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
- Creates an appointment booking flow with step-by-step steps: Date → Time → Details
- Collects booking details via configurable booking form fields (default Name, Email, Phone and additional custom fields like Text, Textarea, Telephone, Number)
- Sends confirmation emails and booking reminders to both admin and customer
- Supports booking via shortcodes and Gutenberg blocks (including a booking popup button and an inline booking interface)
- Integrates with Google Calendar and Outlook Calendar to push bookings and block busy time slots
- Generates downloadable .ics (iCalendar) files for bookings
- Provides a customer-facing calendar that can follow the website language or use one of 67 explicit language and regional choices
CONTENT BOUNDARY
Creavi Appointment Booking Calendar 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
Creavi Appointment Booking Calendar and REEID Translate FAQ.
What does Creavi Appointment Booking Calendar do according to the available plugin evidence?
Creavi Appointment Booking Calendar 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 Creavi Appointment Booking Calendar?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for Creavi Appointment Booking Calendar?
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 Creavi Appointment Booking Calendar in a multilingual WordPress workflow.
REEID documents Creavi Appointment Booking Calendar 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.