Claims, billing, and policy messages your policyholders can check in seconds

• The claims payout lure

  "Your claim has been approved, confirm your bank details" from yourcarrier-claims.com. Your registered claims messages verify. This one comes back Not verified and the payout page domain becomes an indicator for your SIU.

• The premium overdue notice

  A fake billing notice with a payment link, timed to renewal season. Your registered billing notices verify in seconds; the lure fails and its phone number and URL are pulled out.

• The policy document with a QR code

  A PDF "policy update" with a QR code to a credential page. Policyholders upload a screenshot on yourcarrier.com/verify; OCR reads it into the same deterministic extractors and the QR payload is stored.

• The agent impersonation

  Mail that looks like it comes from a captive or independent agent, sent from a free mail account. Not in your registry, so Not verified, and the sending address is an indicator you can share with the agency channel.

• The copied footer

  A lure that copies your verify footer comes back Not verified and raises a replay flag. The attacker just showed you which template they are imitating.

• The contact center question

  "Did you send me this?" is a call that costs roughly $8 to $15 and ends without a certain answer. verify@ answers in seconds, from your domain.

1. 01

   Claims communications

   Claim received, adjuster assigned, payout issued. Highest fraud value and highest scrutiny. Register from the claims platform with one call at send time, or from SFMC through the reserve flow.

2. 02

   Billing and premium notices

   Payment due, payment received, autopay changes. Template driven, high volume, and the most imitated around renewal.

3. 03

   Policy changes and renewals

   Endorsements, renewals, cancellation warnings. Register through the ESP adapter; Salesforce Marketing Cloud and Braze work with a pre-send reserve call.

4. 04

   Documents and statements

   Batch runs from the document vendor: the batch endpoint, or a journal BCC on the vendor's sending system.

• Fewer "is this real" calls

  Contact center volume on the pilot stream before and during, split by forward and web verification.

• Faster claims fraud response

  A claims payout lure is found by the policyholder it targeted, in the first hour, with the payout domain already extracted for your SIU.

• Agency channel protection

  Indicators from agent impersonation lures, exportable as CSV or STIX to share with agencies and your gateway.

• Analyst time back

  Suspicious message triage per week, before and during. The verdict and the indicators arrive attached.

• Digital adoption that holds

  Policyholders who can verify a message keep opening real ones, which protects paperless and self service adoption.

• A record you can defend

  Immutable verdicts and a timestamped registry give your compliance team a record of what was sent, when, and what the policyholder was told.

Carriers answer to state insurance regulators and, for many lines, to data security rules modeled on the NAIC Insurance Data Security Model Law. Fromenance gives you a documented, policyholder facing fraud control: immutable verdicts, an audited analyst trail, configurable retention, US data residency, and a DPA with a subprocessor list. We provide the evidence; your compliance team maps it to each state's requirements.

1. 1

   Step 1: Week 0

   We sign the contract and the DPA and create your tenant. You publish one TXT record and one redirect rule. The wizard sends itself a test message and tells you when the rule is right.

2. 2

   Step 2: Week 1

   You register one stream and paste the footer into that template. Replies go out from your own domain. The first customers usually ask that week.

3. 3

   Step 3: Weeks 2 to 12

   It runs. We sit with your fraud lead for 30 minutes a week over Submissions and Indicators, and you get a report at day 30, 60, and 90.

FAQ

Questions we get on the first call

We send from Salesforce Marketing Cloud. Does that work?

Yes. SFMC cannot hand us the rendered body, so a pre-send SSJS call reserves a verify code, an AMPscript merge field places it in the footer, and the send event completes the registration. Matching then leans on the code plus the recipient. Braze works the same way through connected content and a Liquid attribute.

Which stream should a carrier pilot first?

Claims communications or billing notices. Policyholders scrutinize both, attackers imitate both, and both are template driven enough to register from the ESP or the claims platform without a large project.

How does this relate to state insurance regulators?

Regulators increasingly ask about customer facing fraud controls and incident response. Fromenance gives you a documented control with an audit trail, retention you configure, and a data protection addendum. It is evidence for your program; your compliance team maps it to each state's requirements.

What does the policyholder see?

A reply from your reply identity in your branding with the locked verdict and a next step, or the same template rendered on yourcarrier.com/verify. Our name is nowhere on it.

What do you store about a policyholder?

On a registration: a one way hash of their address and a fingerprint of the text, never the address or the body. On a submission: the forwarded message encrypted for your retention window, and the submitter's address encrypted and purged 30 days after the reply.