01
Customer, service, invoice
context before every contact
Collections and reconciliation for ISPs
Automate ISP collections without replacing your current system
Connect customers, services, invoices, and payments; coordinate reminders across WhatsApp, SMS, email, and calls; and keep every promise and exception visible to your team.
Your BSS keeps billing and your gateway keeps processing. Certeza adds collections and reconciliation without managing the network, holding funds, or triggering suspension or reconnection in phase one.
- recurring receivables cycle
- Monthly
- coordinated channels
- 4+
- of your ISP system
- No migration
Certeza key points
02
Confirmed payment
stops follow-up immediately
03
Promises and responses
shared history for collections
04
Isolated exceptions
disputes and ambiguous payments reviewed
ISP receivables operations
Your system bills; Certeza organizes follow-up and payment matching
The focus is reducing manual work and incorrect outreach, not becoming another network and billing suite.
01
01
Collections before and after due date
Run preventive reminders and overdue sequences based on invoice, balance, zone, response, and rules approved by the operator.
02
02
Paid customers leave the workflow
A reliable payment confirmation stops outreach. Synchronization and exceptions are monitored to avoid collecting from customers who already paid.
03
03
Confidence-based reconciliation
Match transaction reference, invoice, service, amount, and date. Uncertain matches and incomplete receipts remain for human review.
04
04
Promises and multichannel follow-up
WhatsApp, SMS, email, calls, and internal tasks form a traceable sequence with promised dates, responses, and next steps.
05
05
The BSS keeps technical control
Certeza does not replace billing, contracts, tickets, MikroTik, OLT, or ONU management. The ISP system governs invoice, service, suspension, and reconnection.
06
06
Minimal data, roles, and auditability
Only fields needed for collections are imported, technical credentials are excluded, and rules, access, contacts, payments, and decisions remain auditable.
How it works
From open invoices to applied payments or clear exceptions
The pilot starts in read mode with a controlled segment. No network automation belongs in phase one.
- 01
Connect receivables by file or assessed API
Use only the customers, services, contacts, invoices, due dates, balances, references, payments, and dispute status required by the workflow.
- 02
Test real cases and boundaries
Validate customers with multiple services, open invoices, partial payments, credits, duplicate references, disputes, and unmatched receipts.
- 03
Approve segments, channels, and messages
The ISP defines rules by aging, balance, zone, and status, plus timing, frequency, exclusions, and moments for human intervention.
- 04
Certeza runs the follow-up
The platform coordinates reminders, records responses and promises, and stops collections when it receives reliable payment confirmation.
- 05
Apply reliable payments and review exceptions
Payments with sufficient references follow the agreed process; ambiguous, disputed, or inconsistent items remain visible for the team's decision.
Integration without empty promises
Start with exports; connect an API only after validating it
WispHub, Wispro, or another system can be assessed according to its API, subscription, and permissions. We do not publish logos or claim a native integration before completing a real test.
1Excel and CSV for the pilot
2BSS or billing system
3Bank, gateway, and receipts
4WhatsApp, SMS, email, and calls
Operational outcome
Less time between payment, identification, and receivables update
The pilot measures manual work, unapplied payments, promises, contacts correctly stopped after payment, and exceptions; it does not promise reconnection or recovery rates without evidence.
Your team handles exceptions; Certeza sustains repetitive follow-up.
- Invoices prioritized by aging, balance, and response.
- Collections stop when payment is confirmed.
- Ambiguous, duplicate, or disputed payments are isolated for review.
- Contact, promise, and decision history by customer and invoice.
Questions from operators
What must be clear before connecting an ISP
Collections and reconciliation on top of the existing operation, without touching the network or replacing billing.
Regional ISPs
01Does Certeza replace my ISP software?
No. Certeza is not a BSS, ERP, or network management platform. Your system continues to manage customers, contracts, billing, tickets, equipment, suspension, and reconnection. Certeza receives the minimum receivables data, runs follow-up under approved rules, and returns payments or exceptions so the primary source can remain current under the agreed scope.
02Does it work with WispHub, Wispro, or another system?
A pilot can begin with an Excel or CSV export to validate the workflow without an expensive integration. WispHub and Wispro provide APIs that can be assessed, but connectivity depends on each operator's subscription, permissions, fields, and tests. Certeza does not ingest PPPoE, CPE, router, or network configuration credentials; an integration starts read-only and uses a strict data allowlist.
03Is Certeza a payment gateway or does it receive money?
No. The ISP's contracted gateway or financial institution processes the funds. Certeza can facilitate the existing payment link and match available information to the customer, service, and invoice. It does not hold or disburse funds. If a reference, amount, or date cannot support a reliable match, the case remains in review and is not marked paid automatically.
04Does Certeza suspend or reconnect customers?
Not in phase one. The BSS and the operator retain technical and regulatory control of the service. Certeza can stop contact once payment is confirmed and make the outcome visible to the system or team, but it does not promise immediate suspension or reconnection and does not directly use MikroTik, OLT, ONU, or service activation endpoints.
05How are missing references, duplicates, or disputes handled?
The workflow first looks for an exact transaction reference or invoice. Customer or service, amount, and a time window can then be assessed. Everything else goes to human review. Disputed invoices or amounts are excluded from collections according to the information supplied by the operator. A confirmed payment must stop follow-up to avoid contacting a customer who already paid.
06How does an ISP pilot start?
We review subscriber count, current system, gateway, payment sources, invoice volume, channels, and the main friction. A sample is tested in read mode, rules and messages are agreed, and a controlled segment is selected. Applied payments, exceptions, manual hours, promises, and correct stops are measured before expanding or authorizing writes to the system.
Assessment for ISPs
Let's find where time is lost between invoice, collection, and payment
Tell us your subscriber count, current system, and payment sources. We can assess a pilot without requesting network credentials or technical data.