Skip to main content
Platform serviceProvisioning workflow API

Telecom Provisioning (TMS)

Creates telecom users through ordered, logged steps, and rolls back cleanly when one step fails, so there are no half-created accounts.

In plain words

Setting up a phone user involves several systems in a strict order. If step four fails, you're left with a broken account. TMS runs the steps in order, records each one, and undoes the earlier steps if something fails, so support never has to clean up by hand.

Interactive preview

How Telecom Provisioning (TMS) works

Interactive · illustrative sample data

The challenge

Manual provisioning across LDAP, extensions and phone profiles leaves broken, half-created users whenever a step fails, and takes hours to debug.

Our approach

Treat provisioning as a workflow: sequential operations with explicit state, per-step logging, and compensating actions on failure.

Step by step

From first click to finished job

  1. 1

    Provisioning request arrives

    With company_id and an idempotency key.

  2. 2

    Steps run in order

    Each step logs input, output and duration.

  3. 3

    Failure triggers compensation

    Earlier steps are disabled or reverted automatically.

Capabilities

What it does

Ordered pipeline

Create LDAP user → verify → apply phone profile and routing rules.

Clean rollback

Failures stop the pipeline and undo partial records.

Multi-company

company_id scoping and per-tenant profile templates.

Security

JWT + HMAC for service calls; 2FA for admins.

Engineering

Key decisions

Test the failure paths

PHPUnit suites simulate mid-pipeline failures and concurrent requests.

Architecture

Tech stack

API & UI

  • Laravel
  • React
  • TypeScript

Security & quality

  • JWT
  • 2FA
  • PHPUnit

Outcome

What it delivers

  • No more half-created users after partial failures
  • Every provisioning step is traceable

Deep dives

Read the engineering notes

Services behind it