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
Connect core integrations
Connect the external systems your team actually uses so claimOS can remain the operating layer instead of becoming another disconnected tool in the stack.
Outcome
What this helps you do
Set up core integrations in a way that supports real workflows, proves the handoff works, and avoids brittle configuration debt.
This guide is written for admins and uses real claimOS screenshots so the instructions map cleanly to the product surface.
Prerequisites
Before you start
- Admin access and the credentials for the systems you want to connect.
- A clear understanding of which workflow the integration should support first.
- A demo-safe path for testing the handoff after connection.
Steps
How to do it
1Connect only the workflows you will actually use
Start with the integrations that unblock communication, scheduling, billing, or intake for the team’s near-term workflow.
2Choose one operating path to prove first
Before connecting multiple tools, decide which single workflow you want to validate end to end so you know what successful handoff should look like after setup.
3Verify account health after connection
Do not stop at a successful connect flow. Confirm the account state, callback behavior, and the expected claimOS readiness indicators.
4Confirm claimOS is now the place the team can work from
A good integration should reduce context switching. Check whether the team can now act from claimOS with less dependence on the external system for day-to-day follow-through.
5Test the end-to-end behavior
Run a real or demo-safe action through the integrated path so you know the workflow works beyond a green status light and that the team understands what success looks like.
6Assign an owner for drift, support, and future testing
Every integration should have a clear operational owner who can retest the workflow, diagnose drift, and decide when configuration changes are safe.
7Document the operational owner
Each core integration should have a clear owner who can diagnose problems quickly when an external dependency drifts.
8Run a reliability check before calling the integration done
Make sure the integrated workflow works more than once, lands in the right place, and is understandable to someone other than the person who connected it.
If the integration only looks healthy because the original admin knows its quirks, it is not stable enough for the wider team yet.
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.
Which integrations should be connected first?
Start with the systems that directly unblock communication, intake, scheduling, or billing in the near-term workflow. Connecting everything at once usually creates more testing work than real value.
How do I know an integration is truly ready?
A green connection state is not enough. Run a real or demo-safe workflow through the integration and confirm the result lands where the team expects it inside claimOS.
Keep Going