GUIDED PILOT · OPERATOR REVIEW REQUIRED

Run a guided pilot with 50 customers and one router.

Start with a small customer sample. Rehearse the path from payment to access evidence with your team. CRM, billing, payments, and access control are guided pilot foundations, with live actions subject to readiness gates.

What your team prepares

Planning a Tanzania evaluation? Read the Tanzania operator checklist for local payment targets and language requirements.

  • A customer export with stable identifiers and the agreed service/balance fields.
  • A plan list: prices, renewal rules, speed profiles, and exceptions.
  • An operator who can arrange scoped router or RADIUS access after review.
  • Your payment provider account and a test workflow; provider support must be qualified.
  • A finance contact, approved message templates, and a rollback owner.

Use the contact form to describe the setup. Do not include passwords, API keys, or customer exports; agree a secure handoff during onboarding.

What we work through together

Done-for-you import assistance uses guided pilot import preview/apply and external-reference foundations. Reconcile the sample before expanding it.

Basic subscriber records, search, and device assignment are shipped. CRM/Customer 360, invoice/payment foundations, and notifications remain guided pilot scope. MikroTik RouterOS REST client, backup export, neighbor discovery, and enrollment are guided pilot scope; guarded writes and RouterOS 6 fallback remain product work.

We define a reviewable evidence checklist for the chosen workflow. Live provider integration and automatic suspension and reconnection remain roadmap requirements.

A four-week working plan

  1. WEEK 01

    Prepare and import

    Choose 50–200 customers and one router or RADIUS endpoint. We help map your export, preview the import, and reconcile the sample. Agree which system owns each field; keep incumbent write-back disabled.

  2. WEEK 02

    Rehearse one workflow

    Review one service-order scenario and one payment/messaging workflow with the team. Use mock events first. Check balances, partial payments, duplicates, reversals, cash approval rules, and message templates.

  3. WEEK 03

    Review the live-action gates

    Check customer/device links, permissions, manual holds, adapter evidence, and rollback steps. Only consider a limited live trial after every relevant gate is signed off. Otherwise continue the mock or read-only evaluation.

  4. WEEK 04

    Review evidence and decide

    Compare the agreed sample records and payment/access evidence with your source system. Review paid-but-offline cases manually where needed. Decide together whether to extend the pilot, keep it read-only, or stop.

Readiness gates before live actions

These are acceptance requirements to prove with your team. They are not a list of completed product capabilities. Missing proof means no live cutover.

Finance
Verify the subscriber ledger, balances, invoice/renewal, payment, credit/manual-adjustment and audit history needed for the sample. Rehearse duplicate webhooks, retry, reconciliation, partial payment, cash/manual posting, and reversal correction.
Payment rules
Agree the paid threshold: a partial payment should reduce the balance without full reactivation unless the invoice or agreed threshold is satisfied. Decide whether trusted cash collection can reactivate immediately or requires finance approval. Verify one provider or a region-specific mock-to-real path.
Access safeguards
Require preview, audit, exception handling, role permissions, and rollback notes. A manual hold must block automatic reactivation until an authorized operator removes it. Verify customer/device links and enforcement profiles before considering automatic cut/reconnect.
Adapter proof
Verify the exact live access adapter for the pilot path. MikroTik direct safe actions are the first evaluation path; existing FreeRADIUS is a separate qualification. Neither is a promise of shipped automatic payment-to-access control.
Managed RADIUS guided pilot, if selected
Commercial early access requires tenant-specific onboarding, live smoke, and launch signoff. Agree primary/secondary behavior, accounting visibility, dashboard status, NAS secret handling, CoA/disconnect behavior, and emergency bypass before live traffic.
Messaging and ownership
Approve reminder, receipt, suspension, reactivation, outage, and payment-failure templates. Record source-of-truth rules and disabled write-back for incumbent systems. Name the operator who can stop the trial and execute rollback.

Out of scope

A full accounting migration, live Splynx/UISP synchronization, turnkey mobile-money clients, and unrestricted bulk router changes are not yet shipped as part of this offer. A complete technician app, ticketing suite, customer portal, and full operator copilot are not yet shipped.

Existing FreeRADIUS Status-Server probe and opt-in SQL accounting import are guided pilot. CoA/Disconnect against a real NAS, SQL/API sync, and policy write-back are not qualified. Managed RADIUS is commercial early access, not public GA or a hard SLA.

Our rollback promise

We agree the stop conditions, source of truth, named operator, and recovery steps before any live change. Keep the original export and incumbent service configuration. No bulk suspension, reactivation, or router action proceeds without a reviewed rollback plan.

If a gate fails, stop the trial, disable its write-back, and use the agreed operator recovery procedure. Reconcile the sample before resuming. This is an assisted operating commitment; one-click automated rollback is not yet shipped.

Read migration planning or compare the four approaches.

Questions before you start

Is automatic reconnection included as a shipped capability?

No. Service-policy, payment, and messaging foundations are guided pilots. Live payment-to-access automation is not yet shipped as a general product promise; a pilot must prove its exact adapter, provider, permissions, and rollback path first.

Do we have to replace our current billing system?

No. Start with an agreed export and read-only coexistence. Live Splynx and UISP adapters are not yet shipped. Your existing system keeps authority until a separately approved cutover.

Is the pilot a free trial or a fixed-price package?

Scope, onboarding responsibilities, fees, and timing are agreed during the pilot review. The public workspace plan is separate from the guided pilot scope.

Bring one customer sample. Agree one proof path.

Tell us your customer count, router model, current billing system, and payment provider.