Processes Callvu runs

Utilities

Electric, gas and water processes that start at a call, a web visit, an agency or a field crew, need identity, documents or approvals, and must end correctly in CIS, billing or the work system. This list is illustrative, not exhaustive: Callvu runs the utility's own processes.

In production

Proof at scale,not one process at a time.

  • More than 1,000 processes are live across Callvu customers.
  • PSEG Long Island runs start, stop and move service on Callvu, live in 4 weeks.

These processes are examples, not a complete list. Callvu runs the customer's own regulated processes: any process that starts at a front door (form, call, chat, AI agent, branch, email), needs data, documents, signatures or approvals, and must end correctly in a system of record.

Live, published
Live at the named customer, with a published use case and claims on agents.callvu.com.
Live at a customer
Live in production at a customer. Reference on request.
In scope
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process.

Start, stop and transfer service

  • Start, stop and move service

    Live at PSEG Long IslandComplex: multi-party handoffs

    Started from Visual IVR or by an agent with the customer, the account is prefilled, dates, forwarding address and final bill address captured, then written to CIS and billing.

    Parties: Customer, Contact center agent, CIS, Billing. Rules: State commission tariff rules. Callvu moves: prefill, classify, decide, write back. Use case and claims

  • Failed self-service request returned to an agent

    Live at PSEG Long IslandComplex: multi-party handoffs

    When a start, stop or move cannot finish, the customer returns to an agent whose screen opens with the IVR details and the reason it stopped.

    Parties: Customer, IVR, Contact center agent, CIS. Callvu moves: prefill, classify, write back. Use case and claims

  • Service transfer between addresses

    In scopeComplex: multi-party handoffs

    Started online or on a call, the old address is closed and the new one opened in one request, with balance transfer and deposit rules applied before CIS is updated.

    Parties: Customer, Contact center agent, Credit team, CIS, Billing. Rules: State commission tariff rules. Callvu moves: prefill, classify, decide, write back.

  • Stop service and final bill address

    In scopeSimple

    The customer gives the stop date and where the final bill goes, the date is checked against the minimum notice, and the stop order is written to CIS.

    Parties: Customer, CIS. Rules: State commission tariff rules. Callvu moves: prefill, write back.

  • Start service for a new customer

    In scopeComplex: multi-party handoffs

    A new customer starts service online or by phone with identity verified, premise matched, deposit decided and the account created in CIS.

    Parties: Customer, Credit team, CIS, Billing. Rules: State commission tariff rules; FTC Red Flags Rule identity theft program. Callvu moves: prefill, classify, decide, write back.

  • Account name change

    In scopeSimple

    A name change after marriage, divorce or death is requested with supporting documents, verified and written to the account.

    Parties: Customer, Account services, CIS. Callvu moves: chase and verify, decide, write back.

  • Service after an account holder's death

    In scopeComplex: multi-party handoffs

    A family member or estate reports a death, provides the documents, and the account is closed, transferred or placed with the estate, with the final bill routed correctly.

    Parties: Family member or executor, Account services, Collections, CIS. Rules: State commission tariff rules. Callvu moves: chase and verify, classify, decide, write back.

  • Seasonal service suspension and restoration

    In scopeSimple

    A seasonal or vacation property owner requests suspension and restoration dates, which are checked against tariff rules and scheduled in CIS.

    Parties: Customer, CIS, Field operations. Rules: State commission tariff rules. Callvu moves: prefill, decide, write back.

