Compare the in-force file against the DMF, work each match into evidence, run the good-faith beneficiary search on a confirmed death, track the dormancy clock by state, and prepare the escheat report.
A comparison runs against the in-force file, on the block's schedule and against DMF update files.
02
A match is returned, and the agent pulls the policy, the beneficiary record and the identifiers behind it.
Reason
03
Each possible match is worked up into evidence for and against, with a confidence score attached.
04
The block's own match-tolerance rules and state dormancy configuration are applied, not a generic default.
05
On a confirmed death, the good-faith beneficiary search runs and every contact attempt is logged.
Decide
06
Ambiguous matches, a stale beneficiary record and a dormancy clock at risk are flagged for the examiner.
07
The match, its evidence and the dormancy status are routed to the examiner named for the block.
Out
08
The match, the evidence, the search log and the examiner's decision stay on the policy.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent raises the match and assembles the evidence; the examiner confirms death and decides, and is the one who signs what goes to the state.
Example workflow
One match, comparison to report
AgentHuman
1Comparison runPeriodic in-force comparison against the full DMF and DMF update files
2Evidence assembledPolicy record, beneficiary record, contact history and identifiers — each against the match
3Match worked upEvidence for and against, confidence and dormancy status
4Controls appliedMatch-tolerance checks, LADMF-certification check, dormancy-rule fit and confidence threshold
No human action required
Stages 1 to 4 run unaided, and no death is confirmed at any of them — the agent is assembling evidence, and the examiner's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the examiner's queue as a match to confirm.
Low confidence
Adds a supplemental-identifier check first.
Examiner review
The match is held with its evidence, its search log and the confidence.
Decide · Request more evidence · Escalate
Decided — released to prepare filing▼
6Claims and policy systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedMatch accuracy, search outcomes, dormancy timing and post-filing corrections
Additional searches
Every additional search is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Confirming that a policyholder has died.
Determining eligibility or authorizing a claim payment.
Closing a policy or clearing it off the in-force file.
Reporting unclaimed property to a state administrator.
Automation boundaryAgent acts unaided
✓Run the periodic comparison against the in-force file and the DMF.
✓Work each possible match up into evidence for and against.
✓Apply the block's own match-tolerance and dormancy rules to the case.
✓Flag ambiguous matches and an at-risk dormancy clock.
Any write happens inside the boundaries agreed at implementation, never ahead of the examiner.
Initiating beneficiary contact — wording, channel and timing are a person's call.
Treating public DMF data as equivalent to certified LADMF access.
Assuming one dormancy-trigger position across every state.
Changes to match-tolerance rules or state dormancy configuration.
Example output
One match in the file, annotated
Everything the agent assembles is attached to the record it was drawn from.
Match-evidence output · single policyIllustrative example
Policy
Evidence line
Match strength
Evidence type
Confidence
Attribution
In-force whole-life policy, DMF match
Name and date of birth match the DMF record; the SSN field on the policy is incomplete
3 of 4 identifiers
DMF comparison result
86%
Examiner of record and licence ID
As receivedTaken from the comparison result and the policy record — nothing on this side is written by the agent.
Evidence usedDMF comparisonBeneficiary recordPolicy file history
Why this matchIt states what the comparison shows, not a death — the line the examiner weighs.
ActionDecideRequest more evidenceEscalate
What the score decidesBelow the configured threshold before it reaches the approver.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every policyFrom the in-force file
03Comparison
Compare against the DMF
Draw on the in-force file, the beneficiary records on file and the block's configured match rules.
01Approved path
A match is a question
Every match carries the evidence for and against it, not a bare name-match flag.
02Human review
Point the examiner at what needs
Low-identifier matches and stale beneficiary records are flagged, so review starts where confirmation is hardest.
04Build an evidence trail
The match, the evidence weighed against it and the examiner who confirmed stay on the policy.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
A file-level match rate can look clean while a handful of match types carry most of the false positives. Nestack reports the false-match rate by type, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Common names with partial identifiers
7.6%
3.9×
Review
Policies with stale beneficiary records
5.7%
3.0×
Review
Matches on retained-asset accounts
3.3%
1.7×
Watch
Exact matches on full identifiers
1.9%
0.8×
Normal
Bar: false-match rate lift vs. the exact-match baseline · scale 0–4.0× · tick at 2.0×2 of 4 slices over threshold
Evidence-linked improvement
Every cycle earns the file its next case
A cycle shuts when the false match is a case the next release has to catch. That suite is what the next comparison run is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
False-match rate rises in a block slice.
02Diagnose
The name that matched and belonged to someone alive is traced back through the comparison until the cause narrows to one field.
03Improve
The change ships against a version, with the matches that exposed it attached.
04Verify
A failing match case holds the release until it clears.
05Learn
The case joins the standing suite and the search rules move with it.
Learn → DetectThe return edge. Detection next time runs against a suite one match longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, DMF sources, comparison workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Comparison workflow discovery and scope and boundary definition.
02DMF and beneficiary-source assessment.
03Match-tolerance and dormancy-rule mapping and rule mapping.
04In-force file ingestion and normalisation.
05Evidence logic and source binding.
06Confidence scoring and flag routing.
07Examiner review workflow.
08DMF and policy-system integration.
09Match and dormancy cases.
10Guardrails and confirmation controls.
11Policy-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne block, one stateProductionProduction claims systemsAdvancedMultiple blocks / states
Introduced at Pilot
Comparison to your file and rules✓✓✓
Examiner review✓✓✓
Match-accuracy baseline✓✓✓
Introduced at Production
Reporting by state—✓✓
Examiner workflow in your systems—✓✓
Approved write-back—✓✓
Policy-file integration—✓✓
Introduced at Advanced
Multi-state escheat rules——✓
Multi-stage examiner review——✓
High in-force volume——✓
Multi-state escheat controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, block volume, review controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your in-force file structure and beneficiary records→In-force file ingestion and beneficiary-record mappingWeek 1
02Representative past matches, including false positives→Match-evidence baseline and confidence-scoring baselineWeek 2
03Your match-tolerance rules and state dormancy positions→Match-tolerance and dormancy-rule mappingWeek 1
04Access to relevant APIs, feeds or exports→DMF and policy-system assessment, then integration setupWeek 2
05Matches you would not want acted on→False-positive cases and the evaluation suiteWeek 4
06What no match may be treated as→Confidence scoring, flag routing, guardrails and confirmation controlsWeek 3
07Named examiners to confirm matches→Examiner review workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Each band sits on the weeks the work occupies, so week 5 runs evaluation and pilot together.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Comparison workflow discovery, rule mapping and the automation boundaryW2DMF-source integration and the match-evidence baselineW3Match workflow, confidence logic and examiner-review controlsW4Evaluation suite, confirmation checks and failure-mode testingW5DMF-vendor integration, pilot blocks and targeted correctionsW6One comparison cycle run under the claims examiner, then Agent Care handover
Reading the bandA bar covers the weeks its work is named in, and nothing else. The week 5 overlap is real, not padding.
At the end of W6The final checks clear on live matches and monitoring moves to Agent Care.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Insurance AI agent
Build a death-claims agent around your DMF and escheat obligations.
Show us your in-force file, your DMF certification status and your state list. You get matches raised as evidence, a documented search log, and every confirmation and filing left with a named examiner.
