PagerDuty

PagerDuty is incident response and on-call routing software used by operations teams to get the right person alerted when something needs attention. This isn’t a claims integration, PagerDuty is about how your organization runs ProPay itself as procured enterprise software: incident alerting for ProPay-related operational issues.

What ProPay does with PagerDuty

Where a ProPay-related issue needs a human immediately, a system status problem, or a claim recommendation flagged for urgent review, ProPay can route that alert into your existing PagerDuty on-call rotation rather than a separate notification channel your team has to watch separately.

This sits apart from ProPay’s claim-handling integrations entirely. PagerDuty doesn’t touch claim data, parts sourcing, or payment execution, it’s the layer that governs how your team accesses and monitors ProPay as a system, the same way it governs every other vendor you run PagerDuty against.

How the PagerDuty connection works

ProPay’s alerting can route into PagerDuty through a webhook integration configured during enterprise onboarding.

This is configured during enterprise onboarding rather than left to a self-serve setup, since it touches how your team authenticates or how your operations team gets alerted.

What stays in PagerDuty

PagerDuty continues to manage identity, observability, or incident routing exactly as it does for every other tool in your stack. ProPay is one more system governed by the rules you already have in PagerDuty, not a special case.

Data handling and security

ProPay is SOC 2 compliant, with both Type I and Type II audits complete, and each client runs on a company-specific instance, a property directly relevant to how access through PagerDuty is scoped, since there’s no shared environment to accidentally expose.

Every claim recommendation ProPay makes is logged with a confidence level and its supporting inputs, independent of whatever visibility PagerDuty is configured to provide, PagerDuty adds a second layer of oversight on top of an already-audited system, not a replacement for it.

Setting this up

A dedicated Forward Deployed Engineer configures the PagerDuty connection as part of enterprise onboarding, working with whoever owns identity or operations tooling on your side.

Frequently asked questions about ProPay and PagerDuty

Is PagerDuty used for claims data, like ProPay’s other integrations?

No. PagerDuty governs how your organization accesses or monitors ProPay itself; claim, parts, and payment data move through ProPay’s separate category-specific integrations.

How does ProPay connect to PagerDuty?

ProPay’s alerting can route into PagerDuty through a webhook integration configured during enterprise onboarding.

Is PagerDuty required to use ProPay?

No. PagerDuty is available for enterprise clients who want ProPay to run under their existing identity, observability, or incident management setup, it isn’t required for ProPay’s core claims functionality.