One record for each subscriber line, from coverage check to monthly invoice.
Run enquiries, coverage checks, site surveys, installation jobs, routers, plans, fault tickets, outage notices, reseller accounts and recurring invoices in one system. Each subscriber line carries its plan, its equipment serial numbers, its fault history and its balance. Sales, installers, support and accounts all open the same subscriber account, where four separate lists were kept before.
- Plans, node and cabinet names and billing cycles keyed in the way you sell
- Existing subscribers, router serial numbers and unpaid balances carried over
- GullySystem staff edit plans, fault categories and notice text whenever you request it
Subscribers, plans, installation visits, router stock, fault tickets and recurring invoices for an internet provider live together in one place set up by GullySystem. Each line holds its service address, speed tier, equipment serial numbers and payment status. Tickets group under the failed node or cabinet. One notice reaches every affected subscriber.
What goes wrong before the software.
How the work flows through it, step by step.
- 1
Enquiry and coverage
An enquiry arrives from a home or a shop. The address is checked against nodes, cabinets and towers, and the plans that can be served from there are offered. A rooftop radio link is noted where fibre is absent.
- 2
Survey and booking
A survey visit confirms duct access, aerial or trenching route, drop length and a free port. The result is saved on the enquiry. The customer accepts a plan, and an installation slot is booked.
- 3
Installation
The installer receives the job on a phone, fits the drop, configures the router, records attenuation and signal readings and scans the serial numbers. Signing happens on screen. The job closes on site.
- 4
Activation and first invoice
The account is marked active with its start date, the billing cycle begins, and the first invoice or prepaid balance is generated with any joining fee. The authentication server is told, where the link is set up.
- 5
Support and faults
Tickets are raised from calls, messages and the customer portal. Related tickets group under one node, a technician is dispatched, and an outage notice goes to everyone affected. Latency and jitter complaints are tagged apart from outages.
- 6
Renewal and closure
Contracts near their end are listed for renewal. A cancelled line triggers a router pick-up job. The equipment returns to the register, and its serial number is free to issue again.
What is inside.
Every module can be switched on, left out or changed to match how your team already works.
The business modules it is built from.
Each one is also available on its own, or inside a system built for you.
- Lead Management
Each enquiry keeps its source and address, then waits on a coverage match before anyone quotes a speed tier.
- Contact & Account Management
One account holds the service address, plan, contract term and static address, so support never opens three screens for a caller.
- Job Cards
A job card per new connection records drop length, router settings and signal readings, and the installer closes it with a customer signature.
- Technician Scheduling
Survey and installation visits are assigned by area and van, so a missed duct inspection is rebooked from the same board.
- Stock Tracking and Alerts
Routers, ONT units and cable drums are counted in and out by model, with a reorder alert when a model runs low.
- Ticket Management
Tickets from many callers attach to one failed node, so the network desk works one fault instead of two hundred.
- WhatsApp, SMS and Email Notifications
A single outage notice reaches every line on the failed cabinet by SMS, email or messaging app, with the restoration note attached.
- Subscription Billing
Monthly cycles, prepaid balances and plan changes with a start date feed one invoice run, including credits for long outages.
How we would put it in.
Setup, data migration, integrations and anything built on top.
One system, each person sees their part.
For the owner
Read active lines per node, router stock, receivables by age and open faults without calling the network desk. Know which backhaul link carries the most paying lines.
For sales and the front desk
Check coverage, quote a plan, book a survey and see where each enquiry stands. A caller asking about wifi in a new flat gets an answer in one call.
For installers
Open the day’s visits on a phone, scan router serials, record readings and close the job with a customer signature. The route for the day is already set.
For support and the network desk
Raise and group tickets, send outage notices and see a line’s plan, router and last payment while the caller waits. No one asks the caller to repeat the address.
For accounts and resellers
Post receipts, apply credits, chase overdue lines and settle reseller wallets and commission. The month-end sheet is replaced by a statement for each reseller.
The numbers the owner asks for.
- Active, suspended and cancelled lines by node and plan
- Installations completed against jobs booked, by installer
- Router and radio stock by model, with units out at subscribers
- Tickets by node, cause and time open
- Outage credits issued by event
- Receivables by age and by reseller
- Contracts due for renewal in the next month
Who this is built for.
- Local broadband providers selling fibre, wireless or cable plans to homes and shops
- Wireless internet providers serving villages or estates from towers
- Providers that sell prepaid plans through resellers and voucher agents
- Operators who send their own installer vans and stock their own routers
- Providers with several nodes and a support desk that handles faults and billing questions
When it is not the right choice.
- A café that shares its connection with customers does not need subscriber billing or a router register.
- Mobile network operators with core network and roaming billing need a carrier-grade billing platform, which this does not replace.
Adapted to your business before it goes live.
You are not handed a login and left to it. The product is set up around your records, your people and the tools you already use.
Works alongside
- SMS
- WhatsApp or other messaging
- Card and payment gateway
- Authentication server link
- Accounting export
Questions owners ask before a demo.
Does it control internet sessions?
No. Your authentication and bandwidth server keeps running sessions, and this system holds the plan, the status and the payments. A link that pushes suspensions to that server is scoped during implementation.
Can we sell prepaid plans and monthly plans together?
Yes. A line is either billed monthly or drawn from a prepaid balance. Voucher top-ups and expiry dates are recorded against the line, so a prepaid subscriber is never blocked by a late spreadsheet.
How does coverage checking work?
Each node, cabinet or tower carries a list of served areas and its free ports or splitter outputs. An address is matched to those before the sales team quotes. A full cabinet shows as full.
What happens when a whole cabinet fails?
Tickets raised by subscribers on that cabinet are grouped, and one notice goes to every line on it. Closing the group closes each ticket and can apply the agreed credit to every affected line.
Can installers scan serial numbers?
Yes. On the installation job the installer scans or types the router and ONT serials. The register then shows which line holds each unit. A returned unit is checked in against the same serial.
Can resellers log in?
Yes. A reseller sees only its own subscribers, wallet and commission statement. It cannot read another reseller’s lines, and your own staff set which plans it may sell.
How are outage credits worked out?
A rule is set per event, such as hours down on a node. The credit lands on every affected line at the next invoice, not only on those who called. The rule is the same whoever handles the file.
Can our existing subscriber list be loaded?
Yes. Lines, plans, router serials and open balances are imported from your billing sheet. Your accounts team checks the totals before go-live, and rows that do not match come back as a short list.
How is the system priced for our subscriber base, and is there a trial?
Cost depends on the size of your subscriber base and the links needed to your other systems. You first see a trial run loaded with your plan list. A written offer follows.
Who owns the subscriber data?
You do. Subscriber, router and invoice records come out as files, and the quotation names the layout. Leaving needs nobody’s goodwill.
Wondering what it would cost? Share your requirements and an engineer will come back with a scope.
Businesses that use this.
See Internet Service Provider Management Software with your own data.
Tell us how you run things today. We’ll show you the parts that matter to you and say plainly what would need changing.
- No obligation
- A reply within one business day
- Your details stay private
Start with your requirements
Seven short steps that tell us what you need. An engineer reads them before getting in touch.
Share your requirements