Support expectations
Support should not end at install. A district should be able to reach help and make changes with confidence.
Issue categories
Service-affecting issues, single-device problems, configuration changes, and porting questions should each have a clear path.
Emergency support
Issues affecting 911 access or district-wide calling should be treated as urgent. Flag emergency impact clearly in your report.
Changes and moves
Adds, moves, and changes to extensions, routing, and location data should be part of ongoing support.
Outage planning
Call continuity behavior should be defined during deployment and reviewed as the district changes.
What to include when reporting an issue
Clear detail speeds up resolution. Include as much of this as you can.
- Campus and building affected
- Numbers or extensions involved
- What is happening and when it started
- Whether emergency calling is affected
- How many users or sites are impacted
- Any recent changes to the network
- Steps already tried
- The best contact for follow-up
Frequently asked questions
Straightforward answers for district technology and operations leaders reviewing their phone system.
What should I include when reporting a problem?
Include the campus and building, the affected numbers or extensions, what is happening, when it started, and whether it affects emergency calling. The more specific the detail, the faster the issue can be addressed.
What counts as an emergency support issue?
Anything affecting 911 access or calling across a whole building or district should be treated as urgent. Note clearly in your report if emergency calling is impacted.
Who handles number porting questions?
Your provider should. Include the numbers in question and the desired timing when you ask for status or scheduling.
Does support cover our phones and devices?
That depends on your agreement. Device support usually covers configuration, registration, and call routing; physical hardware repair depends on the device and warranty.
How does outage planning work?
Call continuity planning defines what happens to calls if a site loses connectivity, such as routing to mobile, alternate numbers, or voicemail. This should be set up during deployment and reviewed as needed.