Account, identity and authorization

  • Identity verification before account changes

    In scopeSimple

    Every phone, web and IVR request verifies identity the same way before any account change, with the result recorded on the request.

    Parties: Customer, CIS. Rules: FTC Red Flags Rule identity theft program. Callvu moves: chase and verify, decide.

  • Identity theft and fraudulent account claims

    In scopeComplex: multi-party handoffs

    A customer reports service opened in their name, provides an affidavit and ID, and the case is investigated, decided and the account corrected or closed.

    Parties: Customer, Fraud team, Collections, CIS, Credit bureau. Rules: FTC Red Flags Rule identity theft program. Callvu moves: chase and verify, classify, decide, write back.

  • Add or remove an authorized contact

    In scopeSimple

    The account holder names or removes a person who may act on the account, with consent captured and the permission written to CIS.

    Parties: Account holder, CIS. Callvu moves: prefill, write back.

  • Third-party notification enrollment

    In scopeSimple

    A customer names a relative or caregiver to receive copies of shutoff notices, with consent captured and the contact stored for notice runs.

    Parties: Customer, Third party, CIS. Rules: State commission disconnection notice rules. Callvu moves: prefill, write back.

  • Contact details and paperless billing changes

    In scopeSimple

    Phone, email, mailing address and paperless consent are updated with identity checked and the change written to CIS.

    Parties: Customer, CIS. Rules: TCPA consent for automated calls and texts. Callvu moves: prefill, write back.

  • Language and accessibility preferences

    In scopeSimple

    A customer records a preferred language, large print or braille bills, or a hearing or vision need, and every future notice follows it.

    Parties: Customer, CIS, Print vendor. Callvu moves: prefill, write back.

Deposits and credit

  • Deposit and credit decisions inside the request

    In scopeComplex: multi-party handoffs

    The deposit decision is made during the start or transfer request by rule, with credit checks, waivers and the amount written to billing.

    Parties: Customer, Credit team, Credit bureau, Billing. Rules: State commission tariff rules; FCRA adverse action notice when a credit report drives the decision. Callvu moves: classify, decide, write back.

  • Deposit waiver with letter of credit history

    In scopeComplex: multi-party handoffs

    A customer submits a good-payment letter from a prior utility, it is checked on arrival and the deposit is waived or reduced.

    Parties: Customer, Prior utility, Credit team, Billing. Rules: State commission tariff rules. Callvu moves: chase and verify, decide, write back.

  • Deposit installment plan

    In scopeSimple

    A required deposit is split into installments the customer accepts, and the schedule is written to billing.

    Parties: Customer, Billing. Rules: State commission tariff rules. Callvu moves: prefill, decide, write back.

  • Deposit refund or transfer

    In scopeSimple

    After good payment history or a stop, the deposit is refunded, applied to the final bill or transferred to a new account by rule.

    Parties: Customer, Billing. Rules: State commission tariff rules. Callvu moves: classify, decide, write back.

  • Adverse action notice for credit-based deposits

    In scopeSimple

    When a credit report drives a deposit, the required notice is produced and delivered with the reasons, and delivery is recorded.

    Parties: Customer, Credit team, Credit bureau. Rules: FCRA adverse action notice when a credit report drives the decision. Callvu moves: classify, write back.

