Numbers
Number resources
Bind purchased, ported, or connected numbers to workspaces, policies, and channels with provider provenance.
MobDial network
Route communications through one provider-aware control plane.
MobDial coordinates configured communications providers, routing policy, health signals, number resources, failover, and operational telemetry behind MobDial-owned workflows and APIs. Provider ownership, availability, and coverage remain explicit.
One MobDial identityRole-aware workspacesAPIs + automation
Routing control
Product workspace preview
Queue
Healthy
Provider
Ready
Fallback
Armed
Live workflow
InputConversation reaches routing policy
EvaluateQueue, skill, provider, and policy state resolved
RouteBest allowed destination selected with fallback
Execution guardrails
- Tenant-aware routes
- Provider health checks
- Policy before execution
- Audit route decisions
Multi-provider
Configure supported providers behind canonical MobDial routing and resource bindings
Policy-aware
Evaluate workspace, route, compliance, health, and destination state before execution
Observable
Keep provider choice, outcome, failure state, and reconciliation visible to operators
Failover-ready
Design fallback paths without hiding which provider ultimately carried the workload
Network control
One operating layer across the communications providers you configure.
MobDial should abstract provider complexity without pretending provider infrastructure is MobDial-owned. Routing, health, identity, policy, and reconciliation stay explicit.
Routing
Provider-aware routing
Select eligible routes using policy, provider readiness, destination, and workspace configuration.
ExploreVoice
Voice execution
Run calls through configured voice providers while preserving canonical MobDial call and conversation state.
ExploreMessaging
Messaging execution
Use configured messaging routes while keeping consent, sender, delivery, and conversation state connected.
ExploreHealth
Readiness and failover
Represent provider health and fallback state so routing decisions can fail safely and visibly.
Audit
Reconciliation and evidence
Track provider identifiers, lifecycle events, usage, and outcomes against MobDial resources.
Routing lifecycle
Resolve policy. Choose an eligible route. Reconcile the result.
Resolve the workload
Identify channel, destination, workspace, policy, number, and required capabilities.
Choose an eligible provider path
Apply configured readiness, routing, compliance, and fallback rules before execution.
Reconcile provider state
Write delivery, usage, failure, and provider identifiers back into canonical MobDial records.
Next step
Design communications routing around explicit provider truth.
Use MobDial to coordinate providers, policies, channels, and operational evidence without coupling every workflow to one carrier interface.