Build your service on clear operating boundaries.
Plan the voice infrastructure behind a managed or resold communications service.
Clear first point of contact
Provisioning + support ownership
Agreed carrier escalation
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.
Where VirPhone fits
Decide which functions your team operates and which belong in the service scope. Support, provisioning and billing need named owners.
Define the handoff
Connect managed customer environments through your platform or SBC. A Class 4 platform discussion is separate from buying hosted PBX seats.
- 01Your applications
- 02Your voice infrastructure
- 03VirPhone service
- 04PSTN connectivity
Plan around your operation
Review commercial model, number lifecycle and support handoff. Confirm portal, reporting and provisioning scope.
Continue the technical review
Voice service
Explore the relevant connection.
Explore Voice serviceInterconnect
Review signaling and media.
Explore InterconnectOnboarding
Prepare a commercial and technical inquiry.
Explore OnboardingWhat to review with your team
| Review area | What to establish |
|---|---|
| Service model | Customer ownership; provisioning; billing and first-line support. |
| Repeatable delivery | Reference configuration; change process; escalation and offboarding. |
| Next step | Share the proposed architecture, traffic profile and required service boundary. |
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.
Explore the sample operating views.
DID management
Inventory, assignment and inbound routing.
| Number / market | Type | Assigned route | State |
|---|---|---|---|
| +1 212 555 0104 | Local | Demo trunk A | Assigned |
| +1 305 555 0112 | Local | Demo trunk B | Assigned |
| +44 · masked example | Geographic | Unassigned | Review |
| +49 · masked example | Geographic | Demo trunk C | Assigned |
Traffic overview
Read outcomes alongside the traffic profile.
| Destination | Attempts | ASR | ACD | Cost | Status |
|---|---|---|---|---|---|
| Demo group A | 8,240 | 62.1% | 04:42 | $48.20 | Normal |
| Demo group B | 5,180 | 61.3% | 04:28 | $36.10 | Review |
Carrier routing
A sample policy view, not an active configuration.
| Priority | Route group | Policy | CPS limit | State |
|---|---|---|---|---|
| 01 | Demo primary | Quality preference | 250 | Enabled |
| 02 | Demo alternate | Fallback path | 150 | Standby |
| 03 | Demo restricted | Destination review | — | Restricted |
Call detail records
Example call references and reporting fields.
| Call reference | Direction | Duration | Outcome | Trunk |
|---|---|---|---|---|
| DEMO-004812 | Outbound | 04:36 | Answered | Demo trunk A |
| DEMO-004813 | Inbound | 02:18 | Answered | Demo trunk B |
| DEMO-004814 | Outbound | 00:00 | Not answered | Demo 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 deck | Effective | Billing increment | Currency | State |
|---|---|---|---|---|
| Demo deck A | Example period | 60 / 60 sec | USD | Sample |
| Demo deck B | Example period | 30 / 6 sec | USD | Sample |
| Demo deck C | Example period | 60 / 1 sec | USD | Sample |
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.
| Trunk | Direction | CPS | Concurrent limit | State |
|---|---|---|---|---|
| Demo trunk A | Bidirectional | 250 | 500 | Configured |
| Demo trunk B | Inbound | 100 | 300 | Configured |
| Demo trunk C | Outbound | 50 | 100 | Review |
Billing overview
Illustrative usage and invoice presentation.
- Voice usage
- $984.60
- Number services
- $240.00
- Other services
- $60.00
| Document | Period | Amount | State |
|---|---|---|---|
| DEMO-INV-001 | Example month | $1,284.60 | Sample |
Illustrative amounts only. Not an account balance, invoice or offer.
Number selection
A sample workflow for selecting numbering requirements.
| Illustrative result | Type | Next step |
|---|---|---|
| +1 212 555 0104 | Local | Check availability |
| +1 212 555 0116 | Local | Review 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.
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.
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.