Before
- Monthly bills generated in Excel with package mismatches
- OLT/PON inventory tracked separately from subscriber records
- Recovery officers used paper lists and WhatsApp screenshots
Before & after AsanBilling
After
- Connections linked to packages, areas, and infrastructure nodes
- Month-wise billing with printable receipts and CSV exports
- Allocated recovery views plus WhatsApp bill reminder templates
Results
- Billing desk closed month-end faster with fewer package disputes
- Field recovery worked from assigned bill lists instead of ad-hoc chats
- Management reviewed collection KPIs on the AsanBilling dashboard
The problem
Fiber growth outpaced the billing spreadsheet. Package upgrades, inactive connections, and splitter/box moves were not reflected in the same file collectors used on the road.
Complaints about wrong bills and missed renewals piled up while NOC and billing teams kept separate notes.
Implementation
Areas and packages were imported first, then live connections. OLT/PON and customer-box records were linked where the network team already had identifiers. Staff roles separated billing desk, recovery, and complaint handling.
WhatsApp templates with merge fields went live after core billing stabilized — so reminders pointed at verified amounts.
Outcome
The operator kept a single source of truth for subscribers and infrastructure. Explore FTTH billing software and ISP billing software pricing if you are planning a similar migration.
FAQ
Can we import Excel subscribers like this FTTH team?
Yes. Legacy import is planned during onboarding — tell us your columns and connection count on the demo form.
Is OLT/PON required on every plan?
Infrastructure mapping is available on higher tiers. Starter covers core billing; Enterprise includes OLT/PON and recovery modules.
دراسات حالة ذات صلة
اربط هذا المسار بمزود الإنترنت لديك
أخبرنا بمدينتك وعدد الاشتراكات ونوع الشبكة — سنعرض نفس الوحدات.
عرض مجاني موجه · بدون رسوم للحديث · الرد عادة خلال يوم عمل · أو WhatsApp +92 315 2433074