Squadcast Reviews

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.

The best features Squadcast offers include the ability to get weekly and monthly reports by opening the incidents and applying filters. Additionally, you can create multiple escalation policies, create tags based on those policies, and route alerts to the respective teams. You can also suppress alerts during maintenance windows, which helps reduce noise from alerts.

The maintenance window suppression has helped my team significantly, especially in our production environment with numerous setups. If any maintenance is ongoing and the system is down, receiving down alerts during that window creates noise, risking missing genuine alerts for other production environments.

Regarding the features of Squadcast, I would like to add that we can insert notes within Squadcast alerts and share findings so that any senior person can directly review them and guide other team members.

Squadcast has impacted my organization positively by providing timely notifications through phone calls, SMS, and emails, enabling us to respond within that time range and maintain our system running.

When we receive alerts in a timely manner, we can proactively monitor our systems without downtime, maintaining system health with proper alerts. Within the time frame, we can take the necessary action to resolve those alerts, helping to delay major incidents and achieving uptime above 99.9% and 99.2%.

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.

I have been using Squadcast for around four years.

Squadcast is very stable.

Squadcast's scalability is excellent. You can scale it as per your use case.

The customer support is excellent. You can directly raise a customer ticket and have a call with the customer team to resolve queries in a minimal time span.

Positive

I previously used PagerDuty before switching to Squadcast because it offers various features such as alert suppression based on payload uniqueness and the ability to set multiple escalation policies and create tags to route alerts to the correct microservices. Cost comparison showed that Squadcast is not as expensive as PagerDuty.

I evaluated other alternatives to PagerDuty, though I cannot recall the names of the other options we reviewed.

I have seen a good return on investment. If you can resolve issues in your environment without any production incidents, it directly impacts revenue. By taking timely actions, you can address issues without revenue loss, which is definitely a return on investment.

The pricing is overall within the budget and is on a per-user basis. Increasing the number of users affects the pricing, but overall, the pricing and licensing costs fit in the budget and are not too costly considering the features provided.

I would rate Squadcast eight out of ten.

I chose that rating because if Squadcast addresses the points I have mentioned, including eliminating manual intervention for resolving alerts and enabling deduplication across services, I would rate it ten out of ten.

My advice for others looking into using Squadcast is that they should definitely consider it. You will find multiple features within budget, and it improves your system health by timely monitoring and receiving alerts. Receiving alerts leads to improvements in MTTR and MTTA, allowing you to resolve issues with minimal service impact.

I primarily use Squadcast for monitoring purposes, and alerts are received inside the incident management tool where rosters are created based on rotation schedules. Based on the rotation and escalation policies, alerts are redirected to different microservices according to the escalation policy. Additionally, the SRE roster is managed within Squadcast, which contains multiple shifts, so the roster is created according to shift timings.

Squadcast offers multiple features, including the ability to create escalation policies. When working with twenty or more teams, twenty escalation policies can be created and alerts can be routed to a particular microservice team based on the escalation policy. The shift roster of the SRE team can be managed because they work in different shifts, and their roster can be managed inside Squadcast. Alerts can be deduplicated inside Squadcast, which suppresses a lot of noise.

Deduplication is one of the multiple features inside Squadcast that helps reduce noise from false alerts. Additionally, routing and deduplication rules are available, as well as suppression rules. For example, if planned maintenance is occurring, alerts can be suppressed during that time window. Rosters can be managed, escalation policies can be created, notes can be added inside Squadcast incidents, and the tool can be integrated with numerous tools using webhook API integration.

All of the features are relied upon, but the roster is mandatory, and escalation policies are important. Squadcast's routing feature is relied upon primarily. Labels inside the alerts allow alerts to be routed to the respective microservices team based on those labels, which is something the team relies on.

Squadcast has positively impacted the organization by allowing timely receipt of alerts. Based on those alerts, notifications are received via email, SMS, and phone calls, so the SRE team responds according to the severity of the alerts. Numerous labels exist inside the incident, which allows timely actions to be taken based on the label, whether critical or warning, helping minimize downtime by responding promptly to particular incidents.

By taking timely actions on alerts, MTTR and MTTA have been improved, which minimizes downtime and allows for effective incident response.

