People working at desks in an open-plan office
Fewer support tickets

Fewer support tickets when something breaks

Most outage tickets ask the same thing: is it you or is it me? A status page answers that once, in public, instead of in every inbox.

The problem

What an outage does to your inbox

A small fault can create a big queue, because every customer asks separately.

  • Fifty people email to ask whether you are aware of the problem.
  • The team stops fixing things to write the same reply again and again.
  • Customers who get no answer chase, which creates more tickets.
  • Staff answering the phones have no up to date line to read out.
People working at desks in an open-plan office
How Orbis Status helps

How Orbis Status takes the pressure off

The answer lives in one place, and customers can find it or have it sent to them.

A link you can share

Put the status page in your email footer, help pages and auto-replies, so customers check it first.

Status badge

Embed an SVG status badge on your website so the current state is visible without a click. See the badge and feed options.

Subscriber emails

People who subscribe hear about incidents and resolutions without having to ask. See how subscribers work.

Incident templates

Save wording for common problems, so the first update goes out quickly and sounds consistent. See how incidents work.

Atom feed and status.json

Anyone technical can follow the page in a feed reader or read a public status.json.

The incidents screen, with a form for reporting an incident and the timeline of an open one.
Sample data
Step by step

Worked example: a delayed payroll run

A fictional payroll bureau, Tidewell Payroll, has a delay that would normally bring a wave of calls.

  1. The incident is posted early

    A team member uses a saved template to post "Investigating" and sets the Payslips component to Degraded performance.

  2. The phone line points to the page

    The reception message and email auto-reply both mention the status page address.

  3. Subscribers get the news

    Customers who subscribed receive the update and the resolution by email.

  4. The team reviews the quiet

    Afterwards they compare the day with earlier incidents. Fewer people got in touch, and the history page shows why.

This is an illustration of how the features fit together, not a real customer story.

Frequently asked questions

Will it stop tickets completely?

No. It cannot promise that. It gives customers a quick place to check, which often removes the "is it down?" messages.

Do customers have to sign up?

No. Anyone can read the public page. Subscribing by email is optional and uses a confirmation step.

Can we link it from our help pages?

Yes. It is a normal web address, and you can use your own domain such as status.yourcompany.com by adding a CNAME record.

Try it with your own team

Free to start, with your own subdomain or domain. No card required.