Service Health

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,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
• Feedback: Share Feedback
• Web Chat: 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.