Fromenance for insurance carriers
Claims, billing, and policy messages your policyholders can verify
Fromenance is a communication provenance platform for insurance carriers: register claims, billing, and policy communications at send time, and a policyholder who forwards a suspicious one to verify@yourcarrier.com gets Verified, Not verified, or Known fraud in seconds. Adapters for Salesforce Marketing Cloud and Braze cover the enterprise sending stack, and every lure forwarded becomes an indicator for your SIU.
What your customers are receiving
The impersonation scenarios insurance carriers fraud teams see every week, and what a Fromenance verdict does to each one.
The claims payout lure
"Your claim has been approved, confirm your bank details" from yourcarrier-claims.com. Registered claims communications verify; this one returns Not verified and the payout page domain becomes an indicator.
The premium overdue notice
A fake billing notice with a payment link, timed to renewal season. Registered billing notices verify in seconds; the lure fails and its phone number and URL are extracted.
The policy document with a QR code
A PDF 'policy update' with a QR payload to a credential page. Policyholders upload a screenshot on yourcarrier.com/verify; OCR feeds 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, from a free mail account. Not in the 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 resolves to 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 an authoritative answer. verify@ answers in seconds, from your domain.
Register these streams first
Coverage is the whole game. Start with the communications customers already scrutinize, because those are the ones they will forward.
- 01
Claims communications
Claim received, adjuster assigned, payout issued. Highest fraud value and highest scrutiny. Register from the claims platform through the API or from SFMC through the reserve flow.
- 02
Billing and premium notices
Payment due, payment received, autopay changes. Template driven, high volume, and the most imitated around renewal.
- 03
Policy changes and renewals
Endorsements, renewals, cancellation warnings. Register through the ESP adapter (Salesforce Marketing Cloud and Braze are supported with a pre-send reserve call).
- 04
Documents and statements
Batch runs from the document vendor: the batch endpoint or a journal BCC on the vendor's sending system.
Outcomes you can put in front of the board
Every metric below is captured by the product itself, so the pilot report is a dashboard export.
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
Suspicious message triage per week, before and during. Verdict and indicators arrive attached.
Digital adoption
Policyholders who can verify a message keep opening real ones, which protects paperless and self service adoption.
A defensible record
Immutable verdicts and a timestamped registry give your compliance team a record of what was sent, when, and what the policyholder was told.
Compliance framing
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 customer 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.
The pilot, week by week
60 to 90 days on one stream, with onboarding help for the SFMC or Braze reserve flow.
Step 1: Week 0
Contract and DPA, tenant created, TXT record published, redirect rule live, forwarding test passed.
Step 2: Week 1
One stream registered, footer deployed to that template, reply identity live on your domain.
Step 3: Weeks 2 to 12
Run. Weekly 30 minute review of Submissions and Indicators with your fraud lead. Reports at day 30, 60, and 90.
Questions evaluators ask
- 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. Both are scrutinized by policyholders, both are heavily imitated, 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 your state 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. The Fromenance name never appears.
- What is stored about a policyholder?
- On a registration: a one way HMAC of their address and a content fingerprint, never the address or the body. On a submission: the forwarded message encrypted for your retention window and the submitter address encrypted and purged 30 days after the reply.
Run a 60 to 90 day pilot on one communication stream.
Fraud alerts or transaction alerts are the best first stream. You get a written report of verification volume, verdict distribution, campaigns discovered, and intelligence yield.