Scope of Services
Describe service components (extensions, voicemail, call routing, conferencing), numbering responsibilities, feature sets, and any third-party integrations required for functionality and provisioning.
A precise agreement reduces operational disputes by defining uptime, support response times, number portability, billing cycles, and data handling responsibilities. It protects both parties during incidents and outlines migration steps and costs when service changes or ends.
These agreements are commonly completed by procurement, IT, legal, and operations teams responsible for communications infrastructure.
Describe service components (extensions, voicemail, call routing, conferencing), numbering responsibilities, feature sets, and any third-party integrations required for functionality and provisioning.
Specify uptime targets, mean time to repair, support hours, escalation procedures, credits for SLA breaches, measurement methods, and reporting frequency for performance metrics.
List recurring charges, one-time setup fees, taxes, invoicing cadence, payment terms, late fees, price increase notice periods, and accepted payment methods.
Detail call recording rules, encryption in transit and at rest, access controls, data retention, and responsibilities for protecting personal and regulated data.
Document provider support tiers, change windows, scheduled maintenance notifications, and customer responsibilities during provisioning and troubleshooting.
State contract length, renewal mechanics, early termination charges, migration assistance, porting procedures, and handover format for numbers and CDRs.
| Field | Configuration |
|---|---|
| Required Fields | Make Customer Legal Name and Effective Date mandatory |
| Signature Order | Set sign sequence: provider then customer |
| Authentication | Enable email + SMS code for signer verification |
| Attachments | Require network diagrams and carrier letters where applicable |
Use e-signature tools that accept PDF and DOCX and provide a tamper-evident audit trail for executed agreements.
| Criteria | Hosted PBX Agreement | Traditional Telecom Contract |
|---|---|---|
| Number Management | provider-managed | carrier-managed |
| Feature Set | sip, pbx features | transport-focused |
| Porting Complexity | higher, includes pbx routing | lower, carrier port only |
| Onsite Equipment | typically none | often required |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day free trial | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
Service and billing begin on the signed effective date
Monthly or annual cycles specified in billing section
Port requests often complete within 30–60 days
Typical cure period is 30 days before termination
30–90 days written notice is common
Optica adopted digital signing for vendor agreements to accelerate procurement
Martin Properties used eSign to process service contracts remotely