Advertisement
Australia markets closed
  • ALL ORDS

    8,153.70
    +80.10 (+0.99%)
     
  • ASX 200

    7,896.90
    +77.30 (+0.99%)
     
  • AUD/USD

    0.6509
    -0.0027 (-0.41%)
     
  • OIL

    82.64
    +1.29 (+1.59%)
     
  • GOLD

    2,235.80
    +23.10 (+1.04%)
     
  • Bitcoin AUD

    108,669.38
    -440.09 (-0.40%)
     
  • CMC Crypto 200

    885.54
    0.00 (0.00%)
     
  • AUD/EUR

    0.6020
    -0.0010 (-0.17%)
     
  • AUD/NZD

    1.0894
    +0.0014 (+0.13%)
     
  • NZX 50

    12,105.29
    +94.63 (+0.79%)
     
  • NASDAQ

    18,280.84
    +70.30 (+0.39%)
     
  • FTSE

    7,956.34
    +24.36 (+0.31%)
     
  • Dow Jones

    39,760.08
    +477.75 (+1.22%)
     
  • DAX

    18,494.26
    +17.17 (+0.09%)
     
  • Hang Seng

    16,541.42
    +148.58 (+0.91%)
     
  • NIKKEI 225

    40,168.07
    -594.66 (-1.46%)
     

Incident.io helps your team communicate better during outages

Incident.io has raised a $4.7 million funding round led by Index Ventures and Point Nine. When your company is facing an outage or a data breach, Incident.io provides the right framework to communicate about the issue — both internally and externally — and make sure it is resolved as quickly as possible.

In addition to Index Ventures and Point Nine, several business angels are also investing in the company, such as Monzo founders Tom Blomfield and Jonas Templestein, Eileen Burbidge of Passion Capital, Renaud Visage, the co-founder of Eventbrite, as well as some clients, such as Hiroki Takeuchi of GoCardless and Vinay Hiremath of Loom.

Incident.io starts with a deep integration with Slack. Many teams have to deal with multiple tools. They track an outage on one service and then talk about it with the rest of the team in Slack. That seems inefficient and leads to information disparity.

With Incident.io, everything happens in Slack. Incidents are announced in a Slack channel so that people can get notified when something happens. People can create incidents with a /incident shortcut.

ADVERTISEMENT

After that, Incident.io automatically creates a separate channel about the specific issue with the current date. Once again, you can interact with the service from the chat box in Slack or click on buttons. For instance, you can assign an issue to someone, add a summary, escalate the issue and more.

And because it’s a Slack channel, people can discuss the issue in that channel as well. This way, all information remains available in the same place. When you add people to an ongoing incident, they receive a summary from Incident.io so that they don’t have to ask unnecessary questions.

That information isn’t just restricted to Slack. Customers get their own Incident.io dashboard with a list of incidents. Each incident gets its own page with participants and a timeline of events. For instance, GitHub pull requests are automatically added to these timelines.

You can leverage this information to create a post-mortem post, share it with the team or your customers. Essentially, companies using Incident.io likely handle issues more gracefully and are more transparent about those issues. It should lead to a better experience for both team members and customers.