Sometimes, while updating the escalation policies tab, Squadcast takes a lot of time, which could be improved. Most of the time when escalation policies are being updated, it takes too long, which is considered one of its drawbacks. Additionally, when adding a tag inside a Squadcast incident, there is no P0 option available; there is only P1 to P5, and it would be beneficial to have a tag related to P0 as well.

I have used Squadcast for the last five years.

Squadcast is very stable.

Squadcast is very scalable.

Squadcast has excellent customer support.

Previously, PagerDuty was used, but their UI is not user-friendly and it is costly, which is why the switch to Squadcast was made.

A significant return on investment has been seen because incidents can be tracked timely and actions can be taken that minimize downtime. On the customer side, there are financial transactions involved, and continuous downtime could result in a loss of revenue for both the client and the organization. If many transaction-related costs are encountered and a lot of downtime occurs in the production environment, it leads to definite revenue loss. Using Squadcast allows incidents to be tracked and timely actions to be taken, which minimizes downtime and leads to substantial cost savings related to revenue.

The experience with pricing, setup cost, and licensing is that it is very affordable and not as pricey as other tools. There is no cost related to setup and licensing, making it very affordable.

Other options have not been evaluated; the search for an incident management tool led to Squadcast. Numerous tools are available, but based on price perspective and use cases, Squadcast fit the organization well, which is why it was chosen.

My main use case for Squadcast is in two different ways. I use it for on-call management, whereby I'm able to schedule calls and do the escalations, as well as live call routing to agents. That is the first use case that I use Squadcast for.

Secondly, I use the enterprise incident management that gives us a preview of how our platform is, the incident that happens, and exactly how we are able to use the Terraforms and the API to see exactly anything that goes wrong in real-time.

For example, I use Squadcast to integrate with our API. Anytime the APIs are not running, Squadcast is able to provide an incident alert that the API is not running. We solve the issue before a customer can.

Another way I use Squadcast would be the reliability AI. We use the solution to have our AI run faster and resolve incidents faster without the human input.

The best features Squadcast offers for me would be the API integration. I am able to create my own solution and my own incidents using the API of Squadcast. I am able to integrate it into my existing tool so that Squadcast can run the backend.

Another feature would be the professional user interface. I am easily able to navigate what features I am looking for, the reports, and the alerts from one dashboard. For me, that is a win.

The third would be about pricing. The pricing of the solution is very affordable, at $29 per month. That is a good option for me, which has more features like alerting through SMS, through voice, and notification workflow worldwide.

The integration with our tool to get alerts is straightforward, with no headache and no complexity.

Squadcast has impacted our organization positively by reducing more time and by making sure our solution runs faster. The ability to have incident watchers that can watch incidents that happen in real-time and then give us an alert has also helped us to always resolve issues as soon as they happen. That has helped us to create a stable solution for our enterprise clients.

A few areas need improvement. For example, AI-generated incident summaries take a lot of time to be completed.

I have been using Squadcast for two years.

Squadcast is stable.

Squadcast's scalability is more scalable. It scales with the growth of my business.

The customer support is very great and very responsive.

No solution was used in the past.

It is very easy and very fine.

I purchased Squadcast through their website.

We have been able to save time around 28%.

We have seen a return on investment by 32% and fewer employees are needed because the tool has a lot of AI automation.

My experience with pricing, setup cost, and licensing was very awesome because pricing is affordable. They charge a very affordable pricing compared to features. The setup cost was more attractive.

I did not evaluate other options before choosing Squadcast.

I would give Squadcast a rating of ten out of ten.

I choose ten out of ten because it is more scalable.

Squadcast's AI capabilities are secure and the governance is positive.

Regarding Squadcast's AI capabilities, it is more reliable and easy.

If anyone is looking to solve incidents as soon as possible and to get alerts, then Squadcast is the right tool and I would recommend it.

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.

Squadcast provides numerous features, including the ability to create and add runbooks via workflow, put services in maintenance mode during maintenance, suppress alerts during scheduled maintenance from AWS, and add tags to create routes based on tags to ensure that the respective alert is automatically assigned to the appropriate team, which helps reduce noise and ensures only the responsible team receives alerts.

