This free starter gives you a clean first-response baseline for investigating, identified, and resolved incident updates. It is not a full response system, but it will already read better than writing from scratch in the middle of a bad hour.
Use this in the first minutes when you know something is wrong but do not have a root cause yet.
We are investigating an issue affecting parts of the product right now. Our team is actively working on it and we will share the next update by [time]. If your workflow is blocked, reply here with the affected area so we can prioritize impact.
Use this once the affected system is known and the team is already working on a fix.
We have identified the issue affecting [system or feature]. The current impact is [plain-language impact]. We are working on mitigation now and will post the next update by [time]. If you are a paying customer handling a time-sensitive workflow, contact support so we can track account-level impact.
Use this when service is back and you need to close the loop clearly instead of going silent after recovery.
The incident affecting [system or feature] has been resolved. Service is now operating normally. We are reviewing the failure internally and will share any relevant follow-up actions if needed. If you still see issues, reply with details and timestamps so we can verify your account specifically.
The full AlertPost sprint is built for founders who do not want the next outage to turn into improvised customer messaging, reactive support replies, and ad-hoc refund decisions.