Operations add-on
RLX Landing Intake
Database-first landing forms routed into Waitlist, Contact, Newsletter, admin notifications, acknowledgements, and the retryable email queue.
About this add-on
RLX Landing Intake for LifeRaft OS
Database-first landing forms routed into RLX Waitlist, RLX Contact, RLX Leads, RLX Newsletter, administrator notifications, visitor acknowledgements, and the retryable LifeRaft OS email queue.
Database-first landing forms routed into Waitlist, Contact, Newsletter, admin notifications, acknowledgements, and the retryable email queue. Use it when staff need a controlled operating surface for reporting, approvals, planning, security, automation, and decision support instead of another spreadsheet habit.
- Admin-managed content and settings
- Public pages with clean presentation
- Designed to run as an optional RLX module
- Turns admin work into a controlled process instead of a spreadsheet habit
Capabilities and outcomes
How RLX Landing Intake improves the build
The overview above identifies the core capability. These supporting outcomes help a project owner judge whether the add-on belongs in the package.
Gives professional teams cleaner visibility, repeatability, and post-launch operating confidence
RLX Landing Intake can be packaged as an optional upgrade, bundle component, or project-specific module
Operations builds that need RLX Landing Intake without forcing it into every install
Standalone value
What it does by itself
RLX Landing Intake can run as its own Operations workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
Connected value
What improves when related add-ons are active
When the customer also owns and activates related modules such as RLX Waitlist, RLX Contact, RLX Newsletter, RLX Leads, and RLX Notifications, RLX Landing Intake can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Best fit
Who should care about it
- Operations builds that need RLX Landing Intake without forcing it into every install
Workflow
How it fits into a real build
- Activate RLX Landing Intake and review its add-on settings
- Configure the module settings and permissions
- Add the records, content, media, or rules this module manages
- Review public pages and backend empty states before launch
Works well with
The strongest builds connect the right modules
RLX Landing Intake becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Waitlist, RLX Contact, RLX Newsletter, RLX Leads, RLX Notifications, depending on the customer package and what the site needs to accomplish.
Admin setup
Confirm settings, navigation placement, permissions, and any required starter content before launch.
Public QA
Review the public page, empty states, mobile layout, and activated/deactivated states.
Data QA
Check exports, filtering, retention, audit visibility, and staff-only permissions.
Docs and support
Add customer-facing notes, admin setup instructions, and known limitations for the module.
Customer FAQ
Common questions about RLX Landing Intake
What does RLX Landing Intake do?
Database-first landing forms routed into Waitlist, Contact, Newsletter, admin notifications, acknowledgements, and the retryable email queue.
Who is RLX Landing Intake best for?
Operations builds that need RLX Landing Intake without forcing it into every install.
Can RLX Landing Intake run by itself?
RLX Landing Intake can run as its own Operations workflow. By itself, it focuses on Admin-managed content and settings, Public pages with clean presentation, and Designed to run as an optional RLX module, so a customer can use the module without buying every related add-on first.
Do I need the other add-ons mentioned on this page?
No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Landing Intake should still explain a useful standalone job before any connected modules are considered. Standalone means it does not have to be cross-linked with other add-ons. It still runs inside LifeRaft OS and requires a valid core LifeRaft OS license.
What changes when related add-ons are active?
When the customer also owns and activates related modules such as RLX Waitlist, RLX Contact, RLX Newsletter, RLX Leads, and RLX Notifications, RLX Landing Intake can hand off data, links, reporting, access control, content, or follow-up steps into those workflows. Those connections are optional and depend on the package being built.
Which add-ons work well with RLX Landing Intake?
RLX Landing Intake commonly pairs with RLX Waitlist, RLX Contact, RLX Newsletter, RLX Leads, RLX Notifications. Active pairings depend on the package, customer workflow, and installed add-ons.
What should be decided before launching RLX Landing Intake?
RLX Landing Intake should be launched with its real data model and public routes in mind. Optional integrations: rlx-waitlist, rlx-contact, rlx-newsletter, rlx-leads, rlx-notifications.
How much does RLX Landing Intake cost?
RLX Landing Intake has a $64.85 Advanced add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.
What support is included for RLX Landing Intake?
Enhanced add-on support indicates a broader or more operationally involved module. Exact response scope and duration are confirmed with the licensed package and core edition. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.
How ready is RLX Landing Intake for deployment?
Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.
How does RLX Landing Intake fit into a real LifeRaft OS build?
Activate RLX Landing Intake and review its add-on settings. Configure the module settings and permissions. Add the records, content, media, or rules this module manages. Review public pages and backend empty states before launch.
Does the public page include implementation details?
No. The public page explains customer value, package fit, related modules, and launch expectations. Setup steps, route details, data structures, hooks, and operator-only notes stay in the licensed add-on documentation.
Related add-ons
Explore the surrounding add-on ecosystem
Coming soon
Want RLX Landing Intake in your LifeRaft OS build?
RLX Landing Intake is part of the modular LifeRaft OS add-on roadmap. Join the waitlist or discuss a package so the right modules can be planned around the way your community, product, studio, or business actually operates.