Know issues: 
- "Status Update" didn't work.
- Some system messages are not displayed correctly

Issues

Use command "/support-chat" and chat with support! 

maximum active chats per server: 1, to open u must be manager. Bot must be Administrator.

New! - In bot support chat

- Now you need to enter hours (like 1.5) to schedule maintenance instead of a Unix timestamp.
- Added a "tutorial" (like a tip) to the /dash - "Create." 

Small update

📅 **New Maintenance Scheduling Command**  
- Added the s!schedule command for scheduling maintenance windows.  

🖥 **Improved Interface**  
- Updated the s!schedule interface

⚠️ **Incident Reporting**  
- Introduced a new "Report Incident" feature to log issues directly.  Setup via /dash

🔍 **Status Tracking Update**  
- Added the /current-status command to check the system's real-time status.  (Previously, status visibility was limited to active incident/maintenance messages.)
- Use s!new-incident to update or announce new incidents.  

This update improves maintenance management and provides clearer status transparency. Share your feedback! 🚀  

New module - maintenance

Bot has been migrated to better servers, now it works faster & stable. 

Server migration

/setup has been replaced with /dash — it’s the same but better! Use the wizard to update your settings.

New dashboard

This bot offers extra features or perks that can be unlocked through optional payments or subscriptions.

Paid Features Available

Whether the current project contains any paid features, is paid only, or is 100% free to use.

This project is free to use and contains no paywalls for core functionality.

Has Paid Features

Service Health: Your Automated Status Guardian with Precision Control  
Keep your community in the loop with Service Health, the Discord bot designed to streamline service updates, incident alerts, and maintenance management. Whether you’re handling outages, planned downtime, or routine updates, Service Health ensures your audience stays informed with **zero guesswork**.

**Have feedback?** Use `/support-chat` or [web](https://support.qq.com/products/706292),share your ideas!

---

### 🚀 Key Features  
🔹 **Role-Based Alerts**  
- Configure a dedicated **ping role** in `/dash` to notify subscribers instantly.  
- Specify an **incident channel** and an **Russian‑language role**: if a user has this role, bot interactions (e.g. subscription prompts) will appear in Russian.

🔹 **Manual Incident Control**  
- Use **`s!new-incident`** to:  
  - **Create notifications** for outages, bugs, or updates.  
  - **Manually adjust** the “Current Status” (it won’t update automatically).

🔹 **Smart Maintenance Scheduling**  
- Use **`s!schedule`** for **semi‑automated** maintenance workflows:  
  - **Pre‑alerts:** Status changes to **“Upcoming Maintenance”** when scheduled.  
  - **Auto‑start:** At the scheduled start time, status updates to **“Under Maintenance.”**  
  - **Manual end:** After the scheduled end time, status resets to **“All Operational,”** but maintenance remains active until you close it.  
- Enable subscriber feedback via `/dash` → Setup → Feedback: users can report issues during maintenance.

---

### 📝 How It Works  
1. **Initial Setup**  
   - Run `/dash` to configure:  
     - **Ping Role**: Role mentioned in all alerts.  
     - **Incident Channel**: Channel for posting updates.  
     - **Russian‑Language Role** (optional): Enables Russian prompts for role‑holders.  
     - (Optional) Link your service‑status API for full automation.  

2. **Incident Management**  
   - Type `s!new-incident` to create or update incident notifications.  
   - *Note:* “Current Status” only changes when you send a new notification.

3. **Maintenance Workflow**  
   - Type `s!schedule` to plan downtime. The bot will:  
     - Publish **“Upcoming Maintenance”** when scheduled.  
     - Switch to **“Under Maintenance”** at start time.  
     - Reset to **“All Operational”** at end time (maintenance stays active until manually resolved).

---

### ⚠️ Important Notes  
- **Status Updates:**  
  - “Current Status” auto‑updates only during maintenance windows (start/end).  
  - All other changes require `s!new-incident`.  
- **Maintenance Control:**  
  - Maintenance starts automatically but **must be ended manually**.

---

### 🛠️ Support & Customization  
- **Live Chat:** `/support-chat` (1 active chat per server; Manager permissions required)  
- **Ticket Support:** [Open a Ticket](https://zsp.freshdesk.com/support/tickets/new)  
- **Feedback:** [Share Feedback](https://support.qq.com/products/706292)  
- **Web Chat:** [mcbeinside.helpshift.com](https://mcbeinside.helpshift.com)

Streamline your status communications with Service Health—precise, role‑targeted alerts, manual control, and optional automation. Keep your community informed with confidence.

Service Health

Service status: Create/update incidents, let customers report issues. Have a web status page API? Contact support to integrate!

Voting for Service Health

Möchtest du uns unterstützen?