RLX Support

Self-contained support ticket system with member tickets, replies, staff queue, canned responses, SLA fields, and optional RLX Kanban sync.

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.

RLX Support can run as its own Community workflow. By itself, it focuses on 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, and Optional RLX Contact bridge for signed-in contact messages to become linked support tickets, so a customer can use the module without buying every related add-on first.

No. Related add-ons are optional package pairings, not required purchases unless a project specifically needs that wider workflow. RLX Support 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.

When the customer also owns and activates related modules such as RLX Kanban, RLX Newsletter, RLX Chat, RLX Polls, and RLX Survey, RLX Support 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.

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

RLX Support should be launched with its real data model and public routes in mind. Routes: RLX Support 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. sample tickets. Empty states are shown until members or staff create real support records Optional integrations: rlx-kanban.

RLX Support has a $44.85 Everyday add-on license. The add-on requires a valid Personal, Professional, Creator, or separately agreed LifeRaft OS core license.

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.

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

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. Enable the Kanban bridge in add-on settings only when rlx-kanban should receive synced support cards. canned replies from the Canned Replies tab if the team needs reusable responses.

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.