Skip to main content
GullySystem
Computers and IT · Software for telecommunications companies

Hold every subscriber plan, installation, device and fault ticket on one account record.

Regional telecom providers sell broadband, fibre, fixed wireless and voice plans to homes and businesses. The telecom product keeps the subscriber, the plan, the line or port, the router and the open faults on one record. Installation crews, support desks and billing read the same account.

At a glance

A regional telecom provider sells connectivity by plan and keeps it running by hand. Each subscriber has a plan, a connection point, a device and a billing cycle. Those four facts usually live in four different tools, kept by four different people, and none of them is the subscriber’s own record.

Software for this trade joins them at the subscriber. A first walkthrough can follow one installation from sign-up to first bill. Your network management and subscriber authentication tools stay where they are.

How the work runs today

Sales staff take sign-ups from homes, shops and offices and check whether the address can be served from a cabinet, a mast or a fibre splitter. The answer often sits in one engineer’s head. A survey visit confirms the route and drop cable length. The subscriber then picks a plan, a static address option or a voice bundle, and a business account signs an agreement naming its restore target and term.

An installation crew fits the drop, the termination box and the router, then records the device serial, the port used, the signal level at the socket and any extra cabling. Billing runs each cycle against the plan, adds any installation fee or add-on, and chases late payers. Support takes calls. Slow speeds, dropped links and billing questions all arrive on the same line.

Faults come by phone and chat. A technician finds a cut cable, a faulty optical unit or a misaligned dish. Enterprise customers expect a restore target in the contract. Outages touch many accounts at once. Each needs a message.

Where it breaks

What goes wrong for telecommunications companies without a proper system.

Plan and billing disagree

The network profile says one speed while the invoice says another. A plan change made at the desk is not always carried to the billing run.

Devices are not traced to subscribers

Routers, optical units and radios are handed out by the box. When a subscriber leaves, nobody can say which serial went back.

Installation survey notes are lost

Drop length, splitter port and mast direction are noted on a pad. The next technician repeating the visit starts the survey again.

One outage creates hundreds of calls

A cut in the feeder cable affects every account behind it, yet support logs each call alone. The same message is typed again and again.

Enterprise service terms are held apart

Restore targets, fixed address blocks and contract end dates sit in a signed PDF. Support cannot see them when a business account reports a fault.

What the software does

What we would build for telecommunications companies.

Named the way your team already talks about the work. We start with whichever part the audit shows is costing you most.

Subscriber accounts and sites

Keep each subscriber with service address, contact, account type and every connection at that address, from a single home link to a multi-site business.

Plans, add-ons and tariff rules

Set data plans, speed tiers, voice bundles and one-off charges once, with the rule for upgrades, downgrades and mid-cycle changes.

Coverage checks and survey visits

Record the serving cabinet, splitter or mast for each address, and keep survey results such as drop length and signal readings.

Installation and activation jobs

Schedule crews, capture the port, device serial and activation date, and close the job only when the line is confirmed live.

Device and equipment stock

Track routers, optical units, radios and SIM cards by serial from the warehouse to the subscriber and back on return.

Fault tickets and outage notices

Log each fault against the account, link many tickets to one network incident, and send the same restore message to every affected subscriber.

Recurring billing and collections

Raise invoices each cycle from plan and add-ons, take payments by card, bank debit or cash at agent counters, and follow overdue accounts.

Before you talk to a supplier

A requirements checklist for telecommunications companies.

What to cover, which reports to ask for and what to put to every vendor, ready to print or save as a PDF.

Open the checklist
Ready product

A product already built for telecommunications companies.

It is adapted to how your business works before it goes live, and anything your trade needs that it lacks is added then.

Telecom Service Provider Management Software

Subscriber accounts, plans, installation jobs, device stock, fault tickets, outage notices and recurring billing for regional telecom and broadband providers.

See the product
Solutions inside

The business modules telecommunications companies use most.

Each one is also available on its own, or inside a system built for you.

How it works

How the work runs from Bengaluru for your city.

  1. 1

    The audit, by call

    A screen-share and a look at the sheets, accounting reports and WhatsApp groups your team uses. No travel needed.

  2. 2

    A written proposal

    Scope, what we build first and the cost, agreed in writing before anything starts.

  3. 3

    Build in short rounds

    Working screens shared every few weeks. Your team tests them from your own office.

  4. 4

    Go-live, in person when it helps

    For data migration and training we can come to your city. Travel is agreed in advance.

  5. 5

    Support online

    Fixes, changes and hosting handled remotely by the same team that built it.

Common questions

Questions telecommunications companies ask before they call.

Does the software control the network itself?

No. It does not configure routers or manage subscriber logins on the network. It holds the subscriber, plan, device and ticket records, and a link to your network tools is scoped during implementation.

Is this for a small broadband provider?

Yes. A local fibre or wireless provider with a few thousand subscribers is the usual fit. Large carriers with their own billing platforms are a different case.

Can it handle monthly plans and usage-based charges?

Plans bill on a cycle with add-ons and one-off fees. Usage-based charges need a usage file from your network, and that feed is agreed with you at the start.

Can agents collect payments in cash at a counter?

Yes. A payment taken at an agent counter is posted against the subscriber and shown on the next statement. Agent commission rules are set with you.

What happens after I share my requirements?

An engineer reads what you send and replies within one business day. We then look at the software, spreadsheets and WhatsApp groups your business runs on today and write down what works, what slows your team down and what is missing. A demo login, a screen-share or a few screenshots are enough. You get a short written summary ordered by priority, with no obligation to hire us afterwards.

How much will the software cost?

We don’t publish a price, because it depends on what the system has to do. That first review settles the scope, and the cost goes into a written proposal before any work starts.

Category

Part of these wider groups.

Talk to us

Tell us how your business runs today.

A few lines on your spreadsheets, software and WhatsApp groups is enough. We reply the same working day.

  • 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