Onboarding & Number-Porting AI Agent

What this agent does

Does the order work, not the hold decision

Ingesting the port request and the account record from supported ordering, CRM or LSR sources.

Normalising the number, account number and zip code into the form the LSR requires, and stamping the interval.

Reason

Assembling only the simple-port fields 47 CFR 52.36 permits, plus a passcode where the customer was assigned one.

Applying the carrier's configured onboarding, market and due-date rules to the order.

Binding each field to the record it was read from, and marking what the account leaves unresolved.

Decide

Recognising a request that may be a line separation, and routing it to trained staff without scoring it.

Routing anything that would delay or reject a port to the provisioning desk.

Out

Retaining the request, the fields it carried, the timestamps and the release.

Executing write actions only inside the approval boundaries agreed during implementation.

→ Product statement

The agent prepares and tracks the order; a provisioning person decides any hold, and the carrier remains the party the interval binds.

Example workflow

One port, request to release

AgentHuman

1Port request receivedOrder portal, retail or care system, or an inbound LSR from the gaining provider

2Fields assembledThe standard simple-port fields, an assigned passcode where there is one, and the received timestamp

3Order preparedValidated fields, due date and confidence

4Controls appliedField-set checks, interval timing, line-separation detection and confidence threshold

No human action required

Stages 1 to 4 run unaided and none of them pauses the interval — the agent is preparing the order, and the desk's lane opens at the confidence gate.

5DecisionBranches at the confidence threshold

High confidence

Goes to the provisioning desk to release.

Low confidence

Adds a porting-desk check first.

Provisioning release

The order is held with its fields, its flags and the time left in the interval.

Release · Correct · Send to fraud review

Released — order sent▼

6Order systems updatedOnly where write access and approval policy allow it

7Outcome evaluatedInterval performance, desk corrections, rejections and ports put right after release

Corrections

Every desk correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required8 items

Holding a port, or delaying one past the interval.

Requiring any field outside the closed standard set.

Surfacing an account balance inside the port flow.

Actioning a line-separation request from a survivor.

Automation boundaryAgent acts unaided

✓Collect the standard simple-port fields the rule permits.

✓Validate the fields for form, and carry each source forward for the named owner.

✓Run the checks the carrier has configured for the market.

✓Flag what a person must decide, stop there, and show the time left.

Any write happens inside the boundaries agreed at implementation, never ahead of a release.

Standing in as the third-party verifier of a change.

Placing any offer on the authorisation screen.

Returning a rejection to the gaining provider.

Changes to field, interval or authorisation rules.

Example output

One port order, annotated

Everything the agent puts on the order is attached to the record it was read from.

Port-order output · single requestIllustrative example

Order

Request

Due date

Field set

Confidence

Authorisation

Simple port-out

Number, account number and zip code taken from the account record

Next business day

Standard fields only

94%

Separate LOA screen

As receivedTaken from the account record and the inbound LSR — nothing on this side is supplied by the agent.

Fields used Account record match Assigned passcode Received timestamp

Why these fieldsThe rule closes the list and a person still decides and it is logged..

ActionReleaseCorrectSend to fraud review

What the score decidesBelow the configured threshold the order picks up a desk check before anyone releases it.

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value landsValue 01 – 04

Every port requestFrom the order or the LSR

03Preparation

Build from the record

Use the account record, the closed standard field set and the carrier's configured market and interval rules.

01Approved path

Port on the clock, not on a hunch

Routine simple ports arrive validated and already inside the interval.

02Human review

Send the desk to what needs deciding

Flagged orders and low-confidence requests are marked, so the desk's time goes where a decision is actually owed.

04Build an evidence trail

The request, the fields it carried and the person who released it stay on the order.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

Porting and numberingLSR gateway · NPAC feed
ATIS LSOG order formats

BSS / OSSAmdocs · Netcracker
CSG · Optiva · in-house billing

CRM and careSalesforce · Dynamics 365
Zendesk · ServiceNow

Agent

Onboarding & number porting

Reads the record
Builds the order
Stops for release

Identity and authorisationLOA capture · e-signature
Independent TPV · IVR authorisation

Observability & evaluationOpenTelemetry · Langfuse
Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the port order

Controls stack inward. What the stack does not catch is set out in the map below.

L6 · Outermost — last line of defenceInward → L1 · closest to the model

L6Rollback / safe modeNarrow the agent to preparing and reporting when evaluation or production signals degrade.Roll back

L5Version monitoringTrack model, prompt, field-rule and interval-configuration changes.Track

L4TraceabilityRecord the request, the fields, the timestamps, the flags and the release.Record

L3Provisioning releaseA person decides any hold; it governs who decides, not whether the hold was justified.Gate

L2Field-set guardrailsTest the order against the closed field set and the configured rules; a failure returns the order.Restrict

L1Confidence thresholdsRoute low-confidence orders to a desk check; confidence is not a reading of intent.Require review

Model coreOrder prepared — validated fields, due date, interval position and confidence

L1 – L2Test whether an order may stand

L3Puts the release in a person's hands

L4 – L5Keep the request and the fields it carried

L6Narrows to status reporting when signals degrade

How Nestack evaluates it

Evaluate the whole porting workflow — not only the completed port.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the order the customer sees

Depth of coverage ▼

E1Final-output evaluationDid the order carry only the fields the rule permits?

E2Step-level evaluationDid the agent read the right account, market rules and interval configuration?

E3Tool evaluationDid it read and write the correct order and the correct field?

E4Confidence calibrationDo low-confidence orders actually attract more desk corrections?

E5Slice evaluationHow does performance change across specific order types?

E6Business outcomeHow many orders needed a desk correction, and how many were put right after release?

Floor — whether the number arrived on time

Failure modes

Where each failure originates in the agent

Seven failure modes, placed at the stage each one originates.

Agent lifecycleDirection of processing →

01 · Retrieval1 mode

VP-03

Stale account record

Passcode or account number read from a superseded record.

Stage gathersAccount record, assigned passcode

02 · Reasoning2 modes

VP-04

Survivor read as attacker

A line-separation request scores as a port-out fraud signal.

VP-06

Interval consumed by review

Verification work eats the business day the rule allows.

Stage proposesThe order, its fields and the confidence

03 · Tool / write2 modes

VP-02

Balance surfaced in the flow

An outstanding balance appears inside the port conversation.

VP-05

Authorisation voided by offer

An inducement lands on the authorisation screen.

Stage writesOnly where write access and approval policy allow it

04 · Output1 mode

VP-01

Unauthorised required field

The order asks for something outside the closed standard set.

Stage returnsThe order the desk releases and the gaining carrier sees

05 · Change / Version1 mode

VP-07

Silent interval regression

A model or rule change slows the path to release.

Stage tracksModel, prompt, field rules and interval config

Sev-1 · a port is delayed Sev-2 · an unpermitted field is required Sev-3 · record degrades, order routes to the desk

See the complete Telecom failure-mode catalogue →

Affected slices

Overall timing can hide one bad cohort

Survivors are the cohort no aggregate counts: a line-separation request is confidential by law, so it never appears in a fraud or retention report. Nestack reports the desk-correction rate by slice, not only in total.

Slice performance — reported separately, not only in aggregateIllustrative example

Slice	Failure rate	Lift	Status
Line-separation requests	7.0%	3.4×	Review
Ports with a disputed balance	4.5%	2.2×	Review
Non-simple and multi-line ports	3.3%	1.6×	Watch
Standard simple ports	1.2%	0.6×	Normal

Bar: desk-correction-rate lift vs. the all-orders baseline · scale 0–4.0× · tick marks the 2.0× review threshold 2 of 4 slices over threshold

Evidence-linked improvement

The cycle ends in a case, not a note

An apology does not close a cycle; a case the next release must pass does. That suite is what the next port through the desk is measured against.

Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn

01Detect

Desk-correction rate rises in an order slice.

02Diagnose

Within the same business day, the desk reads the orders behind the rise until the cause narrows to one.

03Improve

The correction is versioned, with the orders that motivated it attached.

04Verify

A failing case holds the release until it passes.

05Learn

The case is added permanently, and the port rules move with it.

Learn → DetectThe return edge. The next cycle is measured against a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, order workflow, evaluation, integration, then production validation and handover.

Workstream Week 1Week 2Week 3Week 4Week 5Week 6

01Porting workflow discovery and automation-boundary definition.

02Order and LSR source assessment.

03Standard field-set and interval-rule mapping for each market.

04Order ingestion and field normalisation.

05Validation logic and record binding.

06Confidence scoring and desk routing.

07Provisioning release workflow.

08Order-management and LSR integration.

09Port-interval and field cases.

10Guardrails and authorisation controls.

11Order-trail instrumentation.

12Deployment, documentation and Agent Care handover.

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tier PilotOne market, one order path ProductionProduction order systems AdvancedMultiple markets / brands

Introduced at Pilot

Order preparation on your rules✓✓✓

Provisioning release✓✓✓

Port-completion baseline✓✓✓

Introduced at Production

Reporting by order type—✓✓

Desk workflow in your systems—✓✓

Approved write-back—✓✓

Order-management integration—✓✓

Introduced at Advanced

Multi-market interval rules——✓

Multi-stage provisioning approvals——✓

High port volume——✓

Multi-market porting controls——✓

Build price From $5,000 From $8,000 Custom quote

Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.

Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

You bringWe build with it

01Your order intake fields and account record structure → Order ingestion and field mappingWeek 1

02Representative completed port orders → Validation baseline, field-set extraction and record bindingWeek 2

03Your market rules and assigned-passcode policy → Field-set, interval and market-rule mappingWeek 1

04Access to relevant APIs, feeds or exports → Order and LSR assessment, then integration setupWeek 2

05Ports you would not want delayed → Interval cases and the evaluation suiteWeek 4

06What must reach a person before a port is held → Confidence scoring, desk routing, guardrails and release controlsWeek 3

07Named provisioning staff to release orders → Provisioning release workflow, then pilot and production validationWeeks 5–6

Nothing else is required Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

Each band covers the weeks the work really takes, so week 5 carries evaluation and launch together.

Phase W1W2W3W4W5W6

Discovery W1

Build W2 – W3

Evaluate W4 – W5

Pilot & Launch W5 – W6

Week focus W1Porting workflow discovery, field mapping and the automation boundary W2Order and LSR integration and the validation baseline W3Order workflow, confidence logic and release controls W4Evaluation suite, interval checks and failure-mode testing W5Order-system integration, pilot ports and targeted corrections W6One porting cycle run under the provisioning desk, then handover

Reading the bandEach band spans only the weeks its work is named in. The fifth week genuinely carries two kinds of work.

At the end of W6Validation finishes on live orders and Agent Care assumes monitoring.

DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Telecom AI agent

Build a porting agent around the interval you are already bound by.

Show us your order path, your field set and who releases a port. Get it wrong and the delay is itself the violation — so we map the boundary and name what stays with a person.

Discuss this agent →

Nestack Agents · Onboarding & number portingAGT-TL-04 · Agent Care available after launch