Why MSPs default to PagerDuty
PagerDuty has been the on-call platform for IT teams for over a decade. It's the safe choice — it's what your big-customer SRE counterpart uses, it integrates with everything, it has an audit log, an escalation policy editor, a mobile app, an SLA SDK. For an MSP that supports a mixed estate (Windows servers, Azure, AWS, third-party SaaS, plus VoIP), PagerDuty is genuinely a reasonable unifier.
The reason MSPs end up with PagerDuty on top of their 3CX monitoring is usually historical: PagerDuty was already there for the rest of the stack when 3CX got added. They wired a Slack-to-PagerDuty bridge or a webhook from their monitoring of choice, and called it good. It works.
Where it stops working for 3CX-heavy MSPs
1. The alert content is templated
When PagerDuty places a phone call, the audio is roughly: "This is PagerDuty calling. You have a high-urgency incident. The title is: Service Down. Press 1 to acknowledge, 2 to escalate." It reads the title field of whatever alert fired and stops there.
For 3CX, that means the on-call user hears "Service Down" — and now has to log into PagerDuty (or Sikurd, or the actual 3CX console) to find out which service on which instance. Sixty seconds of navigation under stress. AI voice alerting reads the structured incident content instead: "Service Down on instance Acme HQ. The service is 3CX Phone System." The next action is clear before the call ends.
2. Per-user pricing scales the wrong way for MSPs
PagerDuty Professional is $29/user/month. A 5-tech MSP pays $145/month for PagerDuty alone. A 10-tech MSP pays $290. That's the price before you pay for the 3CX monitoring underneath, which is the thing actually generating the alerts.
A purpose-built 3CX tool prices for the MSP, not the seat. Sikurd's Pro tier is $99/month flat for up to 10 users, and AI voice-call alerts are included — no separate PagerDuty bill, no per-seat math, no separate vendor relationship.
3. The webhook integration is fragile
Wiring 3CX events into PagerDuty isn't a click-to-integrate flow. You typically need: a monitoring tool that polls 3CX (because PagerDuty doesn't), a transform layer that maps 3CX alert types to PagerDuty event types, a webhook URL stored somewhere persistent, and ongoing maintenance every time 3CX changes its event shape. The plumbing cost is real, and it's usually the MSP's senior engineer keeping it alive.
4. PSA ticket creation is a second hop
A 3CX alert needs to become a PSA ticket (Autotask, ConnectWise, HaloPSA, Syncro) eventually — that's how MSPs bill and track the work. PagerDuty has Autotask + ConnectWise integrations, but they're separately configured, and the ticket gets created with PagerDuty's templated body, not the actual 3CX incident. Purpose-built tools create the ticket directly from the 3CX event with the right title, the right detail, and the right customer mapping.
Where PagerDuty still wins
1. Mixed-source on-call
If 3CX is one alerting source out of many — your on-call also fires for Azure alarms, Datadog incidents, app-level errors, customer ticket SLA breaches — then PagerDuty's strength is exactly the unification. One dashboard, one escalation policy, one phone call no matter what fired the alert. The voice script being generic is a worthwhile trade for that.
2. Mature escalation logic
PagerDuty's escalation policies handle multi-step rotations, time-of-day rules, holiday calendars, follow-the-sun handoffs. If your MSP runs a real 24×7 NOC with a rotation across timezones, the PagerDuty editor is more mature than what most purpose-built tools ship.
3. Cross-team auditability
PagerDuty's audit log is comprehensive — every acknowledgment, every escalation, every handoff. For SOC2-style audits or post-mortems, the depth is meaningful. Purpose-built MSP tools usually have audit logs too, but PagerDuty's are the gold standard.
How to decide
Two questions:
- Is 3CX more than half of what your on-call rotation handles? If yes, a purpose-built tool with native 3CX alerts + voice escalation pays for itself in cleaner alerting and lower per-seat cost.
- Does the rest of your IT estate already live in PagerDuty? If yes, don't migrate everything — add the 3CX-aware tool alongside, or feed 3CX events into PagerDuty via the monitoring tool's webhook, and accept the templated phone-call script as the trade.
What we see most often: MSPs run PagerDuty for the rest of their estate, and run a 3CX-specific tool for 3CX. The 3CX-specific tool generates the PSA ticket directly (skipping a hop through PagerDuty) and fires its own voice call for 3CX criticals. PagerDuty handles non-3CX. Two systems, clean separation, no per-seat overlap.
What AI voice alerts look like in practice
The flow on Sikurd Pro:
- A 3CX instance you connected starts failing a poll — say, the 3CX Phone System service stopped.
- Sikurd creates an Alert row + an audit log entry within 60 seconds of the failure.
- Push notification goes out to every user on the tenant (their iPhone / Android / desktop).
- PSA ticket gets created in your configured PSA (Autotask / ConnectWise / HaloPSA / Syncro) with the right customer, the right title, and the right description.
- If the alert type has voice calling enabled, an outbound call goes to the current on-call user's phone within seconds.
- The AI agent speaks the incident: "There is a service down on instance Acme HQ. The service is 3CX Phone System."
- If the alert isn't acknowledged within the escalation policy window, a second voice call goes to the next person in rotation.
The whole flow is one configuration in Sikurd's alert-routing matrix — no webhooks to maintain, no PagerDuty seat per technician, no script that breaks on the next 3CX upgrade.
Cost math, concretely
For a 5-tech MSP with 30 customer PBXes:
- PagerDuty + a separate 3CX monitoring tool: PagerDuty Pro at $29/user × 5 = $145/month, plus the monitoring tool (say $50–$100/month for an entry-level option). Total: $195–$245/month.
- Sikurd Pro alone: $99/month flat. Monitoring + push + PSA + status pages + AI voice alerts all included. Up to 10 users.
For a 10-tech MSP, the gap widens: PagerDuty alone hits $290/month. Sikurd Pro stays $99.
This isn't a knock on PagerDuty — it's a different product solving a broader problem. The math is just different when the on-call surface is concentrated on one stack.