Running a hotspot platform is only half the story. Behind every YesSpot deployment there is an ISP business that needs recurring billing, GST invoices, OTT subscriptions, and partner settlements handled cleanly. In this post we share the exact stack and workflows we use to manage our own ISP billing and OTT bundles.
The Two Halves of an ISP Operation
Most operators think of their business as one system, but in practice it splits into two distinct workloads:
- Access & authentication — hotspot login, RADIUS, vouchers, FUP, captive portals. This is what YesSpot does.
- Subscriber lifecycle & money — recurring plans, invoicing, payment collection, OTT entitlements, franchisee/partner settlements, and compliance.
Trying to force one tool to do both usually ends with spreadsheets filling the gaps. We learned this the hard way, so we run the two halves on purpose-built systems that talk to each other over RADIUS and webhooks.
Our Billing Stack
For the subscriber lifecycle side we use NowaCRM. It owns the customer record from lead to renewal:
- 📄 Automated recurring invoices with GST breakup
- 💳 Payment collection via UPI, payment gateways, and cash entries from field agents
- 🔁 Auto-suspend and auto-resume tied to RADIUS, so non-paying users drop off without manual work
- 🤝 Franchisee and LCO settlement reports at the end of every cycle
Because billing drives RADIUS state directly, the hotspot layer never needs to know whether a customer paid by UPI, cash, or wallet — it just sees an active or suspended account.
How We Handle OTT Bundles
OTT is now a retention tool more than an upsell. Subscribers churn less when their broadband plan includes the streaming apps they already pay for separately. Our workflow:
- Define broadband plans with OTT packs attached (e.g., 100 Mbps + 12-app pack)
- On activation or renewal, the OTT entitlement is provisioned automatically against the subscriber's mobile number
- On suspension, the entitlement pauses — no leaking paid OTT to inactive accounts
The entitlement provisioning runs through NowaCRM's OTT integration for broadband plans, so there is no separate OTT panel to reconcile at month-end. One plan, one invoice, one renewal date.
Where YesSpot Fits
YesSpot stays focused on what hotspot operators need: MikroTik integration, voucher sales, OTP logins, and captive portal branding. For pure hotspot businesses — hotels, cafes, public WiFi — YesSpot's built-in voucher billing is all you need.
But if you are a broadband ISP running home connections alongside hotspots, pair YesSpot with a dedicated billing and CRM platform for Indian ISPs and let each system do its job. The combination gives you hotspot monetization and subscriber billing without duct tape between them.
Lessons Learned
- ✅ Keep authentication and billing loosely coupled — RADIUS attributes are the contract between them
- ✅ Automate suspension; manual disconnection lists are where revenue leaks
- ✅ Bundle OTT at the plan level, not as ad-hoc add-ons, or reconciliation becomes a monthly headache
- ✅ Settle partners from system reports, not WhatsApp screenshots
Want to try the hotspot side of this stack? Start a free YesSpot trial — setup takes under a minute.
