01
Analysis
We understand the business and the technical environment.
TELECOM SOFTWARE
Subscribers, services and operations.In one connected system.
We build custom software for internet providers and telecom companies. We connect subscriber management, billing, service activation and technical support with the systems you already use.
Operator panelIllustrative view
- 8,412Subscribers
- 11,380Services
- 37Activations
- 1,204Invoices
- 2Incidents
Order ORD-7731Fibre 300 · 12 Demo Street
- Order
- Verification
- Activation
- Confirmation
StateOrder recorded
The state changes only after the relevant system responds.
- INC-204 · 4 services affectedIn progress
- INV-2026-0412 · partly paidFollowing up
Customer portal
Fibre 100 Mbps
Active · 12 Demo Street
October invoice
€24.90Due
Move to Fibre 300
In progress- Subscriber management
- Automation and integrations
- Web and mobile portals
CUSTOM SOFTWARE
Staying connected to customers also takes systems that talk to each other.
A telecom service relies on several processes at once: the customer’s request, coverage, the contract, activation, billing and support. When these are handled separately, information is repeated and the service status becomes harder to follow.
At ENOR, we build applications and integrations that connect these steps. We give sales, finance and technical teams a clearer view, with defined roles and responsibilities.
Who exchanges what
Illustrative viewCustomerCRM / BSS
Request, contract and contact details
Click the same system again to return to the animation.
Click a system to see its responsibility. The arrows show the information being exchanged.
WHO IT’S FOR
Solutions shaped around the services you offer.
Each type of operator has different processes, systems and partners. The application is built around your model.
Types of operators we build software for.
Internet service providers — ISPs
Subscribers, plans, billing, activation and support.
Fixed-line and fibre operators
Orders, coverage, resource inventory and field work.
VoIP providers
Accounts, communication integrations, usage and administration.
Mobile operators and service providers
Portals, sales processes and integrations with the related systems.
MVNO / MVNE
Application components for administration, brands and partners, depending on the ecosystem.
IoT connectivity providers
Devices, SIMs, usage and administration, depending on the provider’s access.
CORE SOLUTIONS
Software for the commercial and operational side of the service.
You can start with one module or connect the systems you already have. Each card links to the matching explanation.
CRM and subscriber management
Customers, accounts, contracts and services in one profile.
Learn moreOSS / BSS
Connecting the commercial offer with technical delivery.
Learn moreBilling and subscriptions
Cycles, tariffs, plan changes and payments.
Learn moreService activation
Authorised commands and a verified state.
Learn moreSelf-service portals
Plans, invoices and requests for the customer.
Learn moreMobile apps
The subscriber portal on the phone too.
Learn moreService and resource inventory
Devices, ports, links and the services on them.
Learn moreTicketing and field work
Requests, incidents, visits and materials.
Learn moreMonitoring and analytics
Metrics and alarms with a source and a time.
Learn moreVoIP and real-time communication
SIP, WebRTC and CRM integrations.
Learn moreAPI integrations
RADIUS, IPAM, device management and finance.
Learn moreSystem modernisation
Gradual migration without losing history.
Learn moreCRM AND SUBSCRIBER MANAGEMENT
One connected profile for every customer.
Sales, finance and technical teams see the same customer, with their services, invoices and requests.
- Individuals and businesses
- Contacts
- Installation and billing addresses
- Contracts
- Active services
- Plans
- Documents
- Invoices and payments
- Support requests
- Communication history
- Owners and tasks
Five levels that are never mixed up
- 01CustomerThe person or company you have a relationship with.
- 02Billing accountWhere and how invoices are issued.
- 03SubscriptionThe plan and the contracted terms.
- 04Technical serviceThe profile applied in the network.
- 05DeviceThe router, ONT or terminal at the customer.
One customer can have several services and locations, each with its own subscription and device.
Customer profileIllustrative view
DSDemo Studio LtdBusiness · 2 locations · owner: AnaActive
- CustomerDemo Studio Ltd
- Billing accountBA-2207 · monthly invoice
- SubscriptionFibre 300 · 24-month contract
- Technical serviceSRV-FB-1088 · profile FB-300
- DeviceONT-55821 · Head office
Switch the profile tabs. The “Overview” tab shows how the levels connect.
OSS / BSS
Connect the commercial offer with technical delivery.
We build applications and integrations that take an order from the catalogue to a delivered service, without re-keying.
BSS
Business Support Systems
Commercial processes such as customers, products, orders, billing and payments.
OSS
Operations Support Systems
Operational processes such as activation, technical inventory, incidents and service tracking.
What we can build
- Product and plan catalogue
- Orders
- Feasibility checks
- Activation flows
- Service inventory
- Integrations with network systems
- Fault tracking
- Reports
The path of an order
Illustrative viewBSS · commercial processes
OSS · operational processes
Catalogue
The plan and price are chosen from the product catalogue.
The steps light up in the order of a typical order. Click a step to stop on it.
A single application doesn’t automatically replace all your existing OSS/BSS. We define what is built, what is integrated and what stays in the systems you have.
BILLING AND SUBSCRIPTIONS
Clear rules for every plan and period.
Billing logic is built around the service model and keeps the tariff version that was applied.
- Recurring charges
- Installation fees
- Add-on services
- Prepaid, postpaid or hybrid models, depending on the project
- Billing cycles
- Renewal dates
- Plan changes
- Proration where applicable
- Discounts and promotions
- Partial payments
- Balances due
- Refunds and adjustments
- Reports
Different things, with different statuses
- Subscription
- Usage
- Invoice
- Payment
- Right to use the service
October invoice · Demo StudioIllustrative view
- Fibre 100 · 15 days
- €12.45
- Fibre 300 · 15 days
- €17.45
- Static IP (add-on)
- €5.00
- Promotion · month 2 of 3
- −€3.00
- Cycle total
- €31.90
Applied: tariff v3, valid from 1 March. The invoice keeps the version and the terms.
- SubscriptionFibre 300 · active
- UsageWithin plan
- InvoiceIssued
- PaymentPartial
- Right to useActive
Move the plan-change day and try the buttons below.
The tariff version and the terms that were applied are stored. Changing a plan’s price doesn’t change the history.
Fiscalisation and financial documents are handled according to the market and the specific integrations.
USAGE, RATING AND CHARGING
From usage data to the calculated charge.
Three different steps, each with its own rules and checks.
- 01MediationCollecting, normalising and checking usage data.
- 02RatingCalculating the charge according to the tariff and its rules.
- 03ChargingReserving or applying the charge according to the service model.
Depending on the project
- CDR / xDR
- Deduplication
- Units of measure
- Time zones
- Time-of-day tariffs
- Rounding
- Late events
- Adjustments
- Reconciliation
Usage data · line VO-311Illustrative view
| Event | Type | Quantity | Rate | Status |
|---|---|---|---|---|
| CDR-1041 | National call | 3:12 → 4 min | — | Valid |
| CDR-1042 | International call | 1:05 → 2 min | — | Valid |
| CDR-1042 ↺ | Copy of the same event | 1:05 | — | Copy · removed |
| CDR-1043 | SMS | 1 | — | Valid |
| CDR-1039 | Event from the previous cycle | 2:40 | — | Late · adjustment |
Mediation: the copy is removed, durations are converted to minutes and the late event goes to adjustment.
Step through Mediation, Rating and Charging. Under Charging, compare postpaid with prepaid.
Periodic billing and online charging are different functions and are designed separately.
Real-time charging needs the matching integration and metering; we don’t promise it without them.
SERVICE ACTIVATION AND MANAGEMENT
From the order to a verified service.
Actions on a service are authorised, traceable and protected against accidental repetition.
- Account creation
- Service profile assignment
- Plan change
- Suspension
- Reactivation
- Termination
- Status check
Four states of a command
- 01Command requestedThe action was requested and recorded.
- 02Command acceptedThe technical system received the request.
- 03ExecutionThe system is applying the change.
- 04Confirmed stateThe result was verified in the relevant system.
Activation · SRV-FB-1091Illustrative view
- Request
- Coverage check
- Approval
- Installation planning
- Activation
- Verification
- Completion
Command: apply profile FB-300Key: ACT-7731-a9
- RequestedRecorded with a unique key
- AcceptedThe system received the request
- ExecutingThe profile is being applied
- ConfirmedVerified by the technical system
Send the command and step through the states. Try “Simulate: verification fails” too. No command is real.
A service isn’t marked active just because an API returned an initial success response.
Repeated requests are recognised by their unique identifier and don’t create duplicate actions.
ISP INTEGRATIONS
Applications that connect to your technical environment.
We connect commercial and operational applications to the systems that keep the network running, after assessing the documentation and access.
Examples of integrations that can be assessed
- RADIUS and AAA systems
- PPPoE account management
- DHCP / IPAM systems
- Device management platforms
- Router APIs
- OLT / ONT through supported interfaces
- Monitoring systems
- Inventory and GIS
- Finance systems
- Payment providers
- SMS and email
Product examples, with their limits
- MikroTik RouterOS
- From version 7.1, RouterOS offers a REST API, a JSON layer over the console commands that needs the web service enabled. Older versions use the native API. The available functions depend on the version and configuration.
- FreeRADIUS 3.x
- Connects to applications through the SQL module, for authorisation and accounting from a database, or through the REST module, depending on the server configuration.
- TR-069 / TR-369 (USP)
- Standards for managing devices such as routers and ONTs through a management platform. Support depends on the device and its firmware.
Compatibility depends on
- The product
- The version
- The licence
- The API
- The configuration
- Access
- The customer’s environment
Integration statusIllustrative view
RADIUS / AAA
Creates and updates subscriber accounts and reads accounting for usage, according to the server schema.
The portal and apps talk to the integration APIs. Device administration interfaces are never exposed to the public portal.
Pick an integration to see what it does and how fresh its sync is.
We don’t promise universal integration with every network device. Each integration is assessed against the actual documentation and environment.
Device administration interfaces are never exposed directly to the public portal.
SUBSCRIBER PORTAL
More actions within the customer’s reach.
Customers see their own services, invoices and requests, with a clear indication of what is confirmed and what is still in progress.
- Services and plans
- Invoices
- Payments
- History
- Change requests
- Support tickets
- Request status
- Notifications
- Documents
- Contact details
- Communication preferences
Three kinds of information
- 01Confirmed stateWhat the technical system has verified.
- 02Request in progressWhat the customer has asked for and is waiting on.
- 03Last received dataThe latest value read, with the time it was received.
My portal
Illustrative viewConfirmed plan
Fibre 100 Mbps
Installation address: 12 Demo Street
Request
Move to Fibre 300No request
- October invoice€34.90
- ConnectionOnline
Last received data: 3 min ago
Request a plan change and see how the portal changes before and after technical confirmation.
A plan change or reactivation isn’t shown as completed before technical confirmation.
The portal and the mobile app use the same APIs and access rules.
SUPPORT AND FIELD WORK
Connect the customer’s request with the work that needs doing.
From the ticket to the field visit, every step is linked to the subscriber, the service and the agreed deadlines.
- Ticketing
- Categorisation
- Priority
- Owner
- Deadlines per agreement
- Link to subscriber and service
- Visit planning
- Field technicians
- Materials used
- Photos
- Completion form
- Confirmation and history
Requests · Centre areaIllustrative view
- TK-8812No internet · 12 Demo StreetHigh
- TK-8815Connection drops · 14 Demo StreetHigh
- TK-8817No internet · 9 Demo StreetMedium
Field work · INC-204
- Technician
- Team 3
- Visit
- Today, 14:00–16:00
- Agreed deadline
- 8 hours
- Status
- On site
2 fibre connectors3 photos
Link the requests to the incident, then simulate the signal coming back.
For shared incidents, several requests are linked to a single incident.
A request isn’t closed automatically just because a technical signal came back, without defined rules.
INVENTORY AND NETWORK VIEW
Know how resources and services connect.
The inventory shows which devices, ports and links carry each service, and where each piece of data comes from.
- Locations
- Devices
- Ports
- Links
- Circuits
- Addresses and allocations
- Linked services
- Administrative status
- Change history
- GIS integration
Three sources that are never mixed up
- 01Planned inventoryWhat will be built.
- 02Recorded inventoryWhat is documented as built.
- 03Discovered stateWhat the technical systems report right now.
Inventory · Centre areaIllustrative view
Source: managed inventory · last change yesterday
| Object | Type | Link / service | Status |
|---|---|---|---|
| OLT-TR-01 | OLT | Port 1/2 → 28 ONTs | In service |
| ONT-55821 | ONT | SRV-FB-1088 · Fibre 300 | In service |
| ONT-55822 | ONT | SRV-FB-1091 · Fibre 100 | In service |
The managed diagram is not presented as a live topology.
Switch the tabs to compare planned, recorded and discovered.
A manually maintained diagram is never presented as a live topology.
Differences between the inventory and the discovered state go to review, not to an automatic change.
MONITORING AND ANALYTICS
From technical signals to an operational view.
We integrate monitoring sources and show them in the context of the affected services and customers.
- Metrics
- Alarms
- Events
- Device state
- Affected services
- History
- Trends
- Reports
Possible mechanisms, depending on the system
- API
- SNMP
- Syslog
- Telemetry
- Webhook
Every indicator has
- A source
- An update time
- A unit
- Context
- A data status
Operational view · Centre areaIllustrative view
OLT-TR-01 uplink loadCurrent
62%
5-minute average
Source: SNMP1 min ago
ONTs offlineCurrent
3of 28
Port 1/2
Source: Device platform2 min ago
Active alarmsCurrent
2
1 critical · 1 warning
Source: Syslog1 min ago
Affected servicesCurrent
4
Linked to INC-204
Source: Inventory + alarms2 min ago
Every value shows its source and update time.
Disconnect the monitoring source and see how old values are marked.
Old or missing data is never shown as a normal state.
A dashboard doesn’t guarantee instant detection of every fault or any specific uptime.
VoIP, SIP AND WebRTC
Communication integrated with your business applications.
We build portals, integrations and communication apps around the platform and provider you use.
- VoIP administration portals
- PBX integrations
- Accounts and numbers per provider
- Click-to-call
- Call history
- CRM integrations
- In-app voice and video
- Operator panel
- Usage reports
- SIP
- For call signalling in the relevant ecosystems.
- RTP / SRTP
- For media transport, depending on the implementation.
- WebRTC
- For communication in supported apps. It may need signalling, STUN / TURN and other integrations.
How a call travels
Illustrative viewApp (WebRTC)
Signalling / PBX
SIP phone
Signalling
The app and the server exchange the call invitation and its parameters.
- STUN / TURN
- Click-to-call
- Call history
- CRM integration
Call recording
The animation follows the signalling and media paths. Recording starts switched off.
Using WebRTC doesn’t automatically mean end-to-end encryption. The protection boundary depends on the architecture and the intermediaries.
Call recording is not enabled by default.
IoT AND CONNECTIVITY MANAGEMENT
Control over devices and connectivity services.
Panels and integrations are built on the APIs of the operator providing the connectivity.
- Device inventory
- SIM / eSIM
- Activation status
- Plans
- Usage
- Limits
- Notifications
- Groups
- Reports
- IoT platform integrations
IoT SIMs · Demo MetersIllustrative view
- SIM ···1021Water meter · Group A412 / 500 MBActive
- SIM ···1022Water meter · Group A476 / 500 MBActive
- SIM ···2210Tracker · Group B36 / 200 MBSuspended
Actions go through the operator’s API.
Suspend or reactivate a SIM: the action goes to the operator as a request.
ENOR doesn’t issue eSIM profiles and doesn’t provide mobile connectivity itself. These functions depend on the operator and the related authorisations.
Platform capacity is set by the architecture and real tests, not by a number declared up front.
MVNO / MVNE AND WHITE-LABEL
Digital components for different brands and partners.
We build portals, apps and processes for several brands on the same platform, according to the integrations with the host operator.
- Onboarding
- Catalogue
- Orders
- Portals
- Apps
- Billing
- Partners and agents
- Per-brand configuration
- Roles
- Reports
The integrations with the host operator or enabling platform decide what can be delivered.
A platform for several brandsIllustrative view
VVala DemoConsumer brand
- Basic€9.90 / month
- Plus€14.90 / month
- Max€19.90 / month
Brand subscribers: 12,480 · other brands’ data isn’t shown
Switch the brand and try opening the other brand’s subscribers.
White-label doesn’t transfer licences, agreements or operating rights.
Multi-tenant includes server-side data isolation, not just a different logo or interface filters.
5G, SDN, NFV AND EDGE
Integrations with advanced telecom ecosystems.
After assessing the project, we can build applications, panels and automation flows around the operator’s existing systems.
- Consuming operator platform APIs
- Administration and reporting
- Authorised automation
- Orchestrator integrations
- Collecting and presenting data
- Apps that use edge where required
Where the project scope lies
Illustrative view- An app that uses a 5G networkIn scopeA web or mobile app running on the operator’s network, without changing the network itself.
- Integration with the 5G platformAfter assessmentConsuming APIs, reporting or authorised automation, depending on the access the operator grants.
- Core network or RAN functionsOut of scopeDeveloping the network functions themselves. ENOR doesn’t offer this service.
Not every application needs SDN, NFV or microservices.
We don’t promise “zero latency”, removing all hardware or guaranteed savings.
AI AND AUTOMATION
Help for your team, with controlled actions.
AI helps with search, summaries and classification, while actions with impact stay under human approval.
- Request classification
- Documentation assistant
- Incident summaries
- History search
- Anomaly flags
- Suggested fixes
- Usage analysis
- Support for customer follow-up
The assistant’s limits
- No network changes
- No service interruptions
- No financial actions
- Human approval for actions with impact
Operations assistantIllustrative view
Pick a question above.
Pick a question and see where the assistant stops.
AI doesn’t change the network, interrupt services or perform financial actions without defined limits and authorisations.
We don’t promise to prevent every fault or to predict customer churn with certainty.
SECURITY AND TRACEABILITY
Control over access and changes.
Measures are defined per project, data and integration, and every important action leaves a trace.
- Roles
- Least privilege
- Multi-factor authentication
- Separation of duties
- Approval for critical changes
- Credential management
- Encryption
- Audit logs
- Environment separation
- Restricted integration access
- Backups
- Restore tests
- Monitoring and updates
Audit logIllustrative view
| Who | What | When | Object | Result | Ref. |
|---|---|---|---|---|---|
| Ana (Sales) | Plan change | 10:42 | SRV-FB-1091 | Requested | AUD-5512 |
| Activation system | Profile applied | 10:43 | SRV-FB-1091 | Confirmed | AUD-5513 |
| Bledi (Finance) | Invoice adjustment | 11:05 | INV-2026-0412 | Approved | AUD-5520 |
| Erion (Support) | Access to integration secret | 11:20 | RADIUS · •••• | Denied | AUD-5524 |
Passwords and secrets are never written to the log; they appear masked.
Filter the log by type of action.
Every important action records
- Who acted
- What was requested
- When
- On which object
- The result
- The related reference
Passwords, secrets and sensitive content are not stored in logs.
Integration credentials are stored separately and used only by the services that need them.
PRIVACY AND MARKET REQUIREMENTS
Requirements defined by service and country of operation.
Legal and contractual requirements differ by country, service and agreements, so we identify them during the analysis.
During the analysis we identify
- Personal data
- Usage data
- Retention periods
- Responsibilities
- Providers
- Transfers
- Access controls
- Contractual and sector requirements
We don’t claim universal compliance with GDPR or with every telecom regulation.
Every legal statement or technical standard in a project is checked against current official sources.
MODERNISATION
Improve your systems without losing service history.
We modernise in phases and check contracts, active services and balances before and after every switch.
- Technical audit
- Process mapping
- Gradual integrations
- Trial migration
- Contract checks
- Active service checks
- Invoice and balance reconciliation
- Keeping references
- Pilot
- Rollback plan
Trial migration checkIllustrative view
- 01Audit
- 02Process mapping
- 03Gradual integrations
- 04Trial migration
- 05Contract and service checks
- 06Pilot
- 07Final switch
| Data | Source | Migrated |
|---|---|---|
| Contracts | 9,214 | 9,214 |
| Active services | 11,380 | 11,380 |
| Open balances | 2,106 | 2,103 |
3 balances differ → under review before the switch
Rollback plan: ready
We don’t promise a migration without downtime before assessing the system.
Switching to the new system doesn’t create duplicate activations, suspensions or charges.
DEVELOPMENT PROCESS
From your existing processesto an integrated system.
We choose the architecture based on load and requirements. We don’t impose microservices, Kubernetes or complex platforms without a need.
02
Scope and integrations
We define the modules, systems and access.
03
Architecture and UX/UI
We design the structure and the interfaces.
04
Phased development
We build with regular demos.
05
Testing
Functional, financial and technical.
06
Pilot and go-live
We go live with a plan and checks.
07
Maintenance
We monitor and improve according to the agreement.
Which systems should connect at your operator?
Talk to ENORThe timeline is set after the analysis and also depends on third-party access and systems.
TESTING
We also test what happens when an action stops halfway.
Tests check the technical and financial outcome, not just how the interface looks.
- 01The activation request is repeated.Expected result: Only one action is created; the repeat is recognised by its identifier.
- 02The API times out, but the action went through.Expected result: The status is checked in the system before any retry.
- 03A payment is confirmed after suspension.Expected result: Reactivation follows the defined rules and is recorded in the history.
- 04A plan change partly fails.Expected result: The real state of each step is shown, and the new plan isn’t billed without confirmation.
- 05Usage data arrives twice.Expected result: The copy is caught in mediation and not charged.
- 06An event arrives late.Expected result: It is handled as an adjustment according to the cycle rules.
- 07The monitoring source disconnects.Expected result: Panels show missing data, not a normal state.
- 08A subscriber opens someone else’s invoice.Expected result: The server refuses the request and the attempt is logged.
- 09A bulk process affects many services.Expected result: A preview, a limit and authorisation are required; the result is reported per object.
- 10Migration must keep balances and statuses.Expected result: Balances and statuses are reconciled before and after the switch.
For bulk actions we provide a preview, limits, authorisation and a detailed result.
We don’t state user numbers or specific availability without measurement.
WHY ENOR
A development partner for systems that have to work together.
- Process analysisWe understand how an order flows from sale to active service.
- Documented integrationsEvery connection has a defined API contract, errors and behaviour.
- Interfaces for different usersFor customers, sales, finance and operations.
- History and control of actionsWho did what, when and with what result.
- Testing of critical casesTimeouts, repeats, late events and bulk actions.
- Phased development and maintenanceNew modules and integrations as agreed.
FAQ
Frequently asked questions.
Other services
More solutions for your business needs.
- Software DevelopmentCustom software for your business processes.
- API Development & IntegrationSecure APIs that connect your systems.
- Mobile AppsiOS, Android and cross-platform apps.
- SaaS Platform DevelopmentSubscription products with many customers.
- AI Assistants & AgentsAssistants that work with controlled sources.
- Technical Support & MaintenanceMonitoring, updates and fixes after launch.
Which processes should connect better at your operator?
Tell us how you manage subscribers, services and operations. We’ll define the functions and integrations the project needs.
What our clients say
5.0
AArben Hoxha, CEO
Sample Logistics Co.
“They translated complex technical concepts into clear decisions for our team.”