Skip to content

Telecom

Operations tools built by AI, inside the network you already run

Provisioning exceptions, field work orders, SLA breaches and site audits fall between OSS, BSS and ticketing. Describe the tool and ToolJet builds it on those systems, scoped by region and role, running inside your own network if that is where it has to be.

  • Provisioning exception queues
  • Field work-order tracking
  • SLA and NOC dashboards
Example Telecom app · illustrative data
Provisioning exceptionsFibre · Region WestSSOAudit onProduction
Orders in exception31247 over 72h
Cleared today126median 3.4h
Field visits scheduled586 unassigned
OrderExceptionOwnerStatus
ORD-88412 · FTTP 1GPort mismatchProvisioningResolved
ORD-88437 · SIP trunkNumber port pendingNumber opsWaiting carrier
ORD-88451 · FTTP 500MNo ONT detectedField · WestEscalated
ORD-88460 · Business 5GCredit holdBillingResolved

Auto-create a field work order when an ONT is not detected 24h after install and assign it to the nearest crew

Trigger, work-order query and assignment logic added · awaiting your review

40,000+stars on the open-source core
AICPA SOCISO 27001
SOC 2 Type IIISO 27001 and GDPR · Visit the trust centre
Your infrastructureCloud, VPC, on-premise or air-gapped
100+ connectorsplus any REST or gRPC endpoint

No engineering ticket needed

Describe the tool you need. ToolJet builds it.

Type what you want in plain language. ToolJet generates the pages, queries and logic as a working app. Connect your data, set who can see what, and review the generated logic before publishing. Edit the app on the canvas afterwards.

  • Working app, not a mockup
  • Review access rules before publishing
  • Free to start, per-builder pricing
Enter to build · Shift+Enter for a new line

Built on the systems telecom teams already run

  • Oracle
  • PostgreSQL
  • SAP HANA
  • REST API
  • Zendesk
  • Jira
  • Twilio
  • Slack
Browse all integrations

Have developers? They can build the same apps fromClaude CodeCodexCursorGitHub CopilotGrok Buildthrough the ToolJet plugin

What telecom operations teams build with ToolJet

Provisioning and order exception handling

Stuck orders by type and age with owners, clearance actions and escalation to field or carrier.

Field work-order management

Crew assignment, photos, checklists and sign-off, usable on a phone at the site.

NOC and SLA dashboards

Open incidents, affected services and SLA clocks from your monitoring and ticketing systems.

Site, tower and asset audits

Scheduled audits with checklists, findings and follow-up actions tracked to closure.

Number and porting operations

Port requests, carrier waits and exceptions with a clear owner at every step.

Billing and credit exception queues

Credit holds, disputes and adjustments with approval thresholds and a decision record.

How operators roll it out

  1. 01

    Deploy inside the network

    Self-host on Kubernetes, Helm or OpenShift in your data centre or private cloud, air-gapped where required.

  2. 02

    Connect OSS, BSS and ticketing

    Oracle, SAP, Postgres and your service platforms connect once with scoped credentials, over direct connections or REST and gRPC.

  3. 03

    Scope by region and function

    Field crews see their region, NOC sees the network, billing sees accounts. Row-level rules are part of the build.

  4. 04

    Automate the hand-offs

    On Self-hosted, event-driven workflows create work orders, escalate breaches and post updates to Slack or Teams.

Built in, not bolted on

The controls your compliance team already expects

Critical infrastructure means the tooling has to live where the network lives. ToolJet self-hosts fully, including air-gapped, with SSO, role and row-level access and audit logs on every app.

Single sign-on and SCIM

SAML, OIDC and LDAP, with directory groups mapped onto ToolJet roles and provisioning through SCIM.

Permissions down to the row

Workspace, app, page, component and query-level access. Row-level security scopes records to the right person.

Audit logs and SIEM export

Platform events with actor, resource and timestamp; configurable retention; export to your SIEM.

Runs where you say

Choose managed ToolJet Cloud or self-host in your VPC, on-premise or air-gapped. Self-hosted Enterprise offers BYOK and private AI deployment options.

Security and governance features vary by plan. Workflows and Agent Builder are available on Self-hosted only; BYOK is a Self-hosted Enterprise add-on. Compare plan availability.

Two ways to get there

Build it yourself, or bring our engineers in

Self-serve

Your team, your pace

Start free. Describe the tool, refine it on the canvas, and ship it under your own access rules. Start with one app, then test it with your team before rolling it out.

Start free

Professional services

Forward-deployed engineers, embedded with your team

When the timeline is fixed or the process is tangled, our engineers build alongside you: scoped delivery, production-ready apps, and knowledge transfer so your team owns the result.

Talk about a project

Questions telecom operations teams ask before they start

Can it run in our own data centre without internet access?

Yes. Air-gapped self-hosting is supported on Kubernetes, Helm, OpenShift and Docker. Updates are applied on your schedule, and no outbound connection is required to run it.

How does it connect to OSS and BSS platforms?

Natively to Oracle, SAP HANA, Postgres and other databases, and to any REST, gRPC or GraphQL API exposed by your service, inventory or billing platforms, alongside 100+ connectors.

Can field crews use it on mobile?

Yes. Apps are responsive and can be laid out for phones and tablets, including photo capture through file upload components.

How do we keep regional teams to their own data?

Row-level security scopes records by region, crew or account, on top of page and query permissions mapped from your directory groups.

Is there an audit trail for changes to orders?

Platform audit logs record events with actor, resource and timestamp, with SIEM export. Order actions taken in the app are written back to your systems of record.

Clear the exception queue with a tool your ops team owns

See it on your OSS/BSS data with an engineer, inside your network.

Page updated