Before
- Dealers remitted cash with handwritten slips
- Recovery officers overlapped routes and double-collected
- Bad debt was only visible after month-end reconciliation
Before & after AsanBilling
After
- Dealer and allocated collections entered against connections
- Recovery officers saw assigned bills by area
- Bad-debt and collection reports exported for owners
Results
- Fewer disputes over who collected which bill
- Owners saw area-wise collection progress during the month
- Staff onboarded using the online user manual and a short demo
The problem
Tower and sector growth meant more dealers and more cash on the road. Spreadsheets could not stop route overlap or show which connections were still unpaid mid-month.
Implementation
Area trees matched how the WISP already divided towns. Packages and connections went live first; dealer collection types and recovery officer permissions followed. WhatsApp reminders were added for overdue bills after collectors trusted the data.
Outcome
Collections became auditable. See ISP collection management and recovery officer software for the same modules, or request a demo with your town list and connection count.
FAQ
Do dealers need separate logins?
Permissions are role-based. Many teams keep dealer remittance entry with office staff while recovery officers use allocated views in the field.
What package do multi-city WISPs usually need?
Professional suits mid-size networks; Enterprise adds recovery officers, complaints, WhatsApp, and advanced reports. Pricing starts from Rs. 3,500/month.
Related case studies
Map this workflow to your ISP
Tell us your city, connection count, and whether you run FTTH, WISP, or cable — we will walk through the same modules.
Free guided demo · No setup fee to talk · Reply usually within one business day · Or WhatsApp +92 315 2433074