Subscriber and service
context before outreach

Certeza organizes subscriber, service, invoice, and payment; coordinates authorized reminders; and separates claims, disputes, and ambiguous receipts for review.
Your commercial system keeps billing, tariffs, claims, and service status. Your bank or gateway processes funds. Certeza does not read meters, file regulatory reports, or order service cuts or reconnections.
context before outreach
clearly identified balance
stops follow-up
cases outside automation
Public-utility receivables
Certeza works on top of the existing system and focuses on collections, promises, payments, and exceptions.
Relate account, service, invoice, period, charge, due date, and balance so every contact refers to the right obligation.
Configure reminders before and after due date based on aging, balance, response, area, and rules approved by the provider.
Reliable confirmation stops follow-up. Incomplete references, duplicates, and reversals remain in review before receivables are updated.
Invoices or amounts under complaint are excluded according to commercial-system status and never trigger suspension decisions.
WhatsApp, SMS, email, calls, and internal tasks follow channels, timing, frequency, tone, and exclusions approved by the provider.
Each contact, response, promise, payment, exception, and decision keeps context for operational review.
How it works
The pilot starts read-only and does not automate service cuts, suspension, reconnection, or tariff changes.
Start with Excel, CSV, or an assessed API containing account, service, invoice, period, due date, balance, reference, payment, and claim status.
Validate partial payments, duplicate references, reversals, incomplete receipts, disputed invoices, and accounts with multiple services.
The provider defines segments, authorized channels, timing, frequency, tone, exclusions, and moments requiring human intervention.
The platform runs reminders, records responses and promises, and stops the flow after payment, a claim, or an authorized instruction.
Payments with sufficient references follow the agreed process; ambiguous cases remain visible before any primary-system write.
On top of your commercial system
We do not display logos or promise native connectivity before testing APIs, permissions, fields, claim states, and error handling.
Operational outcome
We measure unapplied payments, promises, correct stops, and exceptions; we do not promise recovery, compliance, or automatic reconnection.
The commercial system governs service; Certeza sustains follow-up.

Questions from utility providers
Collections and reconciliation on top of the existing operation, without replacing billing, claims, or technical control.
No. The current system keeps subscribers, contracts, readings, tariffs, billing, complaints, and service status. Certeza receives minimal receivables data and returns contacts, promises, payments, or exceptions.
No. Certeza does not read meters, calculate consumption, generate official billing, manage subsidies, or produce regulatory filings. Its scope is collection follow-up, reconciliation, and exceptions.
No. The provider's bank or gateway processes funds. Certeza can expose the existing payment link and match references to accounts and invoices; uncertain matches stay in review.
The disputed invoice or amount leaves the flow according to commercial-system status. Certeza does not resolve the claim or decide suspension and resumes only after an authorized update.
Not in the initial scope. Technical and regulatory decisions remain with the provider and its system. Certeza can expose a confirmed payment but does not promise immediate suspension or reconnection.
We review subscribers, billing cycle, commercial system, bank or gateway, unapplied-payment volume, and complaints. We test a read-only sample, agree on rules, and measure before expanding.
Assessment for public utilities
Tell us your subscriber count, commercial system, and payment sources. Do not submit subscriber information in this form.