Commerce
RLX Leads
Shared lead capture, qualification, consent, source attribution, follow-up tracking, and add-on handoff records for LifeRaft OS.
What it does
Features at a glance
- Lead records with contact details, business context, source attribution, tags, score, status, owner, notes, and follow-up date
- Marketing opt-in fields with consent timestamp, source, and plain-language consent label
- Admin pipeline views for new, qualified, contacted, won, lost, and archived leads
- Payload storage for custom fields from quote builders, forms, funnels, and other add-ons
- Hook events when leads are created or updated
Built for your workflow
Who it’s for
- Businesses and creators organizing customer-facing workflows
- Site owners adding focused sales or membership capabilities
Setup and fit
Compatibility
Requires a valid LifeRaft OS core license and a supported installation.
No additional add-on is listed as a required dependency.
From setup to everyday use
A straightforward starting point
- Activate RLX Leads and review its add-on settings
- Lead records with contact details, business context, source attribution, tags, score, status, owner, notes, and follow-up date
- Marketing opt-in fields with consent timestamp, source, and plain-language consent label
Before you choose
Common questions
What does RLX Leads do?
Shared lead capture, qualification, consent, source attribution, follow-up tracking, and add-on handoff records for LifeRaft OS.
What does RLX Leads need to run?
RLX Leads runs on the LifeRaft OS core without another add-on listed as a required dependency. Optional integrations can be added for a broader workflow.
How ready is RLX Leads for deployment?
Production is this add-on’s declared release stage. The V5 platform is a development build; review the workflows, hosting, and integrations you plan to use.
Review the launch checklist
- 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.
- Payment QA — Test provider setup, order states, entitlements, refunds, and failed-payment recovery.
- Docs and support — Add customer-facing notes, admin setup instructions, and known limitations for the module.
Make RLX Leads part of your build.
Discuss the fit, requirements, and next steps for your project.