Outage, billing, and disconnection notices your customers can check before they pay

• The disconnection threat

  "Your service will be disconnected today unless you pay now", with a payment link or a phone number. The most common utility lure there is. Your registered disconnection notices verify; this one fails and the phone number is pulled out as an indicator.

• The overpayment refund

  "You overpaid, claim your refund", pointing at a card harvesting page. Not in your registry, so Not verified, and the domain is on your fraud list after one analyst click.

• The outage update

  During a real outage, lures ride the news. Your registered outage notices verify in seconds, so customers can tell the real update from the fake one while the lights are still off.

• The smart meter or rebate notice

  Program enrollment lures on a lookalike domain. Screenshot upload handles the ones that arrive as images.

• The copied footer

  A lure that copies your verify footer comes back Not verified and raises a replay flag. It tells your team which notice template is being imitated.

• The "is this real" call

  Each one costs roughly $8 to $15, and they peak exactly when the contact center is busiest. verify@ answers in seconds without an agent.

1. 01

   Billing notices

   Bill ready, payment due, payment received, autopay changes. Highest volume, most imitated. Register from the ESP webhook or the billing platform's journal BCC.

2. 02

   Disconnection and collections notices

   The lure attackers reach for first. Register these and Authoritative Mode becomes reachable for the stream customers fear most.

3. 03

   Outage and service notices

   Planned work, outage updates, restoration. Register through the ESP adapter so real updates verify during an event.

4. 04

   Program and rebate communications

   Energy efficiency, smart meter, and rebate enrollment messages. Batch endpoint, or the journal path from the program vendor.

• Call deflection at peak

  Contact center "is this real" volume on the pilot stream before and during, including during outages, when it matters most.

• Fewer payment scams that complete

  Customers who check before paying do not pay the lure. Time from first submission to analyst confirmation of a campaign shortens the window.

• Abuse mailbox triage

  Volume before and during, and analyst time per week. Submissions arrive with indicators and a verdict.

• Intelligence yield

  Phone numbers, domains, and payment page URLs from lures, exportable as CSV or STIX for your gateway and for law enforcement referrals.

• Trust in real notices

  Customers who can verify a disconnection notice keep reading them, which protects collections and paperless billing.

• A documented control

  Immutable verdicts and audited analyst actions give your customer protection program a record for regulators and commissions.

Public utility commissions and consumer protection offices ask utilities how customers are protected from payment scams and impersonation. Fromenance gives you a documented, customer facing control with immutable verdicts, an audited analyst trail, configurable retention, and exportable indicators for referrals. We provide the record; your regulatory team frames it for your commission.

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

Which stream should a utility pilot first?

Billing notices or disconnection notices. Both are imitated constantly, both are template driven, and customers already scrutinize them. Outage notices come second, because real updates need to verify during an event.

Our customers get lures by phone and text too. Does this help?

Phone numbers and QR codes in forwarded email lures are extracted as indicators today. The SMS channel, with the same code in a shorter footer and verification by short code or web paste, is on the roadmap. Voice is scoped later.

How much DNS do we have to touch?

One TXT record for trust. If you want replies from a subdomain such as verify.yourutility.com, three more records for the sending domain. The web verify page needs none.

What does the customer see?

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

Our billing vendor cannot call an API. Now what?

Add journal-{slug}@ingest.fromenance.com as a BCC or journaling target on the vendor's sending system and we register from the full message. Pair it with a static per template code or the reserve flow so the footer still carries a code.