Systems involved
| System | Role |
|---|---|
| Studio terminal | SSH to SBC for live concurrent-call counts. |
| Voipmonitor / Homer | Call quality and pattern history. |
| Carrier portal (Bandwidth / Telnyx) | Contracted CIC count, change request. |
| Splynx / homegrown billing | Customer record, contract terms, billing rules. |
Microsoft Teams #voice-ops | Internal channel. |
| Gmail | Customer-facing notice and confirmation. |
| Studio Procedures | Trunk capacity expansion runbook. |
Walkthrough
Confirm exhaustion is the cause
Copilot pulls the SBC’s concurrent-call counter for the customer and the rejected-call log. Pattern is unambiguous: rejections fired the moment the counter touched the ceiling, repeatedly, across the morning.
Confirm traffic is legitimate
Pull the call pattern from Voipmonitor for the morning. Outbound calls to a normal distribution of customer-service destinations, ASR (Answer Seizure Ratio) is normal, no pumping pattern. The customer is just busier than their contract allows.
Notify the customer fast
Through Gmail, send the customer a short note: we’re seeing capacity exhaustion, your calls are being briefly rejected, here’s what we recommend (uplift your CIC), if you approve we can do it within the hour. Phone call also placed to the customer’s IT contact.
Customer approves
Customer agrees to a 25 percent uplift. The PSA opportunity is created and won; billing rules will reflect the new ceiling from the change date.
Coordinate with carrier
Through the Bandwidth connector, request the trunk uplift. The carrier confirms within 15 minutes. New CIC ceiling: 250.
Push the SBC change
SSH to the SBC. Stage the customer’s trunk’s new call-admission control limit. Approval prompt shows the diff. Push. Active calls are unaffected; new calls now succeed up to 250 concurrent.
Validate
Copilot watches the rejected-call counter for 30 minutes. Rejections drop to zero. Concurrent-call counter peaks at 217 during the lunch rush — comfortably inside the new ceiling.
Update billing
Update the customer’s billing record with the new CIC count and the effective date. The next invoice picks up the prorated change automatically.
Where Studio earns its keep
- The exhaustion and the legitimacy check happen in one workspace — the engineer is not guessing whether to expand or to investigate fraud.
- The customer hears about the issue from the carrier before it shows up in their own dashboards, which is the conversation a healthcare call-centre manager wants.
- The carrier change, the SBC change, and the billing update reference the same ticket and the same effective date.
- The seasonal memory means the next September has a proactive uplift conversation in August, not a 503 on day one.
Related
Procedures
Trunk capacity expansion runbook with tenant code as the argument.Memories and search
Save seasonal patterns so the next year is proactive.