SRE Manager at a media company with 1-10 employees
Real User
Top 5
Mar 11, 2026
Squadcast could be improved because when multiple alerts trigger, the team currently performs manual resolution of those alerts. There should be a restriction at the team side so they cannot manually resolve those alerts, which would lead to improvements in Squadcast. Apart from that, Squadcast is working well.
I think the areas where Squadcast can be improved include the alerting, the integration part, and especially the documentation while we are integrating. The documentation and integration should be improved. I remember when we were working on the integration, the documentation was not great, and we found it difficult to understand what the document was saying in some parts. So I believe that both should be improved, especially the documentation. I do not think there are any other improvements needed for Squadcast that I have not mentioned yet, or if there are, I do not remember for now. Managing permissions and access control with Squadcast is not 100% straightforward; I remember our manager has to configure that to give access to each team member. I thought even that could be improved a little bit, but from my point of view, access control was pretty cool, and it was fine too because you are sure that you have the needed permission you need to do your job.
Site Reliability Engineer at a tech vendor with 501-1,000 employees
Real User
Top 5
Mar 9, 2026
Squadcast can be improved if we restrict the manual resolution of alerts, as currently this feature is lacking inside Squadcast. Apart from this, it is working perfectly fine, with lots of features inside Squadcast.
Senior Site Reliability Engineer at a tech vendor with 501-1,000 employees
Real User
Top 5
Jan 9, 2026
Squadcast requires improvement in that whenever team members upload notes, there is a restriction preventing them from manually resolving alerts. Alerts can only be resolved via proper signals from Alertmanager. Users should not be able to resolve incidents without manual intervention. This is a major requirement because team members sometimes resolve alerts manually, risking the resolution of critical alerts. Additionally, with multiple production environments and services, we receive multiple alerts for issues such as the same disk alert several times. To reduce this noise, we utilize suppression and need deduplication rules. Having a feature to set deduplication rules in one service applicable to other services would be a great help. Other improvements needed for Squadcast include observations I have made over the last four years, and I will convey any updates regarding improvements in the future.
Senior Site Reliability Engineer at a tech vendor with 501-1,000 employees
Real User
Top 5
Jan 8, 2026
In Squadcast, I want to note that if you want to add tagging based on P0 and P1 incidents, you cannot do that on the alert because that particular feature requires purchasing the enterprise region. The medium version only allows two workflows. Inside the workflow, you can add only one kind of priority. Additionally, there is no P0 severity tag within Squadcast. Regarding needed improvements, when creating deduplication rules, if multiple same types of alerts trigger in Squadcast due to Alertmanager and we have ten services, we need to create deduplication rules over ten services. It would be beneficial if we could add a deduplication rule in one service and have it also work for another service. This would save a lot of time.
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...
Squadcast could be improved if the pricing could be reduced per user.
Squadcast could be improved because when multiple alerts trigger, the team currently performs manual resolution of those alerts. There should be a restriction at the team side so they cannot manually resolve those alerts, which would lead to improvements in Squadcast. Apart from that, Squadcast is working well.
I think the areas where Squadcast can be improved include the alerting, the integration part, and especially the documentation while we are integrating. The documentation and integration should be improved. I remember when we were working on the integration, the documentation was not great, and we found it difficult to understand what the document was saying in some parts. So I believe that both should be improved, especially the documentation. I do not think there are any other improvements needed for Squadcast that I have not mentioned yet, or if there are, I do not remember for now. Managing permissions and access control with Squadcast is not 100% straightforward; I remember our manager has to configure that to give access to each team member. I thought even that could be improved a little bit, but from my point of view, access control was pretty cool, and it was fine too because you are sure that you have the needed permission you need to do your job.
Squadcast can be improved if we restrict the manual resolution of alerts, as currently this feature is lacking inside Squadcast. Apart from this, it is working perfectly fine, with lots of features inside Squadcast.
Squadcast could enhance the UI to be more user-friendly. I also noticed a bug, though I do not recall the exact details.
Squadcast requires improvement in that whenever team members upload notes, there is a restriction preventing them from manually resolving alerts. Alerts can only be resolved via proper signals from Alertmanager. Users should not be able to resolve incidents without manual intervention. This is a major requirement because team members sometimes resolve alerts manually, risking the resolution of critical alerts. Additionally, with multiple production environments and services, we receive multiple alerts for issues such as the same disk alert several times. To reduce this noise, we utilize suppression and need deduplication rules. Having a feature to set deduplication rules in one service applicable to other services would be a great help. Other improvements needed for Squadcast include observations I have made over the last four years, and I will convey any updates regarding improvements in the future.
In Squadcast, I want to note that if you want to add tagging based on P0 and P1 incidents, you cannot do that on the alert because that particular feature requires purchasing the enterprise region. The medium version only allows two workflows. Inside the workflow, you can add only one kind of priority. Additionally, there is no P0 severity tag within Squadcast. Regarding needed improvements, when creating deduplication rules, if multiple same types of alerts trigger in Squadcast due to Alertmanager and we have ten services, we need to create deduplication rules over ten services. It would be beneficial if we could add a deduplication rule in one service and have it also work for another service. This would save a lot of time.