The network is the licence. Service is the margin.
Operators sell a service that must never stop, at a volume where the cost of every call, every bill and every provisioning order is multiplied across the whole subscriber base, under a licence the national telecom regulator can revisit. The systems that carry that service were built in layers over decades, and the rivals now arrive from outside the industry. Altuon builds the service lines, the cores, the intelligence and the brands for an operator whose margin is decided in the cost base and whose licence is decided in the record.
What is at stake
The obligations come from two directions. The national telecom regulator — ComCom and OFCOM in Switzerland, the Telecommunications Regulatory Commission in Jordan, the Federal Communications Commission in the United States — decides who may operate, on which spectrum, under which universal-service, interconnection, number-portability and lawful-intercept conditions, and what must be reported when the network fails. The data regulator decides what may be done with what the network knows. An operator holds location, traffic, billing and identity data on a large part of the adult population of its market, and the revised Swiss Federal Act on Data Protection, the GDPR, Jordan's Personal Data Protection Law and the US state privacy laws each attach duties to that holding: a lawful basis and a stated purpose for every use, retention limits, the subscriber's rights of access and objection, and in several regimes a separate consent for marketing. Telecommunications secrecy sits above all of it. A vendor who treats subscriber data as a marketing asset before it is a regulated one will not survive the operator's own privacy review.
The estate is old and it is load-bearing. Billing, mediation, charging, provisioning, the customer-record system and the order-management layer were built in generations, each around the one before, and every consumer of those systems is a revenue path: an order that does not provision is a customer who is not billed; a rating rule that is wrong is either revenue that leaks or a complaint that is justified. Replacement cannot take the service down for a cut-over weekend, because the network does not have one. The compatibility layer, the reconciliation between old and new, the dual-running and the rehearsed rollback are not caution. They are the only form a migration can take when the system under change is also the one collecting the money.
The buyer is an operating committee, not a person. The chief technology officer wants an estate the organisation can still run in ten years with fewer people than it has now. The chief financial officer wants the cost to serve to fall and can name the figure that matters: the fully loaded cost of a resolved contact. The chief commercial officer wants acquisition measured in activated lines that stay, not in impressions, and wants the consumer, wholesale and enterprise brands to stop competing with one another. The regulatory affairs director wants every automated interaction to be one the regulator could listen to without concern. The data protection officer wants the purpose register before the campaign. A proposal that speaks to one of them is a proposal the others will stop.
Failure is at scale and it is visible. A voice agent that cancels a service or changes a tariff it should not have does so on every call with the same defect. A billing rule that is wrong is wrong for every subscriber on that plan by the next cycle. A campaign that uses a data field without the purpose that covers it is a complaint to the data regulator within days. Network incidents carry their own reporting obligations and their own deadlines. The work is designed so that when something goes wrong the result is a handover to a person, a blocked release, a rollback or a report filed on time — never a subscriber base finding out first.
Practices that apply
- Voice agentsCoreAccount, billing and technical-support lines at the volume where a single point of containment is a line in the annual budget. The agent verifies the caller to the level the request requires, explains a bill from the actual invoice, diagnoses a line from the actual diagnostic, resolves within a written policy of what it may change and what it may not, and hands over to a person with the whole context of the call — in Swiss German, French, Italian, Arabic and English.
- Software engineeringCoreBilling, mediation, provisioning and customer-record cores replaced one consumer at a time behind a compatibility layer, with reconciliation between old and new running from the first day, a cut-over that is a configuration change rather than an outage, and a rollback rehearsed against production-shaped data before any revenue path depends on the new system.
- Technology consultingCoreOperating-model and platform decisions for an operator whose systems estate has outgrown the organisation that runs it: which layers to consolidate, which to retire, what the target estate costs to run, in what order the transition states are reached, and the case the board approved kept as the instrument by which the programme is governed.
- Market intelligenceCoreSpectrum, licensing and adjacent-entrant intelligence at board cadence: what the regulator is consulting on, which auction or renewal is approaching, which rival is a hyperscaler, a satellite constellation, a device manufacturer or a bank rather than another operator, and what each has done in the last quarter — sourced to the line, so the decision can be shown to have been informed.
- Advertising and growthCoreAcquisition and retention programmes where first-party data is the asset and its use is regulated: consent and purpose designed before the first campaign, audiences built by rule from what the operator may lawfully use, incrementality measured against a holdout rather than asserted, and results expressed in activated lines that are still connected a year on.
- Artificial intelligenceSupportingNetwork incident summarisation and customer-record automation, deployed inside the operator's own data plane. An incident summary written by a model from alarms, tickets and engineer notes is a report the operations centre can act on and the regulator can read. A record-automation model with an owner, an evaluation set and a rollback path is one whose accuracy can be shown to have moved the cost base rather than claimed to have.
- Brand and identitySupportingConsumer, wholesale and enterprise sub-brands from one operator, kept distinct by rule without maintaining three identities: a system that decides which elements are shared, which are proper to each brand, how the network brand appears behind each of them, and what happens to all three when the group acquires, is acquired or renames.
Regional notes
- Europe and DACH
- Swiss operators work under ComCom and OFCOM on one side and the revised Federal Act on Data Protection and the secrecy provisions of the Telecommunications Act on the other, serving a base that expects to be addressed in German, French and Italian and speaks Swiss German on the phone. The data plane stays in Switzerland unless there is a written reason for it not to; the sub-processor list is short and read; the exit terms are negotiated before the price. For German and Austrian operators the GDPR, the national telecommunications acts and the practice of the national regulator shape the same decisions, and longevity is the quality being bought.
- Middle East and North Africa
- Operators in Jordan and the Gulf are licensed by regulators — Jordan's Telecommunications Regulatory Commission among them — who take sovereignty seriously, and they serve subscribers who speak Arabic dialects most models were never trained on. Data is held in-country; voice agents are built for Jordanian, Levantine and Gulf Arabic as well as English; and the operator's leadership expects a partner in the room rather than on a call. Jordan's Personal Data Protection Law adds a consent and purpose regime to subscriber data that the commercial function has to be designed around, not reminded of afterwards.
- North America
- US operators move quickly under the FCC's rules on customer proprietary network information, outage reporting and robocall mitigation, and under state privacy laws that decide how subscriber data may be used in service and in marketing and differ from one state to the next. Velocity is bought with evidence: the consent record behind each audience, the policy behind each automated resolution, the change log behind each release. The work has to scale to a national subscriber base and leave a documentary trail that scales with it.
Service regions
Europe and DACH
Registered office
Turin, Italy
Representative engagement
- VoiceSeptember 9, 2026Voice agents in Arabic dialects, and where they breakModern Standard Arabic is a written language. Callers speak Levantine, Gulf, Egyptian and Maghrebi, switch to English mid-sentence and read numbers in two directions. Here is where the systems fail, and what a bank or a ministry should demand before it lets one answer the phone.
- EngineeringSeptember 9, 2026Migrating legacy core systems without stopping the businessThe big-bang cut-over is how core migrations fail. The alternative is slower, less dramatic and works: a compatibility layer, one consumer at a time, and a rollback path that is rehearsed rather than hoped for.
Questions we are asked
Can subscriber data and the models that use it stay in our country, or in our own data centres?
Yes. The data plane is decided per system in the Define phase and recorded in the architecture register: a Swiss region, the European Union, Jordan, the United States, the operator's own premises or a national cloud. Speech, language and record-automation models run inside that plane; the control plane holds policy, identity and metrics but never call content, traffic data or subscriber records. Where telecommunications secrecy or a licence condition requires it, the whole deployment sits on the operator's own infrastructure, and the proposal states what the operator provides — hardware, network, identity — and which model options fit that footprint, so residency is costed rather than assumed.
How is a voice agent kept from changing a tariff, cancelling a service or disclosing account detail it should not?
Policy is enforced outside the language model. The model proposes; a policy engine decides what may be executed, at which verification level and within which limits; and anything not on the permitted list is a handover, not an attempt. The permitted actions — a plan explanation, a payment arrangement, a SIM replacement, a line diagnostic, a tariff change with the right consent — are written with the operator's regulatory and commercial functions and versioned like code. Verification is stepped: a balance enquiry needs less than a cancellation. Adversarial testing for social engineering and prompt injection over voice, including attempts to take over a number, is part of every release gate, and the caller can reach a person from every step with the whole context of the call.
How do you replace a billing or provisioning core without a service interruption?
One consumer at a time, behind a compatibility layer that presents the old interface while the new system is built beneath it. Reconciliation between old and new runs from the first day, so every rated event, every provisioned order and every invoice can be shown to agree before any consumer is moved. Cut-over is a routing change, made for one consumer and reversible within minutes, and the rollback is rehearsed against production-shaped data before it is ever needed. Dual-running continues until the reconciliation is clean for a period the operator's finance function has agreed, and the retirement of the old system is a decision with evidence behind it, not a date on a plan.
How can we use our first-party data in marketing without breaching the FADP, the GDPR, Jordan's PDPL or US state privacy laws?
By designing the consent and the purpose before the campaign. The Discover phase produces a purpose register that maps each data field the commercial function wants to use — location, usage, billing history, device, contact channel — to the lawful basis and the consent that covers it in each market, and to the uses that are excluded. Audiences are then built by rule from that register, so a segment cannot include a field the operator may not use for that purpose. Traffic and location data carry the strictest treatment under telecommunications secrecy and are never used for marketing without the specific consent each regime requires. Every claim in a campaign is traceable to its approver, and the consent record behind every audience is retained in the form a data regulator would ask to see.
Who owns what we build together, and what happens if we end the relationship?
The operator owns the deliverables: the code, the policy definitions, the evaluation sets, the model configurations, the brand system and the documentation, with intellectual property assigned on payment. Altuon retains its pre-existing tooling and methods and licenses them for the operator's continued use. Exit is designed in the Define phase, not negotiated at the end: the agreement carries the notice period, the handover plan, the export format of every data store and the assisted transition to an in-house team or a successor. Key-person risk is answered with named cover for each role and with documentation kept current enough that the cover can act on it.
Who are your sub-processors, and how does our regulator get access if it asks?
The proposal lists every third party that could touch subscriber data — hosting, carrier and telephony providers, speech and language model providers, observability tooling — by name, role and location. Each is approved by the operator before use, changes are notified in advance with the right to object, and for a fully on-premises or sovereign deployment the list can be reduced to Altuon itself. The agreement carries the audit and access rights the operator needs to satisfy both its telecom regulator and its data regulator, including the right to have Altuon respond to a supervisory request within the deadline the regulator sets. Service levels, incident notification windows, liability and insurance are stated in the agreement in full, not referenced in a schedule the operator has not seen.
Bring us the system your subscribers depend on.
Whether it is a service line, a billing core, a spectrum decision or a campaign, the Discover phase begins with your licence conditions and your data obligations and ends with a register your operating committee can approve. Request a proposal, or book a briefing for the executives who will be asked to sign.