LifeRaft OSTM

Community add-on

RLX Contact

Private contact channels, public contact page, footer/profile/forum hooks, internal inbox, optional email delivery, and optional RLX Forms bridge.

CommunityCategory
0.1.0Version
ProductionRelease stage
$34.85 · FocusedLicense
Back to catalog
Community add-on

About this add-on

RLX Contact for LifeRaft OS

## Why It Exists

Private contact channels, public contact page, footer/profile/forum hooks, internal inbox, optional email delivery, and optional RLX Forms bridge. Use it to keep member activity, communication, discovery, and support inside the owned community instead of scattering the experience across disconnected tools. The practical win: private contact channels with internal inbox, assignment, status, and priority workflow.

At a glance
  • Private contact channels with internal inbox, assignment, status, and priority workflow
  • Public, members-only, invite-only, and private contact channel modes
  • Customer invite links with optional account registration invite pairing
  • Keeps member value inside the owned community instead of losing activity to third-party tools
rlx-contact Version 0.1.0 $34.85 · Focused Production

Capabilities and outcomes

How RLX Contact 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.

Keeps member value inside the owned community instead of losing activity to third-party tools

Supports participation, discovery, support, and communication from one coherent product surface

Community builds that need RLX Contact without forcing it into every install

Standalone value

What it does by itself

RLX Contact can run as its own Community workflow. By itself, it focuses on Private contact channels with internal inbox, assignment, status, and priority workflow, Public, members-only, invite-only, and private contact channel modes, and Customer invite links with optional account registration invite pairing, 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 Forms, RLX Support, RLX Newsletter, RLX Chat, and RLX Polls, RLX Contact 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

  • Private contact channels with internal inbox, assignment, status, and priority workflow
  • Public, members-only, invite-only, and private contact channel modes
  • Customer invite links with optional account registration invite pairing
  • Community builds that need RLX Contact without forcing it into every install

Workflow

How it fits into a real build

  1. Activate RLX Contact and review its add-on settings
  2. Configure the module settings and permissions
  3. Add the records, content, media, or rules this module manages
  4. Review public pages and backend empty states before launch
  5. RLX Contact loads from rlx-contact/addon.php and should be configured through the add-on registry, permissions, and

Works well with

The strongest builds connect the right modules

RLX Contact becomes more valuable when it is paired with the workflows around it. Common pairings include RLX Forms, RLX Support, RLX Newsletter, RLX Chat, RLX Polls, 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.

Package QA

Confirm the module fits the selected product package and does not expose unused workflows.

Docs and support

Add customer-facing notes, admin setup instructions, and known limitations for the module.

Customer FAQ

Common questions about RLX Contact

What does RLX Contact do?

Private contact channels, public contact page, footer/profile/forum hooks, internal inbox, optional email delivery, and optional RLX Forms bridge.

Who is RLX Contact best for?

Private contact channels with internal inbox, assignment, status, and priority workflow. Public, members-only, invite-only, and private contact channel modes. Customer invite links with optional account registration invite pairing.

Can RLX Contact run by itself?

RLX Contact can run as its own Community workflow. By itself, it focuses on Private contact channels with internal inbox, assignment, status, and priority workflow, Public, members-only, invite-only, and private contact channel modes, and Customer invite links with optional account registration invite pairing, 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 Contact 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 Forms, RLX Support, RLX Newsletter, RLX Chat, and RLX Polls, RLX Contact 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 Contact?

RLX Contact commonly pairs with RLX Forms, RLX Support, RLX Newsletter, RLX Chat, RLX Polls. Active pairings depend on the package, customer workflow, and installed add-ons.

What should be decided before launching RLX Contact?

RLX Contact should be launched with its real data model and public routes in mind. Routes: RLX Contact is exposed through the routes registered by its add-on entry file when the module is active. During, launch, teams should confirm the public page, admin entry point, empty states, permissions, and navigation placement, match the package being sold. Add screenshots of public pages, admin controls, member workflows, moderation options, and example content types Include a short scenario showing how RLX Contact helps a community owner reduce support load or publish cleaner Optional integrations: rlx-forms, rlx-support.

How much does RLX Contact cost?

RLX Contact has a $34.85 Focused 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 Contact?

Standard add-on support covers the licensed module during the active support window of the selected core edition. Exact scope is confirmed with the package. Personal includes 3 months, Professional includes 6 months, and Creator includes 12 months of core support and updates.

How ready is RLX Contact for deployment?

Production module: packaged for normal licensed deployment, subject to the hosting, configuration, and integration checks described in the documentation.

How does RLX Contact fit into a real LifeRaft OS build?

Activate RLX Contact 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.

Coming soon

Want RLX Contact in your LifeRaft OS build?

RLX Contact 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.