Skip to content
AI claims agent demo

AI Insurance Claim Agent: From the first chat to a signed form

Talk to a working claims agent built on BoldSign MCP. Then build one for your own claim forms.

Create API sandboxTry the live demo
  • Sends only from your approved template
  • Claimants sign on their own device
Insurance Claim Agent
My laptop was damaged by water at home yesterday. Policy CF-204817.
I’ve sent your claim form to sarah.mitchell@cubeflakes.com for signature.Document ID: 7c2a41f0…
What happened, and when?
Example conversation, sample data

Trusted by 100,000+ organizations worldwide

Samsonite
Ryanair
Hyatt
Sony
Crumbl Cookies
Payroc
Cost Plus
Why BoldSign

Why choose BoldSign for an AI insurance claims agent

BoldSign handles the signing step for your AI agent, so your developers build only the claim conversation.

  • One chat, start to signature

    Customers chat with your agent and receive the form to sign, without your team preparing it.

  • Plug and play setup

    Connect your agent to the hosted BoldSign MCP server, then add your claim steps to its instructions. Setup takes about 10 to 15 minutes, with no coding. See the setup steps

  • Approved templates only

    Your agent picks an approved template, fills in the claim details and sends it, without changing the wording.

  • No account for claimants

    Claimants open the signing link and sign in any browser, with no BoldSign account to create.

  • A sandbox to build in

    Build and test your claims agent in the API sandbox before going live.

The claim paperwork problem

Paperwork slows a claim down before anyone reviews it

  • Forms wait to be prepared

    Someone has to retype the claimant’s details into a claim form before the form can go out.

    With BoldSign

    Your AI agent fills the claim form from the chat and sends it.

    See the steps

  • Claimants lose the thread

    A claimant explains the incident, then waits for a form by email. When it arrives, they have to recall the details again.

    With BoldSign

    The claim form reaches the claimant when the conversation ends.

    Try the demo

  • Disputes need proof

    If a claimant later disputes a form, your team needs proof of who signed it and when.

    With BoldSign

    Every signed claim form carries an audit trail and a digital seal.

    See the controls

Live demo

Try the AI insurance claim agent demo

The BoldSign demo is a working claims agent for CubeFlakes, a fictional insurer. It is connected to a real BoldSign account. Describe a made-up incident and give your own email address. The claim form arrives in your inbox to sign.

Try saying

  • “My laptop was damaged by water at home yesterday.”
  • “My checked bag went missing on a flight last week.”
  • “My policy number is POL-12345.”
Live demoConnected to a BoldSign demo account
Open the claims agent demo in a new page

Demo only: claim forms from this demo are not legally binding, and no real claim is processed.

What arrives in your inbox

CubeFlakes via BoldSignSarah Mitchell, please sign: Claim form
CubeFlakes logo
CubeFlakes has requested you to review and sign Claim form.
Review and sign
CubeFlakes is the demo brand of a fictional insurer. Your claimants see your logo and brand colors in the email and on the form they sign.
How it works

What happens in an AI claim conversation, step by step?

