Skip to content

Use case · operations

One channel, and the timeline writes itself

Enclessa runs an incident inside a single channel: monitoring posts into it over an incoming webhook, the video call starts from the room rather than from a separate invitation, decisions are pinned as they are taken, and the work that follows becomes cards linked back to the messages that caused them. Because the alert, the conversation and the call all happen in one room, the channel is the timeline afterwards, and the postmortem is written by reading it rather than by reconstructing it from four products.

Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.

At a glance

Alerts in
An incoming webhook per channel, Slack-shaped payload
The call
Started in the room, with screen share and host controls
The record
Pins, threads, permalinks and full-text search
Follow-up
Board cards that link back to the message behind them
Room type
Managed, so the channel is searchable and exportable
Starts on
The Free plan; webhooks and boards on paid plans

The situation

Something is broken and several people need to work on it at once, at an hour when nobody is at their best. The work is mostly coordination: establishing what is happening, deciding who is doing what, and recording enough that the same failure is cheaper the second time. The technical fix is often the short part.

What goes wrong when this is spread across four products

The alert is in one place and the conversation is in another

Monitoring emails a distribution list, somebody sees it, somebody else asks about it in chat, and for the first ten minutes the most valuable activity is establishing that everybody is talking about the same event.

The call has no thread

The important decision is made out loud on a call that nothing recorded and that half the responders joined late. What is written down afterwards is whatever the person with the best memory remembers.

The timeline has to be rebuilt afterwards

A postmortem written from a chat log, a ticket, a calendar entry and somebody’s terminal scrollback is mostly archaeology, and the parts that are hardest to reconstruct are exactly the parts worth learning from.

The follow-up work drifts away from its reason

Three actions come out of the review and become tickets in another product, where they are read by people who never saw the incident and quietly deprioritised because nothing on the ticket explains why it mattered.

How Enclessa handles it

  1. Create a managed channel for incidents and give it a webhook

    Make a channel in the team that owns the service and set its mode to managed, so the room is searchable, exportable and reachable by automation. Anyone who may manage that channel can create an incoming webhook for it, which returns a URL and a secret to put into your monitoring, your deployment pipeline or your status page.

  2. Let the alert open the incident

    Monitoring posts into the channel through the webhook, authored by a bot account that is a visible member of the room. The post carries whatever your alert payload carries — title, link, fields — flattened into readable text, so the first message of the incident is the alert itself rather than somebody’s paraphrase of it.

  3. Start the call from the room

    Type /call, or start it from the channel. Everybody already in the room can join without an invitation, screen sharing is there for the person who needs to show what they are seeing, and a lobby and host controls exist for the moment somebody senior needs to join a call that has become crowded.

  4. Keep the decisions in the channel, not on the call

    Post each decision as it is taken and pin it. Use threads for the side investigations so the main channel stays a narrative rather than four conversations interleaved, and use a permalink when you need to point somebody at the exact moment something changed.

  5. Turn the follow-up into cards that remember why

    Create the follow-up work as cards on the team’s board directly from the messages that produced them. Each card keeps a link back to the channel and the message, so the person who picks it up three weeks later can read the reason rather than guess at it.

  6. Write the review by reading the room

    Search the channel by time, by author or by phrase, export what you need, and write the postmortem from a single ordered record. Nothing has to be correlated across products, because nothing happened outside the room.

Which plan this needs

The channel, the threads and the call are on every plan, including Free. Incoming webhooks, bot accounts and task boards are on the Team plan and above, so an incident channel where humans coordinate works from day one, and the alerting and follow-up half arrives when you move up. Prices and plan contents are on the pricing page.

Compare the plans

What this will not do

  • An incident channel has to be a managed room. Webhooks, bots and server-side search cannot work in an end-to-end encrypted room, because the server holds no key for one.
  • There is no incident management product here: no on-call rota, no paging, no escalation policy, no severity workflow and no status page. Enclessa is where the incident is run, not what decides who gets woken up.
  • Calls are not recorded to a downloadable file, so the call is not part of the written record. What matters has to be typed into the channel.
  • Nothing pushes events out of Enclessa. Alerts come in over a webhook; if another system needs to know an incident opened, it has to ask, or you tell it.
  • A message cannot carry a button or a form, so an integration cannot offer “acknowledge” or “escalate” as something to click.

Where the detail is

Questions

Incident response: common questions

Can I send monitoring alerts into an Enclessa channel?

Yes. Anyone who may manage a channel can create an incoming webhook for it, which returns a URL and a bearer secret. The payload follows Slack’s shape, so most monitoring tools that already post to Slack need only a new URL.

Does Enclessa have on-call scheduling or paging?

No. There is no on-call rota, no paging and no escalation policy. Enclessa is where an incident is coordinated once people are awake; deciding who to wake is a job for a dedicated tool that can post its alert into the channel.

Can we use the channel as the incident timeline?

Yes, provided the channel is a managed room. Managed channels are indexed with full-text search, can be exported, and keep pins, threads and permalinks — so the ordered record already exists without anybody maintaining one.

Are incident calls recorded?

Calls can be recorded by a host with the recording permission, but there is no downloadable recording file to attach to a postmortem. Anything that has to survive the call should be written into the channel while the call is happening.

Encrypted collaboration, hosted in Europe.

Create a workspace in a couple of minutes. It is yours at your-team.enclessa.app, hosted in the European Union, with encrypted direct messages from the first one you send.

Open beta. Free plan, no payment card to start.