Collections and payments

What an ISP should automate before adding support workload

Define payment matching, evidence freshness and exception ownership before automating ISP support. ISPAgents CRM and access foundations remain Guided pilot.

Illustrative investigation checklist

Keep the evidence distinct

Check qualification
Payment
Check observation
Session
Keep visible
Unknown
ReviewPayment recordConfirm scope
ReviewSession timestampCheck freshness
ReviewMissing identityInvestigate
Illustrative checklist, not a live dashboard or customer outcome.
Page type
Blog
Primary search
What an ISP should automate before adding support workload
Updated
2026-10-16

Define a decision before adding an action

If support staff cannot explain why a case needs attention, automating a response can hide the uncertainty. Begin with a bounded decision: which service is affected, which source is current, and who owns the next step?

Use this checklist to plan an evaluation. It is not a list of finished ISPAgents modules.

A support workflow checklist

  1. Match the payment. Identify the authoritative payment and invoice records. Define how partial payments, duplicates and unmatched references are reviewed.
  2. Match the service. Preserve identifiers across the customer and access systems. Put missing identity in an explicit unknown category.
  3. Check the source. Show whether the evidence came from accounting, a device observation or another system. Do not call every source a router health check.
  4. Check freshness. Show the last observation time separately from the time the dashboard loaded. Define how delayed ingestion and clock errors are handled.
  5. Assign the exception. Give the case an owner and a review path when evidence conflicts.
  6. Gate actions. Before any access change, establish authorization, exact adapter support, failure behavior and rollback evidence.
  7. Measure the outcome. Separate a submitted action, a recorded result and a current observation of access. Keep unknown outcomes visible.

Where ISPAgents fits

Basic subscriber records, search and device assignment are repo-backed. Guided pilot: Customer 360, CRM queues, payment foundations and service-policy preview/jobs help evaluate parts of this workflow. They are not a complete support automation or accounting suite. Live router/RADIUS mutation remains gated, and a full acting operator copilot is roadmap scope.

The paid-but-offline implementation example is one bounded example: fresh accounting suppresses a queue row, while unmapped identity remains separately unknown. It does not prove that every payment adapter or support action works.

Review ISP CRM scope and the canonical subscriber/device identity guide. Use the manual access-check worksheet to measure effort without inventing savings.

Next step

Discuss the scope for your network.