VIRPHONE / VOICE INFRASTRUCTURE
SOLUTIONS / MSPS / RESELLERS

Build your service on clear operating boundaries.

Plan the voice infrastructure behind a managed or resold communications service.

PARTNER OPERATING MODELILLUSTRATIVE · NOT LIVE
Your customer

Clear first point of contact

Your managed service

Provisioning + support ownership

VirPhone connection

Agreed carrier escalation

Planning illustration · service scope confirmed during review
SERVICE PERSPECTIVE

Define what your managed service owns.

The operating model

An MSP or reseller may package the service, administer customer environments and provide first-line support. The operating agreement should say which provisioning, billing and escalation tasks belong to your team and which belong to VirPhone. Clear ownership makes onboarding repeatable and reduces customer handoffs.

Start with one representative customer design. Document number assignment, user or trunk changes, incident triage and cancellation. Confirm available account tools and access permissions before advertising a workflow to end customers. A platform discussion and a hosted PBX seat purchase solve different needs.

OPERATING MODEL

Where VirPhone fits

Decide which functions your team operates and which belong in the service scope. Support, provisioning and billing need named owners.

ARCHITECTURE

Define the handoff

Connect managed customer environments through your platform or SBC. A Class 4 platform discussion is separate from buying hosted PBX seats.

  1. 01Your applications
  2. 02Your voice infrastructure
  3. 03VirPhone service
  4. 04PSTN connectivity
Conceptual call flow. The agreed interconnect design determines the production path.
INTEGRATION

Plan around your operation

Review commercial model, number lifecycle and support handoff. Confirm portal, reporting and provisioning scope.

RELEVANT SERVICES

Continue the technical review

DECISION GUIDE

What to review with your team

Review areaWhat to establish
Service modelCustomer ownership; provisioning; billing and first-line support.
Repeatable deliveryReference configuration; change process; escalation and offboarding.
Next stepShare the proposed architecture, traffic profile and required service boundary.
QUESTIONS & ANSWERS

Before the next step

What should our technical team prepare?

Customer ownership; provisioning; billing and first-line support. Include known application dependencies and the people responsible for testing.

PLATFORM PERSPECTIVE

Explore the sample operating views.

VIRPHONE / PLATFORM PREVIEWSAMPLE INTERFACE · NOT YOUR ACCOUNT

DID management

Inventory, assignment and inbound routing.

Number / marketTypeAssigned routeState
+1 212 555 0104LocalDemo trunk AAssigned
+1 305 555 0112LocalDemo trunk BAssigned
+44 · masked exampleGeographicUnassignedReview
+49 · masked exampleGeographicDemo trunk CAssigned

Traffic overview

Read outcomes alongside the traffic profile.

ASR61.8%
ACD04:36
PDD1.2 sec
CPS217
Active486
00:00HOURLY CALL ATTEMPTS · SAMPLE23:00
DestinationAttemptsASRACDCostStatus
Demo group A8,24062.1%04:42$48.20Normal
Demo group B5,18061.3%04:28$36.10Review

Carrier routing

A sample policy view, not an active configuration.

PriorityRoute groupPolicyCPS limitState
01Demo primaryQuality preference250Enabled
02Demo alternateFallback path150Standby
03Demo restrictedDestination review—Restricted
Eligible routes → Policy evaluation → Selected egress

Call detail records

Example call references and reporting fields.

Call referenceDirectionDurationOutcomeTrunk
DEMO-004812Outbound04:36AnsweredDemo trunk A
DEMO-004813Inbound02:18AnsweredDemo trunk B
DEMO-004814Outbound00:00Not answeredDemo trunk A

Sample records omit personal calling data. Actual fields and retention depend on the agreed reporting scope.

Rate management

Illustrative commercial data for comparison only.

Rate deckEffectiveBilling incrementCurrencyState
Demo deck AExample period60 / 60 secUSDSample
Demo deck BExample period30 / 6 secUSDSample
Demo deck CExample period60 / 1 secUSDSample

Not a quote or published rate deck. Confirm destination rates, increments and effective dates with sales.

SIP trunk overview

A visual inventory of connection boundaries.

TrunkDirectionCPSConcurrent limitState
Demo trunk ABidirectional250500Configured
Demo trunk BInbound100300Configured
Demo trunk COutbound50100Review
Signaling, media and authentication are agreed for each service.

Billing overview

Illustrative usage and invoice presentation.

Example invoice$1,284.60Sample billing period · USD
Voice usage
$984.60
Number services
$240.00
Other services
$60.00
DocumentPeriodAmountState
DEMO-INV-001Example month$1,284.60Sample

Illustrative amounts only. Not an account balance, invoice or offer.

Number selection

A sample workflow for selecting numbering requirements.

MarketUnited States
Number typeLocal
Area code212
Illustrative resultTypeNext step
+1 212 555 0104LocalCheck availability
+1 212 555 0116LocalReview requirements

Reserved example numbers, not purchasable inventory. This demonstration does not place orders.

Illustrative interface concept with sample data. Actual portal features, permissions and workflows are confirmed for your account.

01 / SERVICE DETAIL

Build a managed offer with clear responsibilities

MSPs and resellers need to know what they own in the customer relationship. Separate sales, provisioning, endpoint support, carrier escalation and billing before launching a voice offer. Customers should have a clear first point of contact even when a problem crosses several providers.

Decide whether your offer delivers carrier connectivity to a customer-managed system or a complete business communications service. Those are different support commitments. Document the standard configuration and the changes that require a separate review, especially when customers bring their own PBX or devices.

02 / SERVICE DETAIL

Keep margin connected to the support model

Compare recurring service charges, usage, devices and the effort required to support exceptions. A simple headline price can hide migration and operational work. Establish how service changes, additional numbers and customer departures affect both the commercial relationship and technical configuration.

Start with discuss a partner relationship. Describe the service you operate, the part of the call path you want to change and the person responsible for technical acceptance. That gives the first discussion a concrete scope.

A practical question

How should first-line support be organized?

Give the customer one clear entry point and document when your team escalates to the carrier. Preserve the call evidence across that handoff.

CONTINUE THE CONVERSATION

Shape a managed voice offer.

Clarify the customer relationship, support model and carrier handoff.

Discuss MSP Services