IT OPS

Incident-resolved 'all clear' note + hotline greeting reset

When an incident closes, drafts an 'all clear' resolution note with OpenAI, posts it to the status page, and resets the hotline to its normal greeting via ElevenLabs.

CategoryIT Ops
Enginesim
Difficultybeginner
Triggerwebhook
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerIncident resolved webhookHTTP webhook
  • LogicConfirm incident was previously active
  • ActionDraft all-clear note + normal greeting script (OpenAI)OpenAI
  • ActionSynthesize standard hotline greeting (ElevenLabs)ElevenLabsElevenLabs
  • OutputPublish resolution note to status webhookHTTP webhook

What it does

Handles the closing half of an incident: it writes the resolution update customers see and swaps the hotline back from its incident message to the standard greeting, so callers stop hearing a stale outage notice.

When to use it

Use it whenever an incident is marked resolved and you need the all-clear and the hotline reset to happen together — the step teams most often forget once the fire is out.

How it works

  1. 1A status webhook (or PagerDuty resolve) fires with the incident ID and duration.
  2. 2A logic step confirms the incident was previously published as active, so resolutions for silent incidents are skipped.
  3. 3OpenAI drafts a brief resolution note summarizing impact window and current state, plus a normal-operations hotline script.
  4. 4ElevenLabs synthesizes the standard greeting audio to replace the incident message.
  5. 5The resolution note is published to the status-page webhook as the final output.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect HTTP webhookTrigger any URL on agent actions.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect ElevenLabsText-to-speech, voice cloning.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.