Global incident communication must be addressed (2nd Request)

Skool is a community forum. It is not an incident reporting system. I should not have to monitor community threads daily to find out whether your platform is experiencing a global issue affecting my clients’ infrastructure.

I raised this several weeks ago and I’m raising it again because nothing has changed — and this week it cost us.

Our assistants broke. I spent hours triaging and refining prompts trying to diagnose the issue. The root cause? A global Voice KB outage — which I only discovered by scrolling through Skool posts. That is not acceptable.

Here is what needs to happen:

1. Incident notifications via official channels (email at minimum) — what broke, what’s affected, and the resolution timeline

2. A changelog and release notes page

3. A real-time status/incident dashboard that proactively pushes updates — not a static status page

These are not feature requests guys... they are foundational requirements for any major SaaS product with your size. Stripe has them. Twilio has them. Every platform that businesses depend on has them.

I want to be clear: I really respect the work going into V3, appreciate your team's hard work and persistence, and I understand development is hard. But new features mean nothing if the existing system is unstable and customers have no visibility into what’s breaking or why. We have large enterprise clients whose various internal processes run on these assistants. Silence during an outage is not an option. Guesswork is not an option. 5 star communication should be the standard, and it is not.

I’m asking for a direct response on this: is this being prioritized? What is the timeline? This cannot be a third post, and it cannot continue to be ignored.

6 comments