Stop service and final bill address
How do we take a stop service request with the stop date checked against the minimum notice and the final bill address captured, and write the stop order to CIS?
Take the date and the address once, check them, and write the order. Callvu identifies the customer and prefills the account from CIS (the premise, the services, the meters, the balance, the deposit, the mailing address), takes the stop date and the final bill address on a secure screen, checks the date against the tariff's minimum notice and the field schedule where a final read needs a visit, validates the address, explains what the final bill will include (the usage to the stop date, the balance, the deposit applied with interest) and when it will arrive, captures the customer's confirmation, and writes the stop order with the final bill address to CIS and the billing system.
In scopeSimpleCallvu moves: prefill, write back
Last updated November 7, 2026.
The problem today
The final bill went to the house the customer had left, and the collections letter followed it there.
A stop is simple and still goes wrong: the date is taken for a day the tariff does not allow, the final read needs a visit nobody scheduled, the forwarding address is never asked for or is mistyped, and the final bill, with the deposit credit the customer is owed, chases an empty premise into collections. The customer who left on good terms is a bad debt by spring.
The tariff sets the minimum notice for a stop, the final bill's issue within a set period after the stop with the deposit and its interest applied, and the customer's responsibility for usage until the stop date. The forwarding address is the one data point that decides whether the final bill is paid. A stop taken on a screen with the date checked and the address validated is a final bill that arrives.
The stop is the last impression, and the final bill is its envelope.
How it runs
From the requestto the system of record.
A customer requests a stop online, in the app, from the Visual IVR or with an agent. Callvu identifies them and prefills the account.
- Customer
- Enters the stop date and the final bill address and confirms on a secure screen.
- Agent
- Sends the link on a call or works the same screen.
- Callvu
- Prefills, checks the date and the address, explains the final bill, captures the confirmation and writes.
Prefill
The account is prefilled from CIS: the premise and the services, the meters and whether the final read is remote or needs a visit, the balance and any arrangement, the deposit on file with its accrued interest, and the mailing and email contacts.
Capture and check
The customer enters the stop date, which is checked against the tariff's minimum notice and, where a visit is needed, the field schedule; the final bill address (a new postal address, or email where the customer has paperless consent) is entered and validated against the postal reference; a stop on a premise with a landlord continuous service agreement or a shared meter is flagged.
Explain and confirm
The customer sees what the final bill will include (the usage to the stop date, the outstanding balance, the deposit and its interest applied, any fees the tariff allows) and when it will arrive, and confirms; a date inside the notice offers the earliest allowed date; a flagged premise goes to the service desk in the Decision Desk with the request and only the allowed outcomes.
Write back
The stop order with the stop date, the final read instruction and the final bill address is written to CIS and the billing system, the field order is created where a visit is needed, and the customer receives the confirmation with the date and the final bill timing.
Where it ends: The stop was taken once with a date the tariff allows and an address the final bill will reach, the customer knew what the bill would include, and CIS holds the order. The Decision Trace shows the date and address checks; the Audit Trace shows the entries, the confirmation and the order with 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 website, the app, the Visual IVR's link or an agent's link.
The back office
Nobody retypes; the service desk sees only flagged premises; billing issues the final bill from the order.
The Decision Desk
- A premise with a landlord continuous service agreement, a shared meter or a dispute about the stop date goes to the service desk in the Decision Desk with the request and only the allowed outcomes.
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.
How much notice is needed?
The tariff's minimum, commonly one to three business days; the screen checks the date and offers the earliest allowed one.
What is on the final bill?
The usage to the stop date, the outstanding balance, the deposit with its interest applied, and any fee the tariff allows; the customer sees this before confirming.
Where does the final bill go?
To the forwarding address the customer enters and the process validates, or by email where the customer has consented to electronic delivery.
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.