OpenSpan Management

Operate the AI voice estate across service apps, policy, consent, network invocation, deployment, operations and governance.

Tenant N/A Slug N/A Hosting N/A Updated N/A Services N/A

First-use setup

Configure the management entity

Complete the required operator, sign-on, staging and network gates before OpenSpan provisions the first service or routes production traffic.

Operator Local Computer Current gate Configure sign-on Setup owner Super Admin Substrate Management entity

Onboarding readiness 0 / 6 gates

Loading Jump to setup

Management entity setup

Guided configuration path for the first operator network team

Current gate Loading

Configure sign-on

Choose the operator identity provider before named people are added.

Owner Platform admin

Expected output Provider, domains and role mapping are captured.

Safety No production routing changes.

Review access model

Operator setup brief

Configure sign-on

Choose Local dev, Cognito, Entra, SAML or OIDC before named operator invitations begin.

1 / 6 gates

Ask the operator for

Capture in OpenSpan

Evidence to retain

Keep protected

Setup evidence trail

What OpenSpan has proved

Audit-backed

SIP ingress, SBC/MRF resources and media handling are inventoried before service traffic is routed.

Staging uses test numbers, approval evidence, rollback targets and explicit production gates.

Regional failover, HA posture and route health are captured before the first service is promoted.

Service provisioning journey

Guided path from catalog selection to staging validation and controlled production launch

Current stage Locked

Finish management entity setup

The first service can be provisioned after the operator profile, setup owners, staging lane and network inventory are in place.

Owner Network operations

Expected proof No production traffic touched.

Jump to setup

Staging first Test numbers, route evidence and rollback proof before live traffic.

Governed controls Policy, consent and AI assets must carry retained approval evidence.

Explicit launch Production remains at 0% until a separate promotion gate is approved.

Estate control points

Tenant-scoped operational model

Markets

0

Commercial market scope

Region sites

0

Active, standby and staging sites

Invocation rules

0

SIP, media and route policies

Policy bundles

0

Approved service guardrails

Consent profiles

0

Market-ready disclosure controls

Open incidents

0

Operational events under management

Operator lenses

Persona-level command surfaces across product, network, security, care, deployment and admin operations

Showing all estate work, posture and controls.

Product management

Catalog, lifecycle, adoption and release posture

Service fit

Catalog Market readiness Policy impact

Owns service shape, offer readiness and feature rollout confidence.

Catalog Markets

Network operations

SIP, MRF, SBC, media and regional failover posture

Route watch

Invocation Capacity HA

Owns route validation, media resources, failover paths and service health.

Network Failover

Security & fraud ops

Threat policy, consent evidence and decision audit

Guardrails

Policy Consent Evidence

Owns fraud controls, escalation policy and explainable decision proof.

Policy Evidence

Customer care ops

Containment, escalation, outcomes and customer impact

Experience

Outcomes Escalation SLA

Owns customer journey outcomes, transfer rules and care-facing exceptions.

Deployment engineering

Preflight, rollout waves, rollback and DR readiness

Change gate

Preflight Waves Rollback

Owns version movement, safe rollout, approval gates and rollback proof.

Platform admin

Roles, credentials, notifications and tenant controls

Control plane

Access Credentials Audit

Owns privileged controls, integration hygiene and tenant-wide evidence.

Operator work queue

Prioritized estate actions across alerts, incidents, approvals, rollout gates, policy and network invocation

Operator tasks will appear here as setup, approval and incident work is assigned.

Runtime quality & SLA

Service-level runtime posture from sessions, metric snapshots, SLA budgets, alerts and incidents

Runtime quality appears once a staged service produces sessions, latency and SLA signals.

Mission readiness

Cross-service posture for routes, policy, consent, AI assets, deployment and operations

Mission readiness appears once route, policy, consent, AI asset and deployment gates exist.

Service relationship map

Resolved dependencies across invocation, network resources, governance, AI assets and topology

Create the first service to show relationships between routes, policies, consent profiles, AI assets and deployments.

Market matrix

Market and environment posture across region sites, active services, governance, deployment and operations

Create a staging market and regional topology to populate the market matrix.

Deployment board

Rollout, preflight, approval, rollback and HA posture by deployed service

Create a deployment plan to populate rollout waves, preflight blockers and rollback posture.

Change calendar

Rollout windows, approvals, preflight blockers, rollback posture and customer impact

Create a deployment plan to populate service changes, hold points and rollback posture.

Governance coverage

Policy, consent, evidence, AI asset, credential and notification posture by service

Bind policy, consent, AI assets and evidence controls to a service to populate governance coverage.

Access & integration posture

Service entitlement, integration credential and notification-route readiness

Create operator roles and integration credentials to populate access posture.

Admin control plane

Entitlements, integration credentials and notification routes

Local setup team

Create the first network and deployment operators

Use this during local evaluation to model the first operator handoff without sending real identity-provider invitations.

Network email Network name Deployment email Deployment name

Persona owner team

Create the wider operator role model

Use this after the network handoff to stage product, security, care, governance and AI operations owners as local invited users. Display names default to the persona labels.

Product owner Security owner Care owner Governance owner AI ops owner

Create local operator users and review role assignments to populate the admin control plane.

Policy decision explainability

Active policy bundles, replay results, rule priorities and live runtime decision mix

Create and simulate a policy bundle to populate policy decisions.

Service catalog

Operator-generic AI voice services

Staging instance defaults

Ownership and release metadata for the first staging service

These local defaults give the first staging instance named launch owners before real operator contacts are connected.

Display name Version Owner team Operational owner Product owner SLA tier Criticality

Create the first service draft to populate the operator service catalog.

AI asset assurance

Model, prompt, evaluation and drift posture by deployed service

AI asset defaults

Model and evaluation metadata for draft AI packages

These values are attached when the first prompt, decision-policy and voice-runtime profiles are created for a staging service.

Owner team Languages Model provider Model family Risk tier Evaluation suite

Attach AI asset drafts and evaluations to a service to populate assurance posture.

Service instances

Select a deployed service to inspect workspace context

Create or select a service instance to populate the service estate.

Service workspace

Selected service view

Select a service instance to view bindings, policy, consent, deployment and operations context.

Operations resolution board

Incident, alert, runbook, runtime and SLA impact grouped for operator action

Masked caller Ingress route Decision Outcome Latency ms Ops signal

Runtime sessions, alerts and incidents will appear here once a staged service is exercised.

Alerts & incidents

Mission-critical operating signals

No alerts are currently raised for the selected operator scope.

No incidents are currently open for the selected operator scope.

Consent registry

Reusable controls across deployed services

Governance draft defaults

Policy and consent language for the first staging service

Use operator terminology here so draft policy, consent capture and retention evidence start from a recognizable control baseline.

Owner team Policy name Rule name Consent profile Policy description Default action Disclosure prompt Capture point Retention

Create a policy bundle for the first service to populate policy controls.

Create a consent profile to capture disclosure, retention and evidence obligations.

Network invocation

SIP, media, routing and failover controls

Network intake

Prepare the staging route before the first service is bound

Capture the operator network facts needed to validate OpenSpan invocation without touching production traffic.

SIP ingress SIP domain DID range SBC name SBC endpoint MRF name MRF endpoint Codec policy Failover pool Failover ref RTO

Route draft Trigger Direction

Jump to setup guide Review regional topology

SIP ingress DID range, trunk group, ingress domain and trusted headers. Pending

Media resources SBC, MRF, codec policy, recording fork and RTP handling. Pending

HA / failover Primary and standby path, RTO, trigger conditions and rollback target. Pending

Route validation Staging rule, test numbers, policy bundle and consent profile binding. Pending

Network owner runbook

Capture network inventory to activate the route validation runbook.

Invocation rules

How service traffic enters the OpenSpan orchestration layer

Create an invocation draft to populate SIP route and traffic handling controls.

Network resources

DID ranges, SIP domains, SBC paths, media resources and failover pools

Register SIP, SBC, MRF, media and failover resources to populate network inventory.

Deployment manager

Multi-region topology and rollout state

First staging release

Prepare a reversible rollout before any production promotion

Capture the rollout window, preflight evidence, approval gate and rollback target for the first service package.

Target version Topology mode Rollout strategy

Readiness owner Change window Review note

Release owner Initial traffic % Scope Promotion note

Traffic % Scope Execution note

Next traffic % Scope Advance note

Hold note

Service package Instance, target version, environment and rollout strategy. Pending

Preflight proof Route, policy, consent, AI assets and media checks. Pending

Change window Wave timing, traffic scope, customer impact and hold point. Pending

Rollback path Fallback target, approval owner and rollback evidence. Pending

HA release runbook

Create a deployment plan to activate the HA release runbook.

Create a deployment plan to populate rollout, preflight and rollback controls.

Failover readiness

Active/standby site posture, route validation, rollout gates and traffic split by service

Define active and standby topology to populate failover readiness.

Regional topology

Active, standby, rollout and readiness posture

Staging topology intake

Define where OpenSpan can safely place and fail over service traffic

Capture at least one staging site and one failover posture before service invocation is published.

Market Country Timezone Lane Primary site Standby site

Staging lane Non-production environment, test numbers and validation scope. Pending

Regional sites Primary site, traffic weight, capabilities and health owner. Pending

HA / standby Standby region, failover mode, RTO and restore path. Pending

Promotion gate Preflight checks, approval evidence and rollback target. Pending

Topology HA runbook

Capture staging sites and failover mode to activate the topology runbook.

Create primary and standby sites to populate regional site posture.

Create rollout waves and preflight checks to populate rollout readiness.

Topology matrix

HA role, traffic weight and rollout coverage by site

Define regional topology to populate HA role, traffic weight and rollout coverage.

Approval queue

Policy, deployment and rollback decisions

Policy, consent, AI asset and deployment approvals will appear here when requested.

Audit & evidence

Management command trail and retained proof

Management command events will appear here after setup or control-plane actions.

Approval, simulation, preflight and rollback proof will appear here as evidence is retained.

Management domain

v0

The management domain model will appear once the local API returns schema state.

Canonical domain events will appear as management commands are recorded.