Collect
- Call, data and messaging records from network elements
- Charging data records in 3GPP formats
- Events from CPaaS and partner networks
Telecommunications
Telecom software development: BSS, OSS and CPaaS
In telecom, a lost usage record is lost revenue and a careless support screen is a regulatory problem. Agnotic Technologies builds billing, provisioning and messaging software for carriers, MVNOs and platform resellers, with record reconciliation and FCC rules designed in.
Rating and billingOrder to activationCPNI controlsSTIR/SHAKEN
Trusted by global innovators
Telecom software
What telecom software does Agnotic build?
Telecom software development is building the business and operations systems that carriers, MVNOs and communications platform resellers run on. Agnotic Technologies builds usage rating and billing (BSS), order to activation and number porting (OSS), and messaging and voice products that follow FCC rules on CPNI, caller ID authentication and consent.
We build software, not networks. Radio access, spectrum and network hardware are outside our work; we integrate with the network elements and platforms you already run.
Telecom analytics, such as revenue assurance and churn, uses the same records, so it is covered on this page rather than a separate one.
BSS data path
How does a usage record become an invoice?
Every stage is a place where records can be lost or priced wrong, so each one is counted.
Mediate
- Decode, validate and deduplicate records
- Correlate partial records for long sessions
- A reject and repair queue for bad records
Rate
- Price plans, bundles and allowances
- Real-time balance checks for prepaid
- Roaming and interconnect rates
Bill
- Invoice runs and taxes
- Payments and collections
- Disputes and adjustments
Assure
- Record counts reconciled at each step
- Leakage reports
- An audit trail per account
Which telecom systems do we build?
Rating and billing (BSS)
Mediation, rating, invoicing and payments for postpaid, prepaid and wholesale accounts, with plans set up by product teams rather than code changes.
Order to activation (OSS)
Order capture, provisioning workflows and service inventory, with each step's state visible to care teams.
Number porting
Port-in and port-out workflows with status tracking, an exceptions queue and customer notifications.
Care tools with CPNI controls
Agent screens that authenticate the customer before showing account data, and log who viewed what.
Messaging products
A2P messaging with carrier registration, consent records and opt-out handling for every number.
Voice products
Call signing and verification through STIR/SHAKEN, and monitoring of how outbound calls are labelled.
Failure points
Where does telecom software fail?
Challenge
Usage records are lost between mediation and rating, and nobody notices until an audit.
Agnotic approach
Record counts reconciled at every hop, with alerts when the counts diverge.
Challenge
Porting orders stall between carriers with no owner.
Agnotic approach
Every port has a state, a due date and an exceptions queue that care teams work daily.
Challenge
A support tool shows call detail to anyone who knows a customer's address.
Agnotic approach
Authentication before any CPNI is shown, and call detail on inbound calls only after a password.
Challenge
A2P messages are blocked because a brand or campaign was never registered.
Agnotic approach
Registration status checked before sending, with consent and opt-out stored against each number.
Challenge
Outbound calls are labelled as spam.
Agnotic approach
Calls signed through STIR/SHAKEN at the right attestation level, plus monitoring of call labelling.
Revenue assurance
Where does revenue leak between the network and the bank?
The reconciliation we build into telecom analytics, from network usage to collected cash.
| Control point | Record compared | Leakage it catches |
|---|---|---|
| Network element usage | Records generated against records received by mediation | Usage lost in transfer or dropped by a failed collector |
| Mediation output | Records in against records out, with rejects counted | Valid records stuck in a reject queue and never rated |
| Rated events | Rated usage against the customer's plan and allowance | A wrong tariff, a missing bundle or a new service never rated |
| Invoiced charges | Rated totals against invoice lines per account | Charges rated but never billed, or billed twice |
| Collected revenue | Invoiced amounts against payments received | Unapplied payments and write-offs without approval |
Regulation
Which FCC rules shape telecom software?
Your regulatory counsel confirms which rules apply to your licences and services. We build the controls.
- CPNI rules in 47 CFR Part 64 Subpart U: customer authentication before disclosure, passwords for call detail by phone and safeguards on who can see CPNI
- Breach notice under 47 CFR 64.2011: law enforcement first, customers only after the waiting period
- Caller ID authentication under 47 CFR 64.6301: STIR/SHAKEN in IP voice networks
- Consent and opt-out for calls and texts under the TCPA rules in 47 CFR 64.1200
- Audit logs that show who accessed CPNI and when
Telecommunications analytics
Which telecom analytics do we build?
Revenue assurance
- Reconciliation at each control point
- Leakage dashboards by product
- Case tracking for each fix
Churn
- Signals from usage, care contacts and billing events
- Retention offers tested against control groups
- CPNI approval rules applied to marketing use
Network experience
- Counters and probe data joined to customers
- Quality complaints mapped to sites
- Trends for planning teams
Who do we build telecom software for?
MVNOs and MVNEs
Rating, billing and activation on top of a host network's services.
Regional carriers and fiber providers
Order to activation, billing and care tools that replace ageing systems.
CPaaS and messaging resellers
A2P messaging platforms with registration, consent and usage billing.
UCaaS and VoIP providers
Voice products with STIR/SHAKEN signing and number porting.
IoT connectivity providers
Usage rating and activation for large fleets of SIMs and devices.
References
Telecom rules and standards we build against
47 CFR 64 Subpart U47 CFR 64.630147 CFR 64.12003GPP TS 32.298TM Forum Open APIsIETF RFC 8224
Facts and sources
Facts behind telecom software
FCC rules read on eCFR and the 3GPP specification for charging records.
Telecommunications carriers must authenticate a customer before disclosing CPNI on a customer-initiated call, online account access or in-store visit, and may disclose call detail over the phone only after the customer gives a password.
Source: 47 CFR 64.2010(a) and (b) (eCFR)After a CPNI breach, a carrier must electronically notify the US Secret Service and the FBI as soon as practicable and no later than seven business days after reasonably determining the breach, before telling customers or the public.
Source: 47 CFR 64.2011 (eCFR)Unless an exception applies, a voice service provider must fully implement the STIR/SHAKEN caller ID authentication framework in its internet Protocol networks, a requirement dated June 30, 2021.
Source: 47 CFR 64.6301(a) (eCFR)3GPP TS 32.298 is the technical specification that describes Charging Data Record (CDR) parameters for telecommunication charging management.
Source: 3GPP TS 32.298
Scope and cost
What drives the cost of telecom software?
We do not publish prices. These factors decide the size of the build.
Services you sell
Voice, data, messaging, wholesale or a mix, each with its own rating rules.
Record volume
How many usage records arrive per day and how fast they must be rated.
Network and partner interfaces
Each network element, host network or partner adds an interface to build and test.
Regulatory scope
CPNI, porting, STIR/SHAKEN and consent controls the product must carry.
Legacy BSS migration
Moving accounts, balances and history from an old billing system.
Real-time needs
Prepaid balance checks and real-time charging need more engineering than batch rating.
Frequently Asked Questions
It depends on the services you sell, record volumes, the interfaces to your network and partners, and whether a legacy billing system must be migrated. We agree a first release on the scoping call.
Yes. We use TM Forum Open APIs where your systems support them, and file or API interfaces where they do not, with record counts reconciled across every interface.
No. Radio access, spectrum and network hardware are outside our work. We build the business, operations and product software that runs on top of your network.
Customer authentication before any disclosure, role-based access for staff, audit logs of every view, and a breach workflow that notifies law enforcement before customers, as 47 CFR 64.2011 requires.
Yes. We migrate accounts, balances and history, then run old and new billing in parallel and reconcile invoices before switching over.
Yes. Revenue assurance, churn and network experience analytics use the same records as billing, with CPNI access rules applied in the data layer.
AI tools may help write record decoders and test data, but every rating change is tested against a regression set of real-format records with known expected charges before release.