Rotation from the schedule
The on-call schedule is synced from the operator's scheduling tool via API, scoped during planning. Each tier's current responder is resolved at call time, so a swap in the schedule changes routing without a ticket to IT.
Deployment blueprint
A phone system for a NOC that must be reachable when everything else is down.
Two colocation facilities, a 24x7 network operations centre, customers with hands-on-site requests at three in the morning and an on-call rotation across three tiers. This blueprint shows how 3CTel designs priority routing, escalation and an out-of-band contact plan for a data-centre operator.
- NOC line with priority over the support queue
- Escalation bridge and tiered on-call rotation
- Out-of-band plan when the primary path fails
Example
Incoming call+1 (416) 555-0198
Main menu9–17
11 — Appointments
22 — Renewals
33 — Billing
After hours
Reception queue90 s → Callback offered
AI receptionist
Voicemail to email
For a colocation operator, 3CTel configures a NOC line that takes priority over the general support queue, an on-call rotation across three tiers with automatic escalation, a standing escalation bridge, a customer support queue for tickets and remote-hands requests, and an out-of-band contact plan so the NOC is reachable if the facility's own connectivity fails. An AI agent takes ticket intake with severity capture and never collects credentials.
Deployment blueprint: a representative, anonymized scenario compiled from how 3CTel implements this kind of organization. No client is named and no result figures are stated; every parameter is a configuration choice we design with you.
- Sector
- Colocation and data-centre operations
- Users
- 48 (NOC, facilities, remote hands, support, account managers)
- Sites
- 2 facilities plus a small head office
- Hours
- 24x7 NOC; business-hours support and sales
- Languages
- English and French
- Modules
- Business phone, Contact Centre, SMS, call analytics
- AI agents
- Ticket intake with severity capture, after-hours support triage
- Integrations
- Ticketing and on-call scheduling via API and webhooks
Situation
A colocation operator runs two facilities with a network operations centre staffed around the clock. Customers call for three reasons: something is down, they need remote hands at a cabinet, or they have a billing or access question. The first kind of call cannot wait in a queue behind the other two.
Facilities staff and network engineers rotate on call in tiers. When the NOC cannot resolve an issue, it must reach the right tier fast and get everyone on one bridge. The operator also has to assume that a serious incident may take out the very network its phones use, so the NOC needs a contact path that does not depend on the facility.
Technology & IT Services
Support queues, on-call escalation and API-driven routing for software firms and MSPs.
Learn more: Technology & IT ServicesHigh Call Volume Teams
Queues, callbacks and analytics for teams that are always busy.
Learn more: High Call Volume TeamsContact Centre
Queues, routing and supervision for teams that live on the phone.
Learn more: Contact CentreRequirements
- A NOC line that rings ahead of every other queue and never sends a caller to voicemail while the NOC is staffed.
- A tiered on-call rotation, imported from the scheduling tool, with automatic escalation when a tier does not answer.
- A standing escalation bridge the NOC can drop responders into, with a recorded join announcement.
- A customer support queue for remote hands, access and billing, with callbacks and ticket numbers read back.
- An out-of-band contact plan: numbers that forward to mobile devices on cellular when the facility's connectivity is lost.
- AI ticket intake that captures severity, customer identifier and cabinet or circuit reference, without ever asking for passwords or access codes.
- Recording on the NOC line for incident review, with an announcement.
Call-flow design
The NOC line and the support line are separate numbers with separate queues. Callers on the support line who describe an outage are moved to the NOC queue at the front, not the back. The on-call rotation is a schedule, not a list of names, so the right engineer rings without anyone editing routing at shift change.
ExampleView all team
Business number
+1 (416) 555-0198
Main numberActive call 00:24
IN
Inbound caller
+1 (905) 555-0142
Mute
Keypad
Hold
Add
End
Transfer call
Select a team member or department
Search people or teams
- Sales teamExt. 202
- Customer supportExt. 204
Your team
RC
ReceptionExt. 201
AvailableS1
Sales 1Ext. 202
On a callS2
Sales 2Ext. 203
AvailableSD
Service deskExt. 204
AvailableOM
Office managerExt. 205
In a meetingConceptual illustration of the 3CTel interface — not a screenshot
| When | Then |
|---|---|
| A customer calls the NOC line | The NOC ring group answers immediately; the call is recorded with an announcement and tagged as priority |
| The NOC needs Tier 2 | The on-call Tier 2 engineer rings on desk and mobile for 45 seconds; unanswered, the Tier 2 backup rings; unanswered, Tier 3 and the duty manager ring together |
| A major incident is declared | The NOC opens the escalation bridge and the platform dials each responder into it; latecomers dial a fixed bridge number |
| A customer calls support during business hours | The support queue answers; remote-hands requests are logged with a ticket number read back to the caller |
| Support is closed and the caller reports an outage | The AI agent captures severity and references, and any severity marked critical is transferred live to the NOC |
| The facility loses external connectivity | Inbound numbers forward automatically to NOC mobile devices on cellular; the bridge number remains reachable from any network |
Call routing
Decide who answers, in what order, and what happens when they cannot.
Learn more: Call routingCall queue
Callers wait in order and are delivered one at a time to the next free agent.
Learn more: Call queueAfter-hours calls
A plan for every call that arrives after closing, on a weekend or on a holiday.
Learn more: After-hours callsOn-call rotation and the escalation bridge
Timed escalation
Each tier rings for a fixed number of seconds set with you, then the next responder rings. The final step always rings a manager and the NOC together so nothing ends unanswered.
Standing bridge
A fixed bridge number with a PIN is kept warm. The NOC can dial responders into it from the app, and every join and leave is time-stamped in the call log for the incident record.
SMS alongside the call
When an escalation starts, the responder receives a text with the incident reference and the bridge number, so they can join even if they missed the ring.
Business SMS
Text from the number customers already call — as a team, not from a personal phone.
Learn more: Business SMSRing group
One incoming call rings several phones at once or in sequence; the first to pick up takes it.
Learn more: Ring groupVideo Meetings
Meetings in the app you already use for calls — no second subscription.
Learn more: Video MeetingsAI agents
The AI agent handles ticket intake outside support hours and overflow within them. Its job is to capture a clean ticket and route by severity, not to troubleshoot. It follows a strict rule: it never asks for, accepts or records credentials, access codes, badge numbers or cabinet combinations. If a caller volunteers one, the AI states it cannot record it and moves on.
- Captures customer name, account or customer identifier, facility, cabinet or circuit reference, and a plain description of the issue.
- Asks the caller to rate severity in the operator's own scale and confirms the wording back.
- Critical severity is transferred live to the NOC with the transcript attached; lower severity creates a ticket via API and reads the number back.
- Answers in English or French and carries the language into any transfer.
- Anyone reporting a physical hazard at a facility, such as smoke, water or an unauthorized person, is transferred to the NOC immediately.
AI Receptionist
Answers, understands and books — in English and French.
Learn more: AI ReceptionistAI phone answering service
AI, a human service or voicemail: which should take the calls you cannot?
Learn more: AI phone answering serviceAI receptionist vs answering service
Three ways to handle calls nobody can pick up, compared without a sales pitch.
Learn more: AI receptionist vs answering serviceIntegrations
The ticketing system receives new tickets and call notes via API or webhooks; the on-call schedule is read from the scheduling tool so escalation always targets the current responder. Both connections are scoped during planning and confirmed before activation. Recording links for NOC calls are attached to the incident ticket so the post-incident review has the audio alongside the timeline.
Security, privacy and continuity
- The AI agent and support staff work from a written no-credentials rule; verification of a caller's authority for remote-hands work stays with staff and follows the operator's own procedure.
- The NOC line is recorded with an announcement configured with you; retention is set with the operator to match its incident-review practice.
- Access to recordings and call logs is by role; account managers cannot open NOC recordings.
- Out-of-band plan: designated mobile devices on cellular, a bridge number reachable from any network and a printed contact card in each NOC, reviewed with you at setup and after any change.
- Emergency calling is configured with the registered service address for each facility and the head office, and for staff working remotely.
- Outbound restrictions and per-user calling limits reduce toll-fraud exposure on a platform that is never switched off.
Trust Centre
What 3CTel commits to on 9-1-1, privacy, recording, porting and continuity, and what to ask any provider.
Learn more: Trust CentreService continuity
What happens to calls during an internet or power outage, and how failover is planned with you.
Learn more: Service continuity9-1-1 on VoIP
Why the registered address matters, how it is confirmed at setup, and how to keep it current.
Learn more: 9-1-1 on VoIPCall recording
When recording helps, how callers and staff are informed, and how access and retention are set.
Learn more: Call recordingRollout
Map the escalation
Tiers, ring times, backups and the final step are written down and agreed. The on-call schedule connection is scoped.
Build on temporary numbers
NOC line, support queue, escalation and bridge are configured and drilled: the NOC dials a test incident and each tier confirms it rang.
Connect ticketing
Ticket creation and recording links are tested with the AI agent on the temporary number before any customer hears it.
Port and switch
NOC and support numbers are ported on a date confirmed with you, outside the operator's change-freeze windows.
Drill the out-of-band plan
Connectivity is simulated as lost and the forwarding to cellular devices is confirmed. The drill is repeated on a cadence you set.
What we measure
NOC line time to answer; escalations started, the tier that answered and seconds to reach them; bridge joins per incident; support queue wait, callbacks and abandonment; AI intakes by severity and how many were transferred live; out-of-band drills completed; recordings attached to incident tickets.
How does a data-centre NOC line get priority over other calls?
The NOC line is its own number and queue, separate from support, and rings the NOC group at once. Support agents can move an outage call to the NOC queue at the front. The line is never sent to voicemail while the NOC is staffed, and unanswered rings escalate to a manager. 3CTel sets ring times and the final step with the operator.
What is an out-of-band contact plan for a data centre?
It is the way customers and responders reach the NOC when the facility's own network is down. Inbound numbers forward to designated mobile devices on cellular, the escalation bridge lives on a number reachable from any network, and a printed contact card sits in each NOC. The plan is drilled on a cadence set with the operator.
Can an AI agent take support tickets without creating a security risk?
Yes, if its scope is intake only. The AI captures identifiers, references, severity and a plain description, creates a ticket via API and transfers critical cases live. It is configured never to ask for or record credentials, codes or combinations, and it says so if a caller offers one. Verifying who is allowed to request work stays with staff.
Related pages.
Technology & IT Services
Support queues, on-call escalation and API-driven routing for software firms and MSPs.
Learn more: Technology & IT ServicesContact Centre
Queues, routing and supervision for teams that live on the phone.
Learn more: Contact CentreBusiness Phone
Reliable calling with routing your team will actually use.
Learn more: Business PhoneBusiness SMS
Text from the number customers already call — as a team, not from a personal phone.
Learn more: Business SMSService continuity
What happens to calls during an internet or power outage, and how failover is planned with you.
Learn more: Service continuityCall queue
Callers wait in order and are delivered one at a time to the next free agent.
Learn more: Call queueFrequently asked questions.
No. The current responder for each tier is read from your scheduling tool via API at call time, scoped during planning. If that connection is not available, the rotation can be maintained in the 3CTel admin portal instead.
Yes. The bridge has a fixed number and PIN reachable from any phone on any network. Responders also get an SMS with the reference and bridge number when an escalation starts.
Yes. Callers choose English or French at the greeting, and the choice carries into the queue as a skill and into the AI agent for after-hours intake.
The NOC line forwards to the designated mobile devices as part of the out-of-band plan, and the duty manager can change forwarding from the mobile app. The scenario is included in the drill.
Show us your escalation chart.
Tiers, ring times, your scheduling tool and your ticketing system are enough to design the NOC routing, the bridge and the out-of-band plan, and to quote it.