With BoldSign MCP, a claim conversation becomes a signed claim form in 4 steps.

  1. The claimant describes the incident

    They say what happened and when, in plain words. The demo agent checks the policy number against its sample data and asks for anything missing.

    Insurance Claim Agent
    Hi, my laptop was damaged by water at home yesterday.
    I’m sorry to hear that. I’ll help you file the claim. Could you share your policy number?
    It’s CF-204817.
    Sample chat: the claimant describes the incident and gives a policy number

  2. Your AI agent fills the claim form

    It fills the claim form template your team built in BoldSign. Once the claimant confirms, it sends the form.

    CubeFlakes logoClaim form
    ClaimantSarah Mitchell
    Policy numberCF-204817
    Date of incidentOct 12, 2026
    What happenedLaptop damaged by a burst pipe
    Sign here
    Sample BoldSign signing page showing a CubeFlakes claim form with details filled from the chat and a signature field

  3. The claimant signs the claim form

    The claimant reviews the filled form and signs on their own device. BoldSign then seals the signed form.

    CubeFlakes logoClaim no. CL-48213
    Insurance Claim Form
    ClaimantSarah Mitchell Policy numberCF-204817 Date of incidentOct 12, 2026 What happenedLaptop damaged by a burst pipe
    Declaration
    Sarah MitchellClaimant signature
    Oct 13, 2026Date
    Sample signed CubeFlakes claim form, signed by Sarah Mitchell on Oct 13, 2026

  4. Your team gets the record

    BoldSign attaches an audit trail to the completed form. It names your BoldSign account as the sender.

    Audit trailClaim form
    Document ID7c2a41f0…
    SenderCubeFlakes Claims, claims@cubeflakes.com
    Sent by CubeFlakes ClaimsOct 13, 09:02:14 UTC
    IP +1 XXX XXX XXXX
    Viewed by Sarah MitchellOct 13, 09:05:41 UTC
    IP +1 XXX XXX XXXX
    Signed by Sarah MitchellOct 13, 09:07:03 UTC
    IP +1 XXX XXX XXXX
    CompletedOct 13, 09:07:05 UTC
    Sample BoldSign audit trail: sent by the CubeFlakes Claims account, viewed, and signed by Sarah Mitchell with timestamps and IP addresses, then completed
What the agent asks

What does a claims agent collect before it sends the form?

The BoldSign demo agent asks only what the claim form needs, in a set order. Your own agent can follow the same pattern.

  • The incident first

    What happened and when, in the claimant’s own words.

  • The policy number

    The demo checks it against sample data. Your agent would check your own policy system.

  • Name and email

    Where BoldSign sends the claim form for signature.

Setup

How do you send claim forms from Claude without code?

BoldSign MCP lets your claims team send claim forms from Claude Desktop. It needs no coding.

  1. Create an OAuth app in BoldSign

    Open API, then OAuth Apps. Copy the Client ID and Secret.

  2. Add BoldSign to Claude Desktop

    Add a custom connector with your region’s address, such as https://mcp.boldsign.com/mcp.

  3. Sign in and restart

    Approve access, then reopen Claude Desktop.

  4. Build your claim form template

    Upload your claim form and add a claimant role. Add fields for the policy number, incident date, and description.

  5. Send a claim form from chat

    Ask in one sentence. Claude confirms the claimant before it sends.

    “Send the Claim form template to Sarah Mitchell at sarah.mitchell@cubeflakes.com.”

Read the full setup guide, with screenshots

Control and proof

How do you keep an AI agent from sending the wrong claim form?

BoldSign MCP lets your AI agent send only the claim form templates your team has approved. The agent prepares and sends the form; the claimant signs it.

  • The claim form wording stays yours

    The agent fills the policy and incident fields. Your declaration and legal text stay as approved.

  • A summary before sending

    The demo agent shows the claim details and sends the form only after the claimant says yes.

  • An audit trail for every claim

    Each claim form records when it was sent, viewed, and signed, with timestamps and IP addresses.

  • A sealed, tamper-evident PDF

    Each completed document is digitally signed with an AATL certificate. If the file changes after signing, popular PDF viewers show it.

  • Legally binding signatures

    BoldSign complies with the ESIGN Act, UETA, and eIDAS, so its signatures are secure and legally binding.

Security

How is insurance claim data kept secure?

BoldSign protects claim forms and signer data with security controls audited for SOC 2 Type 2. Each standard BoldSign meets is shown below.

Compliance

BoldSign meets global security and compliance standards to protect your documents and data. Manage the settings below to align with your organization’s requirements.

US flag

Data Residency

Active (US - Global)

Your documents and signer data are securely stored in your selected region to meet data sovereignty and local regulatory requirements.

View Data Residency Policy
HIPAA logo

HIPAA Compliance

Enabled

Enable HIPAA mode to protect PHI using administrative, technical, and physical safeguards aligned with HIPAA regulations.

View Details
PCI DSS logo

PCI DSS

Compliant

