Create your first claim
Create your first live claim in claimOS so the team can move from setup into real execution without getting stuck in unnecessary data entry or unowned records.
Guide
Build and publish a lead form
Use the lead-form builder to publish a clear intake experience without creating another disconnected acquisition tool or cleanup-heavy handoff.
Outcome
What this helps you do
Ship a lead capture path that connects directly into the claimOS operating flow and gives the team cleaner first-notice context.
This guide is written for admins and uses real claimOS screenshots so the instructions map cleanly to the product surface.
Prerequisites
Before you start
- Permission to manage lead forms.
- A basic intake flow you want to publish.
- A clear owner for reviewing the first live submissions.
- A demo-safe test path for validating live-vs-draft behavior.
Steps
How to do it
1Choose the right authoring mode
Decide whether your team needs a focused embedded form or a fuller hosted page, then shape the form around the minimum fields that unblock follow-up.
2Define the first action you want the submission to trigger
Before editing the form itself, decide what the team should be able to do immediately when a lead arrives. That desired next action should shape the field set and delivery mode.
3Configure the content and field structure
Use labels, help text, and the page structure to reduce confusion for submitters instead of relying on follow-up calls to clarify basics.
4Keep the field set focused on usable intake
Ask only for information that helps the team understand urgency, contactability, and the next follow-up step. More fields do not help if they create abandonment or cleanup.
5Review go-live readiness
Before publishing, confirm hosted delivery state, metadata, live-vs-draft behavior, and who will validate the first real submission so you know exactly what will ship.
6Run a live-path test before announcing the form
Submit a demo-safe lead and confirm where it lands, who sees it, and whether the team can route it without manually reconstructing the intake context.
7Publish and verify the live experience
Open the live form, submit a test lead, and confirm the intake lands in claimOS with the right context for the team.
8Do a handoff check after the first real submissions
After go-live, review the first few submissions and confirm the intake path is producing usable work, not just more volume.
If operators are re-contacting leads for basics the form should have captured, tighten the field set and helper copy before scaling traffic.
Screenshots
See the workflow
Watch the paired walkthrough
Walkthrough1:32
See the same workflow in motion
A quick walkthrough of building, reviewing, and publishing a claimOS lead form.
Choose hosted or embedded delivery based on the workflow the team needs to run after submission.
Watch related walkthroughFAQ
Common questions
What should I verify before publishing a lead form?
Confirm field structure, live-vs-draft state, ownership of new submissions, and where the first test lead should appear in claimOS once the form is live.
How short should a lead form be?
Short enough to capture the next follow-up action without creating abandonment. Ask only for the information your team actually needs to start the intake workflow.
When should a team use hosted versus embedded delivery?
Use hosted when you want a standalone intake page and embedded when the form needs to live inside another property. Choose the mode that creates the cleanest first-notice experience for the submitter.
Keep Going