Software Development Engineer 1 at a tech vendor with 501-1,000 employees
Real User
Top 5
Jun 2, 2026
Our main use case for Squadcast is for alerting purposes, where we have set up alerting in our prod and non-prod environment, and we are getting alerts for infra and application-level alerts into Squadcast management tool, and we manage SRE shift rotations in Squadcast. A quick specific example of how Squadcast helps with alerting or SRE shift rotations in our environment is that we have a rotation every month, so we have set up a roster inside Squadcast, and based on the roster, the person who is in the shift gets the alert notification with the help of Squadcast's roster. Our main unique use case is receiving sets of alerting and alert notifications based on the incident trigger to Squadcast. Apart from this, we have set up multiple use cases inside Squadcast, such as setting up services based on our environment, and we have integrated Squadcast with the help of webhook API with other tools like Prometheus and Grafana. We have set up deduplication rules and suppression rules, so if there's a maintenance of any tool and we know that we are getting alerts during that time frame, we have suppressed the alerts during that window with the help of Squadcast incident management tool.
Senior Software Engineer at a tech vendor with 501-1,000 employees
Real User
Top 10
May 6, 2026
My main use case for Squadcast is to handle incident production incidents that we are facing in the applications, and to assign it to the users who are the relevant use case for that particular incident. We assign that alert to that user, monitor how the alert is acknowledged, when it was acknowledged, and the resolution part as well. For instance, in recent days, we got an alert from Squadcast that the CPU of one of our applications is experiencing a sudden spike, and the application was restarted. It was a production server, so we quickly analyzed what went wrong, and due to the incident, we were able to reduce the downtime of our application and solve it on time. Squadcast helps us manage all our applications, monitor how each of our applications are working in production, and how we are triggering the alerts on time so that we can mitigate the risk. This is the major use case we use Squadcast for.
My main use case for Squadcast is alert management and incident response. I use Squadcast to get all my alerts in one place, and then I use it to send notifications to my channel. I also have on-call engineers in place so that when a particular alert is triggered, they are notified and can check what the issue is.
SRE Manager at a media company with 1-10 employees
Real User
Top 5
Mar 11, 2026
Squadcast is used as an incident management tool where alerts are received that have been configured in Alertmanager. Whenever a threshold is breached, the alert reaches Squadcast and notifications are delivered via phone calls, SMS, and email. Multiple features in Squadcast help manage incidents, including the ability to create multiple escalation policies based on microservices teams. Whenever an alert triggers, it routes to the respective microservices team, which reduces noise. Team members on shift receive notifications via phone calls repeatedly if they cannot respond over Squadcast UI, allowing them to acknowledge the alert by receiving the phone call and also receive notifications over SMS. Squadcast is used primarily as an incident management tool with different use cases across more than 10 environments. Different services have been created and integrated with Prometheus via webhook API, and escalation policies have been created based on primary and secondary on-call rotations, so the respective team receives alerts based on the hierarchy.
My main use case for Squadcast is for monitoring. In our team, we have a group of engineers and developers, so we usually schedule monitoring with Squadcast turn by turn. Each person goes to Squadcast to monitor what is happening, take a look at the logs, information, and if there is anything that needs addressing, we do it. It is mainly for monitoring and if necessary, taking action. For our use case, Squadcast has what we needed; probably they could have more, but for our use case, we got what we need. It depends on the project; I have worked with other companies that use other products too, but for this particular company where we use Squadcast, I think Squadcast was our main, our primary product for monitoring. So there was not a switch per se, but in other companies, I have worked with different, similar tools too.
Site Reliability Engineer at a tech vendor with 501-1,000 employees
Real User
Top 5
Mar 9, 2026
My main use case for Squadcast is for incident management. A specific example of how I use Squadcast for incident management is that we have set up Prometheus and Alertmanager, and from Alertmanager, we receive alerts over Squadcast whenever the threshold reaches. I have integrated Prometheus and Alertmanager using a webhook inside Squadcast, so whenever the threshold breaches for an alert, it will trigger a notification inside Squadcast via email, phone, and SMS.
Squadcast serves as our main notification channel. As a notification channel, Squadcast has significantly helped us by implementing alerts in our production system, such as alerts for disk usage, CPU spikes, or any down alerts, which we configured on Alertmanager. Regarding our main use case, we use Squadcast webhooks and recently created a status page using Squadcast, which includes SLA and escalation policies.
My main use case for Squadcast is incident management and escalating alerts to the respective team. A specific example of how I have used Squadcast for incident management and alert escalation is that we have integrated Squadcast with alerting tools such as Grafana, Prometheus, and Alertmanager. Whenever the threshold breaches, we receive the notification from Alertmanager to Squadcast using a Squadcast integrating webhook from inside the service. Once the threshold breaches, we get the alert and the notification for any issue in our system. Whenever my team receives an alert, based on the severity, they will take the required action, and if it is related to the service owner, they will escalate it to the respective service according to the microservice team escalation policy.
My main use case for Squadcast is as an incident management tool where our entire alerting system operates. We receive alerts in Squadcast and route them to different escalation policies and teams based on alert category, with each team taking appropriate action according to the alert. A specific example of how I use Squadcast for incident management involves setting an escalation policy within the alert. Whenever the alert triggers, we receive a quick call based on the escalation policy. Once we receive the call over the phone, we respond back to the Squadcast ticket. Based on the severity of the Squadcast ticket, we raise a bridge call if there is production impact. If the severity is around warning level, we take the required action accordingly. Squadcast serves as our incident management platform with our alerting system based on GitOps principles. Via Alertmanager, we receive alerts based on thresholds we have set. Once a threshold is breached, we get the alert notification from Alertmanager, which triggers to Squadcast incident via a Squadcast webhook configured in Prometheus. Based on different alert categories, we have different sets of actions for which we have set escalation policies. We also use a roster within Squadcast.
Squadcast enhances incident management by providing centralized notifications and alert escalation. Its integration capabilities and user-friendly design improve response times, impacting MTTR and MTTA positively. Organizations use Squadcast to streamline incident responses and maintain system thresholds efficiently.Squadcast is an effective platform for incident management, offering features like multiple notifications via phone, email, and SMS for quick alert responses. Escalation policies...
Our main use case for Squadcast is for alerting purposes, where we have set up alerting in our prod and non-prod environment, and we are getting alerts for infra and application-level alerts into Squadcast management tool, and we manage SRE shift rotations in Squadcast. A quick specific example of how Squadcast helps with alerting or SRE shift rotations in our environment is that we have a rotation every month, so we have set up a roster inside Squadcast, and based on the roster, the person who is in the shift gets the alert notification with the help of Squadcast's roster. Our main unique use case is receiving sets of alerting and alert notifications based on the incident trigger to Squadcast. Apart from this, we have set up multiple use cases inside Squadcast, such as setting up services based on our environment, and we have integrated Squadcast with the help of webhook API with other tools like Prometheus and Grafana. We have set up deduplication rules and suppression rules, so if there's a maintenance of any tool and we know that we are getting alerts during that time frame, we have suppressed the alerts during that window with the help of Squadcast incident management tool.
My main use case for Squadcast is to handle incident production incidents that we are facing in the applications, and to assign it to the users who are the relevant use case for that particular incident. We assign that alert to that user, monitor how the alert is acknowledged, when it was acknowledged, and the resolution part as well. For instance, in recent days, we got an alert from Squadcast that the CPU of one of our applications is experiencing a sudden spike, and the application was restarted. It was a production server, so we quickly analyzed what went wrong, and due to the incident, we were able to reduce the downtime of our application and solve it on time. Squadcast helps us manage all our applications, monitor how each of our applications are working in production, and how we are triggering the alerts on time so that we can mitigate the risk. This is the major use case we use Squadcast for.
My main use case for Squadcast is alert management and incident response. I use Squadcast to get all my alerts in one place, and then I use it to send notifications to my channel. I also have on-call engineers in place so that when a particular alert is triggered, they are notified and can check what the issue is.
Squadcast is used as an incident management tool where alerts are received that have been configured in Alertmanager. Whenever a threshold is breached, the alert reaches Squadcast and notifications are delivered via phone calls, SMS, and email. Multiple features in Squadcast help manage incidents, including the ability to create multiple escalation policies based on microservices teams. Whenever an alert triggers, it routes to the respective microservices team, which reduces noise. Team members on shift receive notifications via phone calls repeatedly if they cannot respond over Squadcast UI, allowing them to acknowledge the alert by receiving the phone call and also receive notifications over SMS. Squadcast is used primarily as an incident management tool with different use cases across more than 10 environments. Different services have been created and integrated with Prometheus via webhook API, and escalation policies have been created based on primary and secondary on-call rotations, so the respective team receives alerts based on the hierarchy.
My main use case for Squadcast is for monitoring. In our team, we have a group of engineers and developers, so we usually schedule monitoring with Squadcast turn by turn. Each person goes to Squadcast to monitor what is happening, take a look at the logs, information, and if there is anything that needs addressing, we do it. It is mainly for monitoring and if necessary, taking action. For our use case, Squadcast has what we needed; probably they could have more, but for our use case, we got what we need. It depends on the project; I have worked with other companies that use other products too, but for this particular company where we use Squadcast, I think Squadcast was our main, our primary product for monitoring. So there was not a switch per se, but in other companies, I have worked with different, similar tools too.
My main use case for Squadcast is for incident management. A specific example of how I use Squadcast for incident management is that we have set up Prometheus and Alertmanager, and from Alertmanager, we receive alerts over Squadcast whenever the threshold reaches. I have integrated Prometheus and Alertmanager using a webhook inside Squadcast, so whenever the threshold breaches for an alert, it will trigger a notification inside Squadcast via email, phone, and SMS.
Squadcast serves as our main notification channel. As a notification channel, Squadcast has significantly helped us by implementing alerts in our production system, such as alerts for disk usage, CPU spikes, or any down alerts, which we configured on Alertmanager. Regarding our main use case, we use Squadcast webhooks and recently created a status page using Squadcast, which includes SLA and escalation policies.
My main use case for Squadcast is incident management and escalating alerts to the respective team. A specific example of how I have used Squadcast for incident management and alert escalation is that we have integrated Squadcast with alerting tools such as Grafana, Prometheus, and Alertmanager. Whenever the threshold breaches, we receive the notification from Alertmanager to Squadcast using a Squadcast integrating webhook from inside the service. Once the threshold breaches, we get the alert and the notification for any issue in our system. Whenever my team receives an alert, based on the severity, they will take the required action, and if it is related to the service owner, they will escalate it to the respective service according to the microservice team escalation policy.
My main use case for Squadcast is as an incident management tool where our entire alerting system operates. We receive alerts in Squadcast and route them to different escalation policies and teams based on alert category, with each team taking appropriate action according to the alert. A specific example of how I use Squadcast for incident management involves setting an escalation policy within the alert. Whenever the alert triggers, we receive a quick call based on the escalation policy. Once we receive the call over the phone, we respond back to the Squadcast ticket. Based on the severity of the Squadcast ticket, we raise a bridge call if there is production impact. If the severity is around warning level, we take the required action accordingly. Squadcast serves as our incident management platform with our alerting system based on GitOps principles. Via Alertmanager, we receive alerts based on thresholds we have set. Once a threshold is breached, we get the alert notification from Alertmanager, which triggers to Squadcast incident via a Squadcast webhook configured in Prometheus. Based on different alert categories, we have different sets of actions for which we have set escalation policies. We also use a roster within Squadcast.