Billing and payments

  • Payments on a secure screen during a call

    In scopeSimple

    The agent sends a secure payment screen during the call, the customer pays without reading card details aloud, and the payment posts to billing.

    Parties: Customer, Contact center agent, Payment processor, Billing. Rules: PCI DSS. Callvu moves: prefill, write back.

  • Autopay enrollment and changes

    In scopeSimple

    A customer enrolls in or changes autopay with authorization captured and the mandate written to billing.

    Parties: Customer, Billing, Payment processor. Rules: NACHA authorization rules. Callvu moves: prefill, write back.

  • Budget billing enrollment

    In scopeSimple

    Eligibility is checked, the levelized amount is shown, the customer accepts and the plan is written to billing.

    Parties: Customer, Billing. Rules: State commission tariff rules. Callvu moves: prefill, decide, write back.

  • Billing dispute and adjustment

    In scopeComplex: multi-party handoffs

    A disputed bill is captured with the reason and evidence, routed to review, decided and the adjustment written to billing, with collection held while it is open.

    Parties: Customer, Billing analyst, Supervisor, Billing, Collections. Rules: State commission tariff rules; State commission disconnection notice rules. Callvu moves: classify, chase and verify, decide, write back.

  • High bill investigation

    In scopeComplex: multi-party handoffs

    A high bill complaint triggers a usage review, a possible meter check and a field visit, with the outcome and any rebill recorded.

    Parties: Customer, Billing analyst, Field technician, Billing. Rules: State commission service quality rules. Callvu moves: classify, chase and verify, decide, write back.

  • Estimated bill correction with customer read

    In scopeSimple

    The customer submits a meter read with a photo, it is checked against history, and the bill is recalculated.

    Parties: Customer, Billing. Callvu moves: chase and verify, decide, write back.

  • Credit balance refund request

    In scopeSimple

    A customer with a credit balance asks for a refund, the payee and method are verified and the refund is issued from billing.

    Parties: Customer, Billing, Accounts payable. Callvu moves: chase and verify, decide, write back.

  • Returned payment handling

    In scopeSimple

    A returned check or failed bank payment triggers a notice, a fee by tariff, a cash-only flag when rules require, and a request for new payment.

    Parties: Customer, Billing, Payment processor. Rules: State commission tariff rules. Callvu moves: classify, decide, write back.

  • Payment due date extension

    In scopeSimple

    A customer asks for more time, eligibility is checked by rule, and the new due date is written to billing and collections.

    Parties: Customer, Billing, Collections. Rules: State commission tariff rules. Callvu moves: classify, decide, write back.

Collections, disconnection and reconnection

  • Payment arrangement or deferral

    In scopeComplex: multi-party handoffs

    An arrangement is offered by rule, accepted by the customer, confirmed in writing and written to billing in one flow.

    Parties: Customer, Contact center agent, Collections, Billing. Rules: State commission tariff rules; State commission disconnection notice rules. Callvu moves: prefill, decide, write back.

  • Disconnection notice on the state clock

    In scopeComplex: multi-party handoffs

    Each notice goes out with the required wording and timing, to the customer and any named third party, and delivery is recorded.

    Parties: Customer, Third party, Collections, Print and notification vendors. Rules: State commission disconnection notice rules. Callvu moves: classify, write back.

  • Shutoff eligibility check before field order

    In scopeComplex: multi-party handoffs

    Before a shutoff order is released, the account is checked for medical holds, pledges, disputes, arrangements and weather or seasonal moratoriums.

    Parties: Collections, Credit and assistance teams, Field operations, CIS. Rules: State commission disconnection notice rules; Winter and extreme weather moratorium rules. Callvu moves: classify, decide, write back.

  • Shutoff blocked by a medical hold, with an arrangement offered

    In scopeComplex: multi-party handoffs

    A shutoff that hits a medical hold is stopped, the customer is offered a payment arrangement, and the hold and outcome are recorded.

    Parties: Customer, Collections, Medical certification team, CIS. Rules: State commission disconnection notice rules. Callvu moves: classify, decide, write back.

  • Reconnection after payment

    In scopeComplex: multi-party handoffs

    Once payment or an arrangement clears, the reconnection is requested, fees applied by tariff and the field order issued within the required time.

    Parties: Customer, Collections, Field dispatch, Field technician, CIS. Rules: State commission tariff rules; State commission disconnection notice rules. Callvu moves: classify, decide, write back.

  • Final bill collection before agency placement

    In scopeComplex: multi-party handoffs

    Unpaid final bills get the required notices and a last payment offer before the account goes to an outside collection agency.

    Parties: Former customer, Collections, Collection agency. Rules: State commission tariff rules; FDCPA for third-party collectors. Callvu moves: classify, chase and verify, decide, write back.

  • Bankruptcy notice handling

    In scopeComplex: multi-party handoffs

    A bankruptcy notice is captured, collection stopped, the account split into pre- and post-petition balances and any adequate assurance deposit decided.

    Parties: Customer or attorney, Credit team, Legal, Billing. Rules: U.S. Bankruptcy Code utility provisions. Callvu moves: chase and verify, classify, decide, write back.

  • Tenant notice before shutoff at a landlord-billed property

    In scopeComplex: multi-party handoffs

    When a landlord-paid account faces shutoff, tenants at the address get the required notice and an option to take over service.

    Parties: Landlord, Tenants, Collections, CIS. Rules: State commission disconnection notice rules. Callvu moves: classify, chase and verify, write back.

