Disconnection notice on the state clock
How do we send every disconnection notice with the required wording and timing, to the customer and any named third party, with delivery recorded on the state clock?
Run the notice sequence as a clock the account cannot skip. When an account reaches the collections trigger, Callvu classifies the account (the balance and its age, the service type, the customer class, the protections and the season, the third parties named for notice, the language preference), selects the notice the commission requires for the step (the first notice, the final notice, the day-of contact where the state requires one) with the required content (the amount, the date not before which service may be disconnected, the arrangement and assistance options, the dispute and complaint rights, the medical certificate right, the reconnection terms), delivers it by the method the rules allow with the timing counted in the rules' days, sends the copy to the named third party, records the delivery, holds the sequence where a protection or a dispute applies, and writes each notice and its dates to the billing system so the shutoff eligibility check can prove them.
In scopeComplex: multi-party handoffsCallvu moves: classify, write back
Last updated November 7, 2026.
The problem today
The notice went out in the wrong language without the medical certificate paragraph, four days short, and the disconnection was unlawful before the truck left.
Disconnection notices are the most regulated letters a utility sends and the most often wrong: a template that lacks a required paragraph, a mailing date that does not give the days the rules count, a third-party designee never copied, a customer whose language preference was on file and ignored. Each defect makes the disconnection unlawful, and the commission's penalties are per customer.
The commission's rules set the sequence (a first notice a set number of days before, a final notice, in some states a personal contact on the day), the content of each notice word for word in places, the delivery method and the counting of days, the third-party notice right, the language requirements, and the holds (a dispute, a medical certificate, a protected status, the moratorium). Every element is a rule on the account's data, and the proof is the record of what was sent, to whom, when.
A notice sequence that runs itself on the rules is the one the commission cannot fault.
How it runs
From the requestto the system of record.
An account reaches the collections trigger in the billing system (a balance past due beyond the grace period). Callvu classifies the account and starts the notice sequence.
- Customer
- Receives each notice with the options and the rights, and can pay, arrange or dispute from it.
- Named third party
- Receives the copy of the notice where the customer designated one.
- Credit and collections desk
- Decides holds and exceptions in the Decision Desk.
- Callvu
- Classifies, selects the notice, delivers on the clock, records, holds and writes.
Classify the account
The balance and its age, the service type (electric, gas, water, combined), the customer class, the protections on file (a medical certificate, a life support registration, a protected status, a pending dispute, a pledge, an arrangement in force), the season against the moratorium rules, the named third party for notice, the language preference and the delivery methods consented to are read and classified; a protection or a dispute holds the sequence at this step with the reason.
Select and deliver the notice
The notice for the step is selected with the required content for the state and the service type (the amount, the earliest disconnection date computed from the rules' days, the arrangement and assistance options, the dispute and commission complaint rights, the medical certificate right, the reconnection charges, the contacts), in the customer's language where the rules require, delivered by the method the rules allow (mail, with electronic delivery where consented), with the days counted as the rules count them (business or calendar, from mailing or receipt); the copy goes to the named third party; the final notice and the day-of contact follow on their own timing.
Record and write back
Each notice, its content version, the method, the date and the recipient (customer and third party) are written to the billing system and the CIS with the earliest disconnection date, so the shutoff eligibility check can prove the sequence before any order releases; a payment, an arrangement or a dispute from the notice's link stops the sequence.
Decide exceptions
An account with a conflict (a protection that expired during the sequence, a returned notice, a third party who cannot be reached, a language the templates lack) goes to the credit and collections desk in the Decision Desk with the record and only the allowed outcomes (continue, restart the sequence, hold, or refer to assistance).
Where it ends: Every notice carried the content the rules require, went to the customer and the third party by the allowed method on the counted days, and the billing system holds the proof the shutoff check will read. The Decision Trace shows the classification, the notice selection and any decision; the Audit Trace shows each delivery with recipient, method and time.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The customer meets the sequence in the notices, each with a link to pay, arrange or dispute.
The back office
Collections runs on the record; the credit desk decides only conflicts; the shutoff check reads the proof.
The Decision Desk
- A conflict in the sequence (an expired protection, a returned notice, an unreachable third party, a language gap) goes to the credit and collections desk in the Decision Desk with the record and only continue, restart, hold, or refer to assistance.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
PSEG Long Island runs start, stop and move service on Callvu, live in 4 weeks.
Across Callvu customers
Questions
What buyers ask next,answered plainly.
What must the notice contain?
What the state's rules require for the step: the amount, the earliest disconnection date, the ways to avoid disconnection, the arrangement and assistance options, the dispute and complaint rights, the medical certificate and protected status rights and the reconnection terms, in the required language.
How are the days counted?
As the rules count them for the state and the service type (business or calendar days, from mailing or receipt), computed into the earliest disconnection date on the record.
What stops the sequence?
A payment, an arrangement, a dispute, a protection or the moratorium; each holds the sequence at classification with the reason recorded, and the shutoff check reads it.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.