The tagging and routing feature in Squadcast has made the biggest difference because with 10 to 15 teams, if all team members receive the same alert, it creates noise. Thanks to the tagging feature, alerts can be directly assigned based on labels inside the alerts to respective teams so they can take timely actions on those alerts.

Runbooks can be added inside the alerts based on the workflow inside Squadcast.

Squadcast has improved MTTA and MTTR because previously, resolving issues would take time, but now alerts are received within a one-minute time frame, allowing acknowledgment and timely action. Squadcast has positively impacted the organization with its notification feature that allows receiving a call in case an alert is missed from the UI, enabling timely action, which helps in resolving issues within the minimum time frame and prevents more production issues.

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.

Squadcast has been used for the last four years.

Squadcast is very stable.

Squadcast is very scalable.

Excellent customer support is provided by the Squadcast team.

Previously, PagerDuty was used, but the switch was made to Squadcast due to the numerous features it provides.

Squadcast was purchased through the AWS Marketplace.

There is definitely a return on investment because by acknowledging alerts timely and taking prior action, downtime is avoided, which indirectly affects revenue, thus saving many costs.

The pricing, setup cost, and licensing are reasonable compared to other tools. It is also very scalable and fits well within the budget.

Before choosing Squadcast, different tools were evaluated, but compared to others, Squadcast was found to be quite reasonable with a multitude of features, which is why it was chosen.

If looking for a stable incident management tool, Squadcast is strongly recommended. The overall review rating for this product is 9.

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.

I could say a lot about the best features Squadcast offers. In our use case, the features that stand out to me the most are the alerting and incident reporting because with that, we are able to know there is an issue. We go there, take a look, and if necessary, we adjust or we fix it.

I think Squadcast helps us to build a better product because of the alerting. Squadcast helped us build a better product by improving both response time and reliability.

Response time improved by up to 50%, and reliability improved too because we are able to identify something and fix it. That improves a lot too, let us say up to 60%, because our product became more scalable.

Squadcast does the job, especially alerting, reliability, and monitoring, so we can reliably use Squadcast for those things.

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.

It is mainly for monitoring; that is how we use it.

Squadcast is stable.

I think Squadcast is scalable; I believe it is stable, scalable, and stable, but in our use case, we do not really go far in terms of scalability.

It was fine; but in our case, I do not think we have a lot of communication with customer support because it was not necessary. Most of the time, the integrations and everything was going well, so we did not have a reason to escalate any complaints. But for customer support, I would say it was good, although I do not have a lot of interaction with them personally.

Negative

This was more for evaluating options before choosing Squadcast.

It was not difficult for our team to onboard and start using Squadcast; I think it is mainly because the people involved are engineers who are used to that. So it was easy.

The learning curve for Squadcast for new team members is easy; I remember in my own case when I started using it, having not used it before, I did not find it difficult to use or even do the integration, so it was straightforward.

It was seamless how Squadcast integrates with our existing tools or systems, and we did not face any real challenges.

For collaboration during incidents, we use Slack for communication among the teams. Usually, in some cases when we receive an alert, someone responsible, like the developer, will call or most of the time go to the dashboard, take a look, investigate, and if necessary, create a ticket for that, so it depends. Mostly what we use in collaboration with Squadcast was Slack.

I think money was saved since we have seen a return on investment. Another thing is fewer employees are needed to do things because after the integration, a lot of work has been reduced; you just go there, check, monitor, and if action is needed, we take the action.

I did not do those things directly in terms of pricing, setup cost, and licensing; my manager handled those things, so I was not worried about this. My main concern was more like integration and monitoring, doing the main job, in terms of pricing, which was the responsibility of my manager and other team members.

I cannot say for sure if we purchased Squadcast through the AWS Marketplace because it was our manager that handled that part. Our part is more like integration and monitoring using it.

On a scale of 1 to 10, I would say Squadcast deserves a seven, which is my overall review rating for the product.

My advice for others looking into using Squadcast is to go ahead and use it because it is a good product.

Squadcast is a good product for monitoring, alerting, and observation. So it is a good thing, and if you have a need for that, you can go for it.

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.

