LifeRaft OSTM
← All add-ons

Community

RLX Contact

Secure private contact channels, configurable shell placement, staff routing, inbox and email delivery, portable presets, and Forms/Support bridges.

ProductionVersion 0.3.1
Product images coming soonA closer look at RLX Contact.

What it does

Features 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

Built for your workflow

Who it’s for

  • Community owners organizing member participation
  • Creators and teams adding focused social workflows

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.

Optional connections

From setup to everyday use

A straightforward starting point

  1. Activate RLX Contact. Its management entry appears under Add-on Content
  2. Open RLX Contact → Contact Settings. Choose the page layout, Contact placement, default recipient email, default assignee, and spam limits
  3. Open Channels. Each channel may override the private recipient, staff assignee, delivery mode, access rule, and security mode

Before you choose

Common questions

What does RLX Contact do?

Secure private contact channels, configurable shell placement, staff routing, inbox and email delivery, portable presets, and Forms/Support bridges.

What does RLX Contact need to run?

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

Make RLX Contact part of your build.

Discuss the fit, requirements, and next steps for your project.

Let’s talk