Customer Self-Service Portal

List of Feature Requests for StatusIQ / Statuspages

We think StatusIQ is really good! In conjunction with Site24x7 a perfect solution.
If we want to change from our previous Statuspage solution to StatusIQ, then we need some more features at StatusIQ.
It would be great if these things on the following list get on the roadmap.

 

GUI: Responsive Design or native App

 

For On-Call Duty – when you're on the road - the current GUI would be easier to use if a native App for iOS/Android exists or if the GUI is optimized for mobile devices.

 

Events: Incident and Maintenance Templates

 

If it becomes hectic and you do not always know what to write to the customers (subscribers), then templates can help.

 

Events: Additional Coordinator field

 

Especially for internal services it is helpful for the subscribers to know whom they can reach to in case of further questions.

An optional field for the entry of a „coordinator“ would be helpful for incidents and maintenance.

It could also be prefilled with the currently logged in user.

But should be changeable.

 

Components: Hide components from dashboard

 

If a service/component is no longer available for customers or other reasons then an option to hide a component would be helpful rather then delete.

Then we don’t losing all data for a component and we will still have data and metrics available for later reports.

 

Alerting: Third party Integrations

 

It would be very helpful for ops teams if we can also send incidents and maintenance events to Slack and Teams.

 

E-Mail: Domain White List

 

We do not want everyone to be able to subscribe, and a limitation to email domains would be helpful.

 

E-Mail: Custom E-mail signature

 

Adding your own signature to e-mails is also helpful.

 

E-Mail: Custom E-mail text for incidents and maintenance

 

Adding your own greeting text to e-mails is also helpful.

 

E-Mail: Export of all subscribers via CSV

 

Currently only an import is possible. Export as CSV for all subscribers is very helpful.

 

E-Mail: Show event logs for e-mail delivery

 

If customers say they did not receive any messages, a log would be very helpful for analyze.

Logfile should show that E-Mail was successfully sent, bounced or rejected.

 

E-Mail: Test E-mail function

 

To test sending of incident or maintenance events a test function with a custom e-mail address is very helpful.

 

E-Mail: Alerts for notification alerts

 

If you get on a blacklist or there are problems with recipients, an automatic alarm would be very helpful. For example:

 

  • Hard bounces greater than 10% of sent email within a 24 hour period.
  • Soft bounces greater than 10% of sent email within a 24 hour period.
  • Rejected email greater than 10% of sent email within a 24 hour period.

 

Reports: Uptime reports for all or specific services

 

Reports for business units or customers are very helpful in communication.

Monthly Reports for all or specific services (SLA defined) would be helpful.

Or an API exists to get all events with Start/End time, Event Typ and Event Status exists.

 

Others: Google analytics tracking for public pages

 

The integration of Google Analytics for public status pages would be very helpful for later analyses.

 

Thanks,

Torsten