The best features that Squadcast offers for our team include email, SMS, and over the phone notifications, and apart from it, we can maintain escalation policies based on different microservices teams, and we can also add route rules; for instance, if a service alert is related to Team A, we can directly route the alert to Team A, which helps in managing alerts in Squadcast. We can make the service on maintenance mode if we have any planned activities, and we can deduplicate alerts to suppress the noise by adding deduplication rules, while also being able to track activities related to alerts and adding primary analysis over Squadcast note of the particular incident.

Our team uses deduplication and routing features effectively, as deduplication is essential because during a shift if four thousand to five thousand alerts are triggering, it is a lot of noise, so to reduce that noise, we have created a deduplication rule by adding a rule in Golang, and apart from it, we have suppression rules, resulting in a lot of noise being reduced after deduplication, allowing the team to handle critical alerts by removing such noise.

Squadcast has positively impacted our organization because we are timely getting alerts, and based on those alerts, we can take the required actions, so if there is any burning security alert, we can timely act to avoid production downtime, which results in a return on investment, and there are many transactional costs involved in it, so by reducing the downtime of the system, we are able to save revenue loss from the client side.

As for specific metrics, we commit to a 99.99 SLA, and by receiving timely alerts, we have saved multiple productions, leading to significant revenue savings.

In terms of improvements for Squadcast, there are opportunities, such as having only two workflows for tagging alerts based on priority P1, P2, with our current premium plan. It would be beneficial if we had multiple workflows inside Squadcast, because after the premium package, we have an unlimited number of workflows, but for mid-sized organizations, the lower premium segment only allows two workflows, and sometimes we see slowness while making changes in escalation policies.

My advice for others looking into using Squadcast is that if someone needs an affordable incident management tool, they should definitely consider Squadcast for its low pricing and multiple features. I would rate this review a nine out of ten.

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.

The best features that Squadcast offers include notifications over phone, email, and SMS, which allow for multiple notifications helping us respond quickly to alerts if a Squadcast email is missed. I can directly set up escalation policies inside Squadcast and route alerts based on different microservices.

We manage around ten to fifteen microservices, making it easy to handle alerts based on escalation policies, where every week we have primary and secondary on-call persons. In the first five minutes, the primary receives the notification, and after ten minutes, the secondary receives it, escalating it through a hierarchy. Different services have different escalation policies, so when a specific service alert triggers, it routes to that particular escalation policy, helping suppress noise for the other team.

Squadcast includes numerous features such as the ability to suppress alerts based on maintenance windows, manage services for various environments, create different services, and use workflows where I can add tagging and attach my Confluence page, which acts as a runbook. There are also escalation policies, routing, tagging features, and the option to upload notes inside Squadcast alerts by taking a screenshot or writing down notes.

Squadcast has positively impacted our organization by providing timely acknowledgment of alerts, which improves our handling of production issues. The team can monitor alerts and take actions promptly, routing them to the respective team if application service requirements arise.

We measure the improvement via SLO inside Squadcast using MTTA and MTTR.

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.

I have been using Squadcast for the last three years.

Squadcast is very stable.

Squadcast's scalability is very good, and we can integrate multiple services inside Squadcast.

The customer support provided by Squadcast is excellent.

Positive

I have not used any other incident management tool previously, and Squadcast is the first one I have used.

My experience with pricing, setup cost, and licensing is that it is very budget-friendly with annual licensing, and there is not much setup cost involved.

My company does not have a business relationship with this vendor other than being a customer.

I have seen a return on investment with Squadcast because if any alert triggers and is taken seriously, we have severity levels based on criticality and warning, allowing us to acknowledge alerts and take timely action, directly helping to reduce production incidents impacting revenue.

Before choosing Squadcast, I evaluated multiple incident management tools, and after looking at other options, we switched to Squadcast because it is within budget and contains multiple features.

My advice for others looking into using Squadcast is that if you are looking for a scalable incident management tool, you should definitely go for Squadcast because it offers numerous features including escalation policies, routing, tagging, and note addition inside incident management, and also includes a maintenance mode with a variety of features. I would rate this product nine out of ten.

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.