Payments are securely processed through Stripe, a PCI DSS Level 1-certified provider, ensuring the safe handling and encryption of all payment data.

View PCI DSS Policy
CCPA logo

CCPA & CPRA

Compliant

Ensures compliance with California privacy laws, giving residents transparency and control over their personal data, including rights to access, delete, and opt out.

View Privacy Policy
AICPA SOC logo

SOC 2 Type II

Compliant

BoldSign has successfully completed a SOC 2 Type II audit, validating our controls for security, availability, confidentiality, and data integrity.

Request SOC 2
US flag

UETA & ESIGN

Compliant

BoldSign ensures that all e-signatures are legally binding and compliant with the U.S. ESIGN Act and the Uniform Electronic Transactions Act (UETA).

View UETA & ESIGN Policy
EU flag

eIDAS (SES)

Compliant

BoldSign complies with the EU eIDAS Regulation (910/2014) and supports Simple Electronic Signatures (SES) by default.

View SES Policy
EU flag

eIDAS (QES)

Enabled

Enable Qualified Electronic Signatures (QES) for contracts requiring the highest legal assurance under eIDAS.

View QES Policy
The compliance panel in your BoldSign account.
What it costs

Limits to know before you build a claims agent with BoldSign

BoldSign prepares, sends, tracks, and seals claim forms for signature. It does not assess claims, check coverage, or pay claims; your claims system and team do that.

Prices are in USD.

  • Enterprise API plan needed for live claim forms through BoldSign MCP From $30 a month with 40 envelopes, then $0.75 per envelope. Testing in the API sandbox is free. Prices are in USD.
See API plans and pricing
Good to know
  • 2,000 API requests an hour per account, in production
  • 14 actions your agent can call through BoldSign MCP Documents, templates, contacts, users, and teams (tool list).
For developers

How do you build an insurance claims agent like this one?

Developers link the claims agent to your policy system and call BoldSign MCP for the signing step.

Common questions

Questions about AI insurance claim agents and eSignatures

What is an AI insurance claim agent?

An AI insurance claim agent holds the first conversation with a policyholder. It collects the incident details and sends the claim form for signature. The BoldSign demo shows that flow from the first message to the signing request.

Can AI automate insurance claim intake?

Yes. An AI agent can take the claim details in chat. Through BoldSign MCP, it prepares the claim form for signature. The claimant still signs, and your claims team still reviews and decides the claim.

Can an adjuster or supervisor sign the same claim form?

Yes. BoldSign supports several signers on one document, in the signing order you set. The public demo sends to one signer to keep it simple to try.

Does the claimant need a BoldSign account to sign?

No. BoldSign sends the claimant a signing link by email, and they sign without an account.

Is the demo insurer a real company?

No. CubeFlakes is a fictional company made for BoldSign demos. No real policy, claim, or customer data is used.

Related

More on AI and eSignatures for insurance

BoldSign pages cover the rest of the insurance workflow, every MCP agent demo, and how signers are verified.

  • Page

    eSignatures for insurance

    Policies, renewals, underwriting, and agent agreements.

    See the page
  • Demos

    All BoldSign MCP agent demos

    Lease signing, patient check-in, HR onboarding, and more.

    See the demos
  • Blog

    Identity verification in the age of AI

    How to confirm the right person signs.

    Read the post
  • Blog

    Introducing BoldSign MCP

    What the MCP server does and how agents use it.

    Read the post
How it works

How does an AI agent send an insurance claim form for eSignature?

With BoldSign MCP, your AI agent turns a claim conversation into a signature request. It fills your approved claim form with the claimant’s details. Then BoldSign emails the form to the claimant to sign.

Works in: BoldSign MCP with Claude, ChatGPT, or an AI agent you build. Claimants sign in any browser, on a phone or a computer.

Get started

Start building your AI claims agent in the API sandbox

Or book a walkthrough of a claims agent with the BoldSign team.

Create API sandboxBook a walkthrough
  • 30-day free trial
  • No credit card required

Last updated: October 16, 2026