Assistance, hardship and protections

  • Assistance pledges from agencies

    In scopeComplex: multi-party handoffs

    Agencies submit pledges on their own link, the account is protected the moment a pledge arrives, and the payment is matched when it lands.

    Parties: Assistance agency, Customer, Credit and collections, Billing. Rules: LIHEAP and state assistance program rules. Callvu moves: chase and verify, classify, write back.

  • Low-income program enrollment

    In scopeComplex: multi-party handoffs

    Applications for discount rates are complete before review, with income documents checked on arrival and the rate written to billing.

    Parties: Customer, Program team, Billing. Rules: LIHEAP and state assistance program rules. Callvu moves: prefill, chase and verify, decide, write back.

  • Hardship applications

    In scopeComplex: multi-party handoffs

    Hardship requests are captured once, documents chased until complete, decided by rule or reviewer, and the result written to the account.

    Parties: Customer, Assistance team, Collections, Billing. Rules: LIHEAP and state assistance program rules. Callvu moves: chase and verify, decide, write back.

  • Arrearage management program enrollment

    In scopeComplex: multi-party handoffs

    An eligible customer enrolls in a debt forgiveness plan, agrees to the payment terms, and monthly credits are applied by rule as payments arrive.

    Parties: Customer, Assistance team, Billing. Rules: LIHEAP and state assistance program rules. Callvu moves: prefill, chase and verify, decide, write back.

  • Medical certificate and renewal

    In scopeComplex: multi-party handoffs

    A physician's certification is requested, received and checked, the account protected for the certified period, and renewal chased before it ends.

    Parties: Customer, Physician, Medical certification team, CIS. Rules: State commission disconnection notice rules. Callvu moves: chase and verify, decide, write back.

  • Life support equipment registration

    In scopeComplex: multi-party handoffs

    A customer who depends on powered medical equipment registers, the need is verified, and the account is flagged for outage and shutoff priority.

    Parties: Customer, Physician, Customer care, Outage and collections teams. Rules: State commission disconnection notice rules. Callvu moves: chase and verify, decide, write back.

  • Senior, disability and military protection status

    In scopeSimple

    A customer claims a protected status with proof, it is verified and the protection applied to shutoff and notice rules.

    Parties: Customer, CIS. Rules: State commission disconnection notice rules. Callvu moves: chase and verify, decide, write back.

  • Annual program recertification

    In scopeSimple

    Discount and protection program customers are reminded before expiry, submit updated proof, and the status is renewed or removed on the record.

    Parties: Customer, Program team, Billing. Rules: LIHEAP and state assistance program rules. Callvu moves: chase and verify, decide, write back.

