Template Overview

This insurance claim form template takes first notice of loss online. It opens by asking which policy the claim is against, then routes the claimant down a path built for that policy type, so a motor claim asks for a registration number and a travel claim asks where the incident happened. Each path collects the contract number, when and how the event occurred, the insured person's details, and a scan of an ID document, then closes with a signature and a confirmation screen.

Worth being clear about what this is not. It is not the CMS-1500, the standardized health insurance claim form that providers use to bill Medicare, Medicaid, and private health insurers. If you need to submit a professional medical claim, you need that form, not this one. This template is for the other side of the process: insurers, brokers, MGAs, and agencies that want policyholders to report a loss through a branded online form instead of a PDF attached to an email.

Because every path ends in the same structured submission, what reaches your team is consistent regardless of which claim type came in. Conditional logic means the claimant never sees a field that does not apply to them, which is the main reason digital intake produces fewer incomplete claims than a general-purpose PDF. Configure the acknowledgement email so every claimant gets written confirmation with a reference and an expected timeline, and route submissions to the right adjuster or inbox by claim type in the Connect tab.

Key Features

Branching by insurance type using Logic Jumps, so motor, travel, and life claims each follow a path that asks only what that policy needs.
Document upload for an ID or passport scan and any supporting evidence, attached to the claim rather than chased over email afterwards.
E-signature at the end of the flow, giving you the claimant's attestation that the account of the incident is accurate.
Date and structured incident capture separating when the event occurred from when it was reported, which is a field your team will use constantly.
Automatic acknowledgement email to the claimant on submission, so nobody has to phone in to ask whether the claim arrived.

Benefits

Fewer incomplete claims. Required fields and type-specific paths mean a claim cannot be submitted missing the contract number or the incident date, which is where most back-and-forth starts.
Documents arrive with the claim. Collecting the ID scan and evidence inside the form removes the slowest step in a typical intake process, which is waiting for attachments.
Claimants stop chasing you. An automatic acknowledgement with a reference and a realistic timeline cuts status-check calls and sets expectations in writing.
Claims land where they belong. Route by claim type to the right adjuster, team inbox, or claims system through the Connect tab, so triage happens on submission rather than in someone's morning.
Claim data is handled properly. involve.me is SOC 2 Type II audited and GDPR-compliant, with CAPTCHA and password protection available on the funnel itself.

How it works

Customize
Replace the placeholder branding, edit the policy types on the first question to match what you underwrite, and rewrite the field labels in your own claims language. Adjust which fields are required per path, and set the wording on the confirmation screen.
Configure
Set the Logic Jumps that send each policy type down its own path, turn on CAPTCHA, and write the acknowledgement email with a reference and an expected response time. Enable partial submissions so a claimant who stops to find a document can come back and finish.
Connect
In the Connect tab, send claims to your claims system, CRM, or shared inbox using 50+ native integrations, Zapier, or webhooks. Route by claim type so motor and travel claims reach different teams, and map the policy number to a contact property.
Share
Publish as a standalone claims page you can link from your policy documents and renewal emails, or embed it inline or as a pop-up in your customer portal with a div wrapper and script tag. Password protect it if claims should only be filed by logged-in policyholders.
Analyze
See where claimants abandon the flow, which policy types generate the most claims, how long submissions take to complete, and export the full claim record when the claims system needs it.

Frequently Asked Questions

: Policy or contract number, the identity of the insured person, the date and time the event occurred, a description of how it occurred, the extent of the loss or damage, any third parties involved, and supporting documents. Keep the incident date separate from the submission date, because the gap between them is something every claims team checks.
: Yes, and this is the main advantage over a single PDF. The first question asks which policy the claim is against, and Logic Jumps send the claimant down a matching path. Motor claims can ask for a registration number and whether the policyholder was driving, travel claims can ask which country the incident occurred in, and nobody sees fields that do not apply to them.
: Yes. The flow ends with an e-signature so the claimant attests that their account is accurate. That gives you a dated record of what was declared, which matters if a claim is later disputed.
: Yes. Configure the participant email so every submission triggers written confirmation. Include a claim reference and a realistic expected response time, and you will remove most of the status-check calls that otherwise follow a claim submission.
: Yes. Send submissions onward through 50+ native integrations, Zapier, or webhooks, and use the claim type or region to decide the destination, so motor claims reach one team and travel claims reach another. Triage then happens at submission instead of in a shared inbox.
: Turn on CAPTCHA to block automated submissions and OTP verification to confirm the claimant's email or phone. For duplicates, the structured fields do the work: the same policy number arriving twice, or an incident date that does not line up with the reported date, is easy to spot when every claim has the same shape.
: Yes. Embed it inline inside a portal page or as a pop-up triggered by a button, using a div wrapper and script tag. The standalone page URL stays available at the same time, which is what you would print in policy documents or link from a renewal email.
: Yes. The flow is one question or short group per screen, which suits a phone better than a multi-page PDF, and the upload field accepts photos taken on the device. That matters most for motor and property claims, where the evidence is best captured immediately.
: The free plan includes 3 live funnels and covers this template. Paid plans start at $29 per month billed annually and add funnel capacity, branding removal, and custom domains, with partial submissions and webhooks available on higher plans.
: An insurance form template is a pre-built, customizable form designed for insurance-related workflows — collecting applications, processing claims, generating quotes, or enrolling members. You can adjust the fields, logic, and design to match your specific insurance line and branding, then publish the form on your website or share it as a standalone link.