Client: VoxPilot · AI/ML & Data · UK AI voice agent provider (45 staff)

Faster Incident Response for AI Voice Agents

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team supported VoxPilot’s Python voice agent platform, which used Twilio and WebRTC. Over four months, the client’s PagerDuty records show incident response time falling from 31 to 8 minutes. Call failures fell from 2.7% to 0.5% in Datadog.

Client and engagement facts

Client
VoxPilot
Industry
AI/ML & Data
Business context
UK AI voice agent provider (45 staff)
Delivery model
Ops support
Application
AI voice agents for contact centres
Supplied geography
UK
Company size in source
45 staff

Application stack and tools

Application stack

  • Python
  • Twilio
  • WebRTC
  • Kubernetes
  • GCP

Tools used

  • Twilio routing
  • PagerDuty
  • Datadog
  • Grafana

Why Support Was Needed

Around 40,000 daily calls depended on carrier routing, codec negotiation and speech-to-text processing. The engineers wrote a first check for each incident class and added a region fallback.

Technical Work

  • Built a Twilio region fallback runbook with one-click cutover.
  • Documented WebRTC codec negotiation checks for the on-call engineer.
  • Fixed the Python GIL bug in the STT bridge and added a stress test.

Representative Incident

A carrier outage affected calls for 22 minutes in month three. TechSupport Team handled the internal escalation and runbook steps. The client owned communication with the carrier.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Incident response31 min8 minmin4 monthsClient PagerDuty
Call failure2.7%0.5%%4 monthsClient Datadog
Voice latency P951.2 s520 msBaseline: s; Result: ms4 monthsClient Grafana

Evidence and Limitations

The four-month comparison excludes one carrier outage. Response time, call failures and p95 voice latency come from separate monitoring records.

Carrier Escalation Ownership

VoxPilot remained the carrier contact. TechSupport Team handled runbook steps and internal escalation.

Scope a Similar Engagement

Share your carrier, speech stack and who owns escalation when a region or codec starts failing. Request a support plan or explore SaaS technical support.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.