Outages, damage and claims

  • Outage report

    In scopeSimple

    A customer reports an outage from any channel, it is matched to the premise and any known event, and the ticket goes to the outage system with updates by text.

    Parties: Customer, Outage management system. Rules: TCPA consent for automated calls and texts. Callvu moves: prefill, classify, write back.

  • Outage credits by rule

    In scopeSimple

    Credits for long outages are decided by the commission or tariff rule and written to billing, with the decision on the record.

    Parties: Customer, Billing. Rules: State commission service quality rules. Callvu moves: classify, decide, write back.

  • Food and medicine spoilage reimbursement

    In scopeComplex: multi-party handoffs

    After a qualifying outage, a customer submits receipts or a list, eligibility is checked by rule and the reimbursement is paid or credited.

    Parties: Customer, Claims team, Billing. Rules: State commission service quality rules. Callvu moves: chase and verify, decide, write back.

  • Customer property damage claim

    In scopeComplex: multi-party handoffs

    A customer claims damage from a surge or utility work, photos and estimates are collected, the claim investigated and decided, and payment issued.

    Parties: Customer, Claims adjuster, Field operations, Accounts payable. Callvu moves: chase and verify, classify, decide, write back.

  • Third-party damage recovery

    In scopeComplex: multi-party handoffs

    Damage to utility facilities by contractors or drivers is captured once with photos, location and estimates, and the recovery is billed and chased.

    Parties: Field crew, Third party, Insurer, Claims team, Billing. Rules: State one-call (811) damage prevention laws. Callvu moves: prefill, chase and verify, classify, write back.

  • Streetlight and pole issue report

    In scopeSimple

    A resident reports a streetlight out or a damaged pole with location and photo, and a work order is created.

    Parties: Resident, Work management system. Callvu moves: prefill, classify, write back.

  • Gas leak and odor report intake

    In scopeSimple

    A reported gas odor is classified as an emergency, routed to immediate dispatch, and the report and response time recorded.

    Parties: Caller, Gas emergency dispatch. Rules: Federal pipeline safety rules. Callvu moves: classify, write back.

Field appointments and dispatch

  • Field technician dispatch end to end

    In scopeComplex: multi-party handoffs

    A field need is captured with the customer's details and access notes, classified, scheduled with the customer, dispatched with the right parts, and closed with the result written to the work and billing systems.

    Parties: Customer, Contact center agent, Scheduling, Field technician, Work management system, Billing. Rules: State commission service quality rules. Callvu moves: prefill, classify, chase and verify, decide, write back.

  • Field appointment confirmation

    In scopeSimple

    Appointments are confirmed with the customer, with reminders that stop when done and rescheduling on the same link.

    Parties: Customer, Scheduling. Rules: TCPA consent for automated calls and texts. Callvu moves: prefill, chase and verify, write back.

  • Access and safety notices

    In scopeSimple

    Required notices before field work, such as access requests and planned outages, are delivered and recorded.

    Parties: Customer, Field operations. Callvu moves: classify, write back.

  • Missed appointment and no-access follow-up

    In scopeComplex: multi-party handoffs

    When the technician cannot get in, the customer is notified, a new slot is offered, and repeated no-access cases follow the escalation rule.

    Parties: Customer, Field technician, Scheduling, Collections. Rules: State commission tariff rules. Callvu moves: classify, chase and verify, decide, write back.

  • Technician job completion and customer sign-off

    In scopeSimple

    The technician records the work, photos and customer sign-off on site, and the result is written to work management and billing.

    Parties: Field technician, Customer, Work management system, Billing. Callvu moves: prefill, chase and verify, write back.

  • Contractor work order closeout

    In scopeComplex: multi-party handoffs

    An outside contractor submits completion documents, photos and invoices against the work order, which are checked before payment.

    Parties: Contractor, Field supervisor, Accounts payable, Work management system. Callvu moves: chase and verify, decide, write back.

  • Tree trimming access and consent

    In scopeComplex: multi-party handoffs

    Property owners near lines receive notice, grant or refuse access, and the response is recorded before crews are scheduled.

    Parties: Property owner, Vegetation team, Contractor crew. Callvu moves: chase and verify, classify, write back.

Meters

  • Meter access request

    In scopeSimple

    A customer is asked to provide access to an indoor or locked meter, with scheduling and follow-up until access is given.

    Parties: Customer, Meter services. Rules: State commission tariff rules. Callvu moves: chase and verify, write back.

  • Meter exchange and smart meter installation

    In scopeComplex: multi-party handoffs

    The customer is notified, the installation appointment set, the work completed and the new meter written to CIS and billing.

    Parties: Customer, Meter services, Field technician, CIS, Billing. Rules: State commission tariff rules. Callvu moves: prefill, chase and verify, write back.

  • Smart meter opt-out

    In scopeSimple

    A customer opts out of a smart meter, the tariff fees are shown and accepted, and manual reads are scheduled.

    Parties: Customer, Meter services, Billing. Rules: State commission tariff rules. Callvu moves: prefill, decide, write back.

  • Meter accuracy test request

    In scopeComplex: multi-party handoffs

    A customer requests a meter test, it is scheduled and performed, and any rebill from the result is applied by rule.

    Parties: Customer, Meter shop, Field technician, Billing. Rules: State commission tariff rules. Callvu moves: classify, chase and verify, decide, write back.

  • Meter tampering and theft of service case

    In scopeComplex: multi-party handoffs

    A suspected tampering case gathers field evidence, back-bills by rule and issues the required notices.

    Parties: Field investigator, Revenue protection, Billing, Customer. Rules: State commission tariff rules. Callvu moves: chase and verify, classify, decide, write back.

  • Customer self meter read

    In scopeSimple

    A customer submits a read with a photo when the meter cannot be reached, it is checked and used for billing.

    Parties: Customer, Billing. Callvu moves: chase and verify, write back.

New connections and construction

  • New service connection application

    In scopeComplex: multi-party handoffs

    A builder or homeowner applies for new service with site plans and load details, the design is completed, costs agreed and the job scheduled.

    Parties: Applicant, Builder or electrician, Engineering, Field operations, CIS. Rules: State commission tariff rules. Callvu moves: prefill, chase and verify, decide, write back.

  • Service upgrade or load increase

    In scopeComplex: multi-party handoffs

    A request to increase service size is captured with the load letter, reviewed by engineering, and the upgrade scheduled and billed.

    Parties: Customer, Electrician, Engineering, Field operations. Rules: State commission tariff rules. Callvu moves: chase and verify, decide, write back.

  • Temporary construction service

    In scopeComplex: multi-party handoffs

    A contractor requests temporary power for a site, inspection approval is checked and service is set and later removed.

    Parties: Contractor, Municipal inspector, Field operations, CIS. Rules: State commission tariff rules. Callvu moves: chase and verify, decide, write back.

  • Line extension agreement and contribution

    In scopeComplex: multi-party handoffs

    The cost of extending lines is calculated by tariff, the agreement signed and the contribution collected before work starts.

    Parties: Developer, Engineering, Legal, Billing. Rules: State commission tariff rules. Callvu moves: prefill, chase and verify, decide, write back.

  • Easement and right-of-way agreement

    In scopeComplex: multi-party handoffs

    An easement needed for new facilities is drafted, sent for signature, recorded and the status written to the project.

    Parties: Property owner, Land rights team, Legal, County recorder. Callvu moves: chase and verify, decide, write back.

  • Facility relocation request

    In scopeComplex: multi-party handoffs

    A request to move poles, lines or meters is reviewed, priced, agreed and scheduled.

    Parties: Customer or municipality, Engineering, Field operations, Billing. Rules: State commission tariff rules. Callvu moves: classify, chase and verify, decide, write back.

  • Municipal inspection release before energizing

    In scopeSimple

    Service is energized only after the municipal inspection release is received and matched to the job.

    Parties: Electrician, Municipal inspector, Field operations. Callvu moves: chase and verify, decide, write back.

Distributed energy, EV and programs

  • Solar and battery interconnection application

    In scopeComplex: multi-party handoffs

    An installer submits the application, diagrams and approvals, missing items are chased, engineering review decides, and permission to operate is written to billing for net metering.

    Parties: Customer, Installer, Interconnection team, Engineering, Billing. Rules: State commission interconnection rules. Callvu moves: prefill, chase and verify, classify, decide, write back.

  • Net metering enrollment

    In scopeSimple

    After interconnection approval, the customer is enrolled on the net metering rate and the meter and billing are updated.

    Parties: Customer, Billing, Meter services. Rules: State commission tariff rules. Callvu moves: chase and verify, write back.

  • Community solar subscription

    In scopeComplex: multi-party handoffs

    A customer subscribes to a community solar project, the allocation is recorded and credits applied on the bill.

    Parties: Customer, Subscriber organization, Billing. Rules: State community solar program rules. Callvu moves: prefill, chase and verify, write back.

  • EV rate and charger rebate enrollment

    In scopeComplex: multi-party handoffs

    An EV owner applies for the EV rate or a charger rebate with proof of purchase and installation, which is checked and the rate or rebate applied.

    Parties: Customer, Electrician, Program team, Billing. Rules: State commission tariff rules. Callvu moves: chase and verify, decide, write back.

  • Energy efficiency rebate application

    In scopeComplex: multi-party handoffs

    A customer or contractor submits invoices and product details for a rebate, eligibility is checked, and payment is issued or credited.

    Parties: Customer, Contractor, Program team, Accounts payable. Callvu moves: chase and verify, decide, write back.

  • Demand response program enrollment

    In scopeSimple

    A customer enrolls in a demand response or smart thermostat program with consent and device details, and events are tied to the account.

    Parties: Customer, Program team, Device vendor. Rules: TCPA consent for automated calls and texts. Callvu moves: prefill, write back.

  • Rate plan change

    In scopeSimple

    A customer moves to time-of-use or another rate, eligibility is checked against the meter, the effects are shown and the change written to billing.

    Parties: Customer, Billing. Rules: State commission tariff rules. Callvu moves: prefill, decide, write back.

  • Renewable energy option enrollment

    In scopeSimple

    A customer opts into a renewable energy option, accepts its terms and the charge is added to billing.

    Parties: Customer, Billing. Rules: State commission tariff rules. Callvu moves: prefill, write back.

Commercial, landlord and third-party accounts

  • Commercial account opening

    In scopeComplex: multi-party handoffs

    A business opens service with entity documents, guarantor or deposit decided, and the account created with the right rate class.

    Parties: Business owner, Credit team, Commercial services, CIS. Rules: State commission tariff rules; FTC Red Flags Rule identity theft program. Callvu moves: prefill, chase and verify, decide, write back.

  • Landlord continuous service agreement

    In scopeSimple

    A landlord signs an agreement so service moves to their name between tenants, and the units are flagged in CIS.

    Parties: Landlord, CIS. Rules: State commission tariff rules. Callvu moves: prefill, write back.

  • Multi-site and summary billing enrollment

    In scopeComplex: multi-party handoffs

    A business with many sites enrolls in summary billing with each account verified and linked.

    Parties: Business customer, Commercial services, Billing. Callvu moves: prefill, chase and verify, write back.

  • Sales tax exemption certificate

    In scopeSimple

    A business or nonprofit submits a tax exemption certificate, it is checked and applied to billing, with renewals chased.

    Parties: Business customer, Tax team, Billing. Rules: State sales tax exemption rules. Callvu moves: chase and verify, decide, write back.

  • Business rate classification review

    In scopeComplex: multi-party handoffs

    A business asks for a rate review, usage and premise facts are checked, and the right rate class is applied.

    Parties: Business customer, Rate analyst, Billing. Rules: State commission tariff rules. Callvu moves: chase and verify, classify, decide, write back.

  • Retail energy supplier enrollment and switch

    In scopeComplex: multi-party handoffs

    Where customer choice applies, a switch to or from a retail supplier is captured with consent and sent to the supplier and billing.

    Parties: Customer, Retail supplier, Billing. Rules: State customer choice and anti-slamming rules. Callvu moves: prefill, chase and verify, write back.

  • Property manager unit move-in and move-out

    In scopeComplex: multi-party handoffs

    A property manager reports tenant move-ins and move-outs for many units, and each one is processed with the right billing party.

    Parties: Property manager, Tenant, CIS. Rules: State commission tariff rules. Callvu moves: prefill, classify, write back.

Your process is not listed?

Name it. If it starts at a front door and must end in a system of record, Callvu runs it.