Squadcast's best features include the ability to add multiple persons in a shift at the same level, along with providing webhooks to receive alerts.

Squadcast has positively impacted our organization because we are confident that we will not miss any alert or system outage, as Squadcast ensures the alert reaches the person even if the SRE person is not available.

This reliability has significantly impacted our team's response time, allowing us to redirect alerts directly to the respective microservice team owners' mobile phones, thus saving time during production alerts.

Before Squadcast, we had a larger SRE team of 18 members, which we reduced to 9 after implementing Squadcast, allowing us to utilize the remaining team in other departments.

Squadcast could enhance the UI to be more user-friendly. I also noticed a bug, though I do not recall the exact details.

I have been using Squadcast for approximately four years.

Squadcast is indeed stable.

Squadcast's scalability is good, and I have not faced any challenges in scaling it.

Squadcast's customer support is very good, as they are always ready to help whenever we experience an outage.

Negative

Before Squadcast, we were using PagerDuty for alerts, although I do not have much exposure to PagerDuty.

Regarding the webhook integration, the setup is straightforward. We created services for different regions and generated a webhook for Signoz.

I advise others looking into using Squadcast to take advantage of more features by creating escalation policies to redirect alerts to the specific service owners of the impacted service to save time.

Having used Squadcast for the last four years, I am truly familiar with it and rely on Squadcast completely for our production system and its outages. If Squadcast is down for some time, it becomes very challenging for us to check the alerts. I would rate this product an 8.

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.

The best features Squadcast offers include reports and filtration, as well as the user summary which we get at the end of the week, daily, and monthly report. That is the best thing I can see in Squadcast.

The reports and filtration features help me analyze how many alerts were triggered, how much the SLA was hit, and how much actual time my team and I took to resolve that particular issue.

The notes and the takings section in Squadcast is really nice; we can tag the users there and notify them. Another feature is about adding predefined notes so that the assigned user can review them and take necessary actions if the service owner is not available.

Squadcast has positively impacted my organization by significantly limiting production incidents compared to before; after using Squadcast, we are much more aware of particular incidents happening with the production server. I do not have the exact numbers with me, but Squadcast has helped us reduce production incidents by around 25 to 30%.

One feature I think Squadcast must improve is the message quality and call quality we get; currently, the proper message is not being clearly heard on the calls we receive. Also, the acknowledge incident beep function does not work properly and it only works some of the time.

Call quality and response acknowledgment are the major things that would enhance my experience using Squadcast.

I have been using Squadcast for four and a half years.

Squadcast is stable.

As of now, I am not facing any issues regarding the scalability of Squadcast; it is handling the number of incidents we receive very well.

I have personally never reached out to Squadcast's customer team.

Earlier, we were managing incidents manually with an internal system, which presented major challenges we resolved by using Squadcast.

My experience with pricing, setup cost, and licensing was smooth, and the pricing was genuine.

Using Squadcast, we have reduced the number of employees needed to oversee production incidents, which has saved us money and especially time, and it has helped us maintain the confidence our customers have in us.

My experience with pricing, setup cost, and licensing was smooth, and the pricing was genuine.

I did not evaluate other options for Squadcast, but perhaps the management decided to do so.

I advise others looking into using Squadcast that it is a great tool and we can totally rely on Squadcast to trigger the alert on time. I would rate Squadcast a nine on a scale of one to ten. I choose nine because it is helping us manage production incidents proactively, which has helped the organization mitigate issues earlier so our clients are not hampered anymore, and I give it a nine, not a ten, because of the improvements I mentioned earlier.

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.

The best features Squadcast offers are the great UI and the metrics I get for alerts, particularly MTTR. What I appreciate most about the UI and alert metrics is how intuitive it is. For first-time users, it is also beneficial as people are able to understand and use it easily.

Squadcast has positively impacted my organization by helping with incident management and enabling alerts to be responded to more quickly. Management has improved overall, and the people on call are now more responsive since using Squadcast.

Squadcast could be improved if the pricing could be reduced per user.

I have been using Squadcast for one year.

I have not experienced any stability issues.

I have not experienced any scalability issues.

My advice to others looking into using Squadcast is that it is a good tool for alert management and monitoring alerts.