Insurance claims & broker submission intake

The challenge

First notice of loss forms, photos of damage, policy schedules, broker slips, the occasional garbled forward chain — insurance intake is still an inbox problem.

Before an adjuster assesses a claim or an underwriter prices a risk, someone spends time triaging: which policy is this, what type of submission is it, where do the attachments belong, and what's missing? That manual re-keying happens on every single submission, and it happens before any actual assessment work begins.

The solution

Every intake channel becomes an email alias.

Claimants and brokers send to a dedicated address — claims@ingest.insurer.com or submissions@ingest.broker.com — and EmailConnect parses everything into structured JSON: sender, subject, body, and every attachment.

That payload feeds straight into your claims or underwriting system — Guidewire, Applied Epic, a custom queue, or an n8n workflow that extracts the policy number, routes by submission type, and files the attachments against the right record. No inbox triage, no re-keying.

{
  "message": {
    "sender": {
      "name": "Jan de Vries",
      "email": "jan.devries@example.com"
    },
    "recipient": {
      "email": "claims@ingest.insurer.com"
    },
    "subject": "FNOL — Policy #NL-2024-8871 water damage",
    "content": {
      "text": "Hello,\n\nReporting water damage at our property following a burst\npipe on 28 June. Claim form and photos attached.\n\nRegards,\nJan de Vries"
    },
    "attachments": [
      {
        "filename": "fnol_claim_form.pdf",
        "contentType": "application/pdf",
        "size": 184213
      },
      {
        "filename": "damage_kitchen.jpg",
        "contentType": "image/jpeg",
        "size": 2841119
      },
      {
        "filename": "damage_hallway.jpg",
        "contentType": "image/jpeg",
        "size": 2653004
      }
    ]
  },
  "spam": {
    "isSpam": false,
    "authentication": {
      "dkim": { "result": "pass" },
      "spf": { "result": "pass" }
    }
  }
}

Showing relevant fields only. See the full webhook payload reference →

The workflow automatically

• Extracts the policy/claim number from the subject or body via regex or an LLM step
• Routes by submission type (FNOL vs broker slip vs supporting document)
• Attaches photos and PDFs to the correct claim record
• Flags missing required documents (e.g. no photos on a damage claim)
• Notifies the assigned adjuster or underwriter
• Maintains an audit trail for regulatory record-keeping

The results

Intake stops being a queue. Instead of an adjuster opening each email, reading it, and copying details into the claims system, submissions arrive already parsed, routed, and filed — ready for assessment. The people who cost the most are freed from the work that costs the least.

The figures below are an illustrative example of a typical setup, not a specific customer's reported results.