From request to service
Connect the portal to provisioning, routing and billing. Make each handoff visible.
Independent engineering. Connected operations.
We connect billing, call control and AI so your business can work as one.
See how it connects
Connect the work, not just the software.
Your portal, switch and billing system can stay. We build the interfaces and workflows between them.
A customer should not need three teams
to activate one service.
Connect the portal to provisioning, routing and billing. Make each handoff visible.
Bring call records, quality evidence and charges into the same operational picture.
Give assistants approved data and tools, with people in control of consequential actions.
An integration we are working toward
Hadlo’s portal. Sergey Popov’s billing and provisioning. Telegent’s SIP Control Plane. One connected workflow.
The billing platform prepares the commercial policy. SCP validates it and publishes a version to the routing runtime.
Illustrative browser demo. Synthetic data, no live calls or carrier requests.
Customer & operator UI
Number search, assignment, routing and reports for each customer.
Existing · owner’s systemContract & orchestration
Idempotent commands, tenant checks, one owner per identifier, explicit errors.
ProposedBusiness operations
Sergey Popov’s platform: rates, least-cost routing, provisioning, rated records.
Existing · owner’s systemPermitted AI
Explains decisions from evidence; proposes changes; acts only through the contract and its role.
Prototype · simulated modelsSignalling & admission
Versioned routing, admission limits, edges. Full integration into this stack is planned.
Planned · from source-project experienceNumbers & trunks
Vendor APIs behind one interface. In the lab: fake vendors only.
LabEvidence
Replay-safe call legs; duplicates and late events handled; totals must match.
ProposedQuality
Test-call measurements attached to the call they describe.
Labnumber.assign.requested · key=7f3cnumber.reserved · DID +1 555 0142 · tenant=demo-aorder.confirmed · vendor=fake-1routing.published · version=42 · rates=r7call.admitted · route=B · routing_version=42cdr.leg ×2 · duplicate ignored ×1vq.sample · synthetic · linked to callreconcile.ok · legs=2 · charge delta=0 on replayreport.ready · tenant=demo-aassistant.answer · sources=3 · actions=0Synthetic event log (generated in your browser)
The portal, billing platform and SIP Control Plane are separate source systems. The combined Hadlo workflow shown here is a proposed integration, not a completed deployment. The walkthrough is simulated. The brief builder runs in your browser.
A source system’s working feature does not establish that its integration is finished.
Each integration should leave tested components, documented interfaces and a team that knows how to use them.
We build the connection.
Your team learns to run it.
Engineering, monitoring, staff training and support belong in the same engagement. Reuse is limited to components and knowledge we are permitted to carry forward.
Agree one business outcome. Connect the systems, test the failure paths and demonstrate the result before a controlled rollout.
BuildKeep the integration supported. Add monitoring, train the people using it and introduce new capabilities as the business needs them.
OperateChoose the systems and the result you need. Download a project brief for the first conversation. Everything stays in your browser.
Generated locally · not sent
Engineers, operators, analysts and teachers: bring a concrete problem, a useful skill and work others can build on.