Pagerduty for engineering teams on-call management

I am part of the engineering team which owns the 24/7 on-call suport for all our services in the production and we use the pagerduty to effectively manage our on-call support and define the escalation policies.
Using pagerduty its easy to notify on-call person via message and call and we liked the feature where we can define after how much duration notification should be delivered to what medium and to whom. Also its easy to override the on-call schedule for a specified duration and manage the overall team on-call schedule.
Also pagerduty integrates very well with the other software we use like mail, Slack and their Android app works seamlessly for me.

Yes, since during our service outages its the only service using which we are notified and its very critical that it has no downtime or maintenance window so that we our services are also up 24*7.

we have integrated pagerduty with Slack and it has benefited us a lot since entire team knows the operational issue we have as a team but only person who is on a on-call duty needs to do the troubleshooting realtime but team can know about all the issues asynchronously also we have intergrate it with our infra monitoring tools to provide more info and graphs/metrics for the issues.

sometime for troubleshooting a production incident we need to collaborate with different teams across the org and using pagerduty its easy to know which team member from other teams are on-call and its easy to page them and involve them in the troubleshooting process.

We use Pagerduty analytics to know how many issues we are getting for a project/team in a weekly/monthly/yearly basis and at what rate we are decreasing/increasing them and can compare it with similar industry benchmarks which are very helpful in planning and improving our operational excellance.