Learn how to create, customize, monitor, and notify users with Crisp Status Page.

Crisp Status Page lets you publish a public status page, monitor services and nodes, receive downtime alerts, and communicate incidents or planned maintenance to your users.

Use this guide to configure the feature end to end:

• Check requirements → confirm the plan needed for Status Page
• Create your Status Page → initialize the page and domain
• Customize your Status Page → logos, colors, and header background
• Configure monitoring → services, nodes, modes, and statuses
• Receive notifications → email, Slack, push, and Pushover
• Communicate incidents → announcements and downtime warnings

Check requirements

You can review plan availability from the Crisp Pricing page. Once your workspace is on a compatible plan, open Crisp, then go to Settings → Status Page.

Create your Status Page

Before your Status Page can be used, it must be initialized from your workspace settings.

To create your Status Page:

• Open Crisp
• Go to Settings → Status Page
• Click the initialization notice
• Follow the setup flow to choose the page name and domain

Customize your Status Page

You can customize the Status Page so it fits your brand. Open Crisp, then go to Settings → Status Page → Customize your Status Page.

Upload logos

You can customize the Header logo and Footer logo from the Status Page customization settings. SVG images are recommended because they scale better across screen sizes.

Change the main color

The main Status Page color follows your Crisp Chatbox color. If you want to change it, update your chatbox color settings first.

You can learn more in How to customize the Crisp chatbox.

Change the header background

If your chatbox uses a pattern image, the same pattern is used in the Status Page header. You can also upload a custom header background image from Customize your Status Page.

Set a custom domain

By default, Crisp provides a hosted Status Page domain such as acme.crisp.watch. You can also configure a custom domain such as status.acme.com.

Open Crisp, then go to Settings → Status Page → Setup your Status Page.

To configure a custom domain:

• Enter your desired domain in Custom domain
• Click Use this domain
• Add the displayed DNS records in your DNS provider
• Give your DNS provider a short moment to propagate the change
• Click Verify domain setup
• Check the domain again once the SSL certificate has been generated

Configure services and nodes

Crisp Status groups monitored nodes into services. A service is a group of related nodes that usually serve the same purpose, such as Websites, APIs, or Email servers.

Open Crisp, then go to Settings → Status Page → Monitored services.

To create a service and monitor a node:

• Click Add a new Service and give it a name, such as Websites
• Open the service, then click Add a new Node
• Give the node a name, such as Crisp Landing Page
• Select HTTP / TCP / ICMP service (poll mode) for a public HTTP URL
• Open the node and click Add a replica
• Enter the URL or endpoint to monitor, such as https://crisp.chat/en/
• Save the configuration, then check your public Status Page

Understand monitoring modes and statuses

Crisp Status can monitor different kinds of infrastructure, including websites, APIs, email servers, database servers, and application servers.

Monitoring modes

Available monitoring modes:

• Poll mode → monitors public HTTP/HTTPS, TCP, and ICMP services directly from Crisp
• Push mode → lets application servers report their own health to Crisp Status with a reporter library
• Local mode → monitors private or LAN nodes through a local daemon installed on your infrastructure

For push mode, read How to setup the Crisp Status Reporter library. For local mode, read How to setup the Crisp Status Local service.

Status values

A replica is the smallest monitored unit with a health status. It can be an HTTP endpoint, a TCP socket, an ICMP host, or an application report.

Crisp Status uses three statuses:

• Healthy → the replica is responding fast and is not overloaded
• Sick → the replica is slower than expected or overloaded
• Dead → the replica did not answer recent probes or stopped reporting

Configure monitoring options

You can tune the monitoring bot depending on the selected node mode.

Options for poll mode nodes

Poll mode options include:

• Number of failed-check retries → how many failed checks are retried before considering the replica dead
• Seconds after which node is dead → how long the replica can take before it is considered dead
• Seconds after which node is sick → how long the replica can take before it is considered sick

Options for push mode nodes

Push mode options include:

• Seconds after which node is dead → how long Crisp waits for the next report before considering the replica dead
• Load ratio above which node CPU is sick → CPU threshold above which the replica is considered sick
• Load ratio above which node RAM is sick → RAM usage threshold above which the replica is considered sick

Options for local mode nodes

Local mode options include:

• Number of failed-check retries → how many failed checks are retried before considering the replica dead
• Seconds after which node is dead → how long the replica can take before it is considered dead
• Seconds after which node is sick → how long the replica can take before it is considered sick

Receive downtime notifications

When a replica goes down and its status changes to dead, Crisp can notify your team through several channels. Open Crisp, then go to Settings → Status Page → Notification channels.

Email notifications

Email notifications are useful when you want downtime alerts sent to a shared or operational inbox.

To configure them, open Email (to address), enable the notifier, and enter the target email address.

Slack notifications

Slack notifications send downtime alerts to a team channel. This lets team members follow or mute the channel based on their role.

To configure them, open Slack (to channel), enable the notifier, and enter your Slack Webhook URL. Slack explains how to create one in its Incoming Webhooks documentation.

Push notifications

Push notifications send alerts to selected operators through their connected Crisp apps.

To configure them, open Push (to operators), enable the notifier, and select the operators who should be notified.

Pushover notifications

Pushover notifications send downtime alerts to your own Pushover application on the devices where it is installed.

To configure it, open Pushover (to application), enable the notifier, then add your application token and recipient keys.

Receive status change Web Hooks

When the general health of your Status Page changes, such as from healthy to dead, Crisp can send a Web Hook to your servers.

To configure a health-change Web Hook:

• Read the Web Hooks Quickstart
• Configure a Web Hook for the event namespace status:health:changed

Example payload:

{
  website_id: "",
  event: "status:health:changed",

  data: {
    "website_id": "-JzqEmX56venQuQw4YV8",
    "health": "dead",

    "nodes": [
      {
        "label": "Primary load balancers",
        "replica": "tcp://edge-3.pool.net.crisp.chat:80"
      }
    ]
  },

  timestamp: 1506985696616
}

Payload fields to review:

• health → general Status Page health, such as healthy, sick, or dead
• nodes → affected nodes; this list is empty when the Status Page returns to healthy

Publish service announcements

For planned maintenance or prolonged downtime, you can publish a service announcement on your Status Page.

Open Crisp, then go to Settings → Status Page → Configure service announcements. Click Add announcement, then write and publish the announcement.

Show downtime warnings in Crisp

When your systems go down, you can warn users before they contact support. By default, when your Status Page reports as dead for more than 3 minutes in a row, a warning appears on the Crisp Chatbox and Crisp Knowledge Base when they are used.

Find Status Page utilities

Crisp Status has two companion utilities for monitoring modes that need additional setup.

Useful Status Page resources:

• Crisp Status Reporter libraries → use them for push mode nodes; read How to setup the Crisp Status Reporter library
• Crisp Status Local service → use it for local mode nodes; read How to setup the Crisp Status Local service

Updated on: 03/05/2026