Community
RLX Support
Self-contained support ticket system with member tickets, replies, staff queue, canned responses, SLA fields, and optional RLX Kanban sync.
What it does
Features at a glance
- Member support tickets with history, replies, status, priority, assignment, SLA fields, and staff notes
- Canned replies, staff queue, product association, and optional Kanban card sync
- Optional RLX Contact bridge for signed-in contact messages to become linked support tickets
- Turns scattered community information into managed pages and repeatable content flows
- Gives owners a stronger reason to keep members inside the RLX site
- Member ticket submission, ticket history, ticket detail pages, and member replies. Dedicated add-on admin queue at workflow. Canned replies for reusable staff responses
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
- Update assignment, status, tags, SLA date, staff notes, and internal notes as work progresses
- Add canned replies from the Canned Replies tab if the team needs reusable responses
- Enable the RLX Contact bridge when signed-in contact submissions should become support tickets
Before you choose
Common questions
What does RLX Support do?
Self-contained support ticket system with member tickets, replies, staff queue, canned responses, SLA fields, and optional RLX Kanban sync.
What does RLX Support need to run?
RLX Support 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 Support 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 Support part of your build.
Discuss the fit, requirements, and next steps for your project.