VoIP Software: Complete Traffic Management
Voice traffic pulled out by hand into an Excel sheet, with customers going from 400 to 2,000.
Telco and digital services
A telecoms operator went from 400 to about 2,000 customers, and voice traffic was still pulled out by hand into an Excel sheet. It is one of three projects we have done for companies that sell pay-as-you-go or subscription services, with those for a virtual server provider and for an e-invoicing service.
Voice traffic pulled out by hand into an Excel sheet, with customers going from 400 to 2,000.
Every renewal, every new instance and every cancellation went through a person.
No customer of the service could see the state of their own invoices, so every question became a support ticket.
What software does a telco operator or a subscription service need?
Software that handles on its own what today goes through a person. For a telco it collects the traffic of up to five providers and calculates its cost; for a VPS provider it handles renewals, cancellations and expiry notices; with an e-invoicing panel customers see the state of their own invoices without opening a ticket.
For a telecoms operator, software that collects call feeds directly from the VoIP providers, up to five where before one came in, and calculates their monthly cost on the customer’s price list. The price list can be corrected backwards too, and the prices already applied are checked again. The software handles top-ups, flags customers below the traffic threshold, spam calls and numbers missing from the customer records, and prepares reports on usage and revenue. With about 2,000 customers, the operator reached peaks of more than 500,000 calls a month, with an average length of 90 seconds.
It is written in PHP with Symfony, Redis, MySQL, RabbitMQ, Angular and Bash, and for security and privacy reasons it is installed in a private space of the customer’s. Four months, with a PM, a backend developer and a frontend developer.
For a provider of virtual servers and data centres, VPS and VDC, several pieces that work together: the public site, the shop, the buyer’s control panel and a system that integrates the management software already in use. Whoever signs up buys their VPS and from there manages it on their own, subscription included. The system creates, updates, renews and removes instances, handles provisioning and sends expiry notices and payment reminders; the integration system keeps the data aligned across Navision, Plesk and Lenovo ThinkAgile. Twelve months, with two backend developers and one frontend developer.
For a service that offers APIs for e-invoicing, a panel in React connected to those APIs. Its customers see their outgoing and incoming invoices and their subscriptions there, and each of them finds only the functions their role allows. Three months, with two people.
The providers the traffic comes from, the price lists, the customer records, invoicing: in this sector the new software sits among systems that are already there. For the virtual server provider they were the Navision management system, the Plesk panel and the Lenovo ThinkAgile infrastructure; for the e-invoicing service its own APIs, which in turn talk to the Italian Revenue Agency.
Before choosing who will write the software, it is worth asking:
After a first call, free of charge, we come to your site to see which operations still go through a person and which systems the new software has to talk to.
The scope is split into phases with a date each, and we start from the step that weighs the most.
Tell us about the project you have in mind.