Complete your workspace setup
Use onboarding to configure the essentials that unblock your team's first live workflow in claimOS without wandering through scattered settings pages or launching half-finished defaults.
Guide
What claimOS does for a modern claims team
Get a practical overview of how claimOS connects launch, live claim work, communications, evidence, and reporting so a team can operate from one shared system instead of stitching together handoffs manually.
Outcome
What this helps you do
Understand the operating model behind claimOS before you decide how the team should launch, route work, and manage handoffs inside it day to day.
This guide is written for all teams and uses real claimOS screenshots so the instructions map cleanly to the product surface.
Prerequisites
Before you start
- A claimOS workspace URL if you want to follow along in the product.
- Admin access if you want to compare the guide to a real setup path.
- A willingness to evaluate one complete workflow instead of isolated features.
Steps
How to do it
1Start with the operating model
claimOS is built to keep intake, active work, supporting evidence, outbound communication, and reporting in one connected system so teams do not lose context during handoffs.
2Understand the main surfaces
Home and My Work help teams decide what to do next, Claims keeps the record and evidence together, and supporting surfaces like Communications, Weather, and Reporting add context only when the work actually demands it.
3Follow one record from launch into active work
The fastest way to understand the platform is to imagine one claim moving from setup into intake, then into the queue, then into the claim workspace. claimOS makes the most sense when you view those surfaces as one flow instead of separate destinations.
4Use onboarding to create the first usable path
The onboarding checklist is not just a tutorial. It is the fastest way to get branding, workspace defaults, and the first real claim path into a stable, team-ready state that operators can trust.
5Notice how visibility changes once work is live
Needs attention, queue views, and the claim workspace are there to keep emerging risk visible. claimOS is not just about storing data, but about showing the team what requires action next.
6Treat the platform like an operating system, not a pile of tools
The biggest gain comes when your team uses the connected surfaces together instead of recreating the workflow in spreadsheets, inbox folders, and side channels.
7Run a quick evaluation check before going deeper
Before opening every feature page, ask whether the launch path, the first live claim, and the first queue handoff already feel clearer than your current workflow.
If those three moments still feel confusing, keep evaluating the core path first. Deeper settings and features are easier to judge once the operating model clicks.
Screenshots
See the workflow
Watch the paired walkthrough
Walkthrough0:56
See the same workflow in motion
A short buyer-facing walkthrough of how claimOS becomes the operating layer for launch, live claims work, evidence, communications, and reporting.
Start with the high-level buyer question: what does claimOS unify that most teams currently spread across multiple tools and private follow-up loops?
Watch related walkthroughFAQ
Common questions
Do I need to finish every onboarding task before creating work?
No. Start with the essentials that unblock your first claim, then return to optional configuration once the team has a working path.
Who should own setup in a new workspace?
An owner or admin should handle the first-pass setup so defaults, permissions, and integrations stay consistent across the team.
How should a team think about claimOS during the first evaluation?
Treat it like an operating model review, not a feature scavenger hunt. The fastest way to evaluate claimOS is to follow one claim from launch into active work and see whether context stays attached the whole way.
What is the best first workflow to test in claimOS?
Start with workspace setup, first claim creation, and the first queue handoff. If those three moments feel clear, the rest of the platform usually becomes much easier to understand.
Keep Going