Learn Gravity Rail

Gravity Rail is a member engagement platform for proactive care. You’ll use Workflows to create conversations, Files to power them with knowledge, and Forms to collect structured data — all within one secure, compliant platform.

This guide walks through the core building blocks in order. Each section takes about 5 minutes.

A Workflow is a member touchpoint. It defines how your AI assistant greets a member, what it discusses, what it collects, and when it escalates. Every workflow can connect to communication channels — SMS, email, and phone — letting you reach members naturally.

Start with one workflow (like a post-visit check-in) and expand from there. Each workflow runs independently and can be triggered manually, on a schedule, or by an external event.

Files hold your knowledge — protocols, FAQs, care plans, and forms. Upload them once and attach them to any workflow. The assistant references these files during conversation, making responses context-aware and accurate.

Supported formats include PDF, Word documents, and plain text. Files are searchable and versioned — update a protocol and every workflow that references it picks up the change automatically.

Once you have a workflow, you can reach members proactively. Schedule an appointment reminder, trigger a risk assessment, or set up a weekly check-in. Gravity Rail handles the outreach — you define the message, audience, and timing.

Outbound campaigns can be one-time or recurring. Members who respond are routed into the workflow conversation, where the assistant picks up with full context.

Forms let you collect feedback, schedule details, or application data directly through conversation. Define the fields, attach the form to a workflow, and the assistant collects responses naturally — no separate portal or link required.

Responses automatically sync to your connected systems. Use forms for intake questionnaires, satisfaction surveys, consent collection, or any structured data capture.

Not everything should stay with the AI. Configure triggers (keywords, thresholds, intents) to escalate, route, or notify the right coordinator instantly.

Escalations include full conversation context so your team never starts cold. Route to Slack, email, or your existing ticketing system — the care coordinator sees the whole thread and can step in seamlessly.

You now understand the core building blocks: Workflows define the conversation. Files power it with knowledge. Forms collect structured data. Escalations keep your team in the loop.

The best way to learn is to build. Start with a single workflow for your most common member touchpoint and iterate from there.