Help Docs

Best practices for StatusIQ

The following are the essential StatusIQ best practices:

  • Add all the features of your product as components in StatusIQ for streamlined communication. For example, you can add the API service of your product as a component in StatusIQ. Now, in case the API goes down, your subscribers can be alerted about the incident immediately.
  • Integrate StatusIQ with Site24x7 to avoid manual status updates.
  • Configure a custom domain and a custom email address to create a strong brand identity.
  • Configure a Notification Types section in Alerting Modes to provide alert flexibility. This feature will enable your customers to subscribe to notification options such as email, SMS, RSS feeds, or via calendar feeds.
  • Improve privacy and restrict access to your status pages by enabling IP restrictions or password protections.
  • Configure Widgets on your website to improve the transparency of your services. Once configured, your page visitors will be able to know the status directly from the website instead of needing to navigate to your Status Page.
  • Streamline your process for recurring incidents by utilizing the Incident Templates option to pre-fill the necessary details and send them instantly when needed.
  • Notify and keep customers informed about the root cause of an incident and the fix applied by writing and displaying a postmortem report for the incident.
  • Link your brand's identity to your emails as well as customize the content and layout using the Simple and Advanced Customize email notifications.

Was this document helpful?

Would you like to help us improve our documents? Tell us what you think we could do better.


We're sorry to hear that you're not satisfied with the document. We'd love to learn what we could do to improve the experience.


Thanks for taking the time to share your feedback. We'll use your feedback to improve our online help resources.

Shortlink has been copied!