> ## Documentation Index
> Fetch the complete documentation index at: https://docs.incident.io/llms.txt
> Use this file to discover all available pages before exploring further.

# What's incident.io?

> The all-in-one platform for on-call, incident response, AI SRE and status pages.

## Getting started

Getting started with incident.io almost couldn't be easier. Pick your communications platform below and you'll be up and running in minutes.

<AccordionGroup>
  <Accordion title="Getting Started with Slack" icon="slack" iconType="brands">
    If your team uses Slack, follow our [Slack installation guide](/getting-started/installing) and start declaring and
    managing incidents directly from Slack.
  </Accordion>

  <Accordion title="Getting Started with Microsoft Teams" icon="microsoft" iconType="brands">
    If your team uses Microsoft Teams, follow our [Microsoft Teams installation
    guide](/getting-started/installing-teams) to get up and running.
  </Accordion>
</AccordionGroup>

## Products

We have four core products that work together across the incident lifecycle:

<AccordionGroup>
  <Accordion title="On-call" icon="https://mintcdn.com/incidentio-18bb4170/TNFk0n6NLlGfiDcr/icons/on-call.svg?fit=max&auto=format&n=TNFk0n6NLlGfiDcr&q=85&s=914a1d3ba304bf4682634a893aac6142" width="20" height="20" data-path="icons/on-call.svg">
    Alert routing, on-call schedules, and smart escalation paths so the right people are notified when something needs
    attention. Integrates with your existing monitoring tools. [Learn more](/on-call/getting-started)
  </Accordion>

  <Accordion title="Response" icon="https://mintcdn.com/incidentio-18bb4170/dVs5B9vdcFcyrX2T/icons/incident.svg?fit=max&auto=format&n=dVs5B9vdcFcyrX2T&q=85&s=9dae65d29dffde40fed75ccbd53f7900" width="20" height="20" data-path="icons/incident.svg">
    Declare and run incidents directly in Slack or Microsoft Teams. incident.io creates a channel, assigns roles, and
    tracks actions. AI handles the repetitive work: writing summaries, drafting status updates, and suggesting
    follow-ups. After the incident, generate postmortems, track follow-ups, and identify patterns to prevent recurrence.
    [Learn more](/incidents/declaring)
  </Accordion>

  <Accordion title="Status pages" icon="https://mintcdn.com/incidentio-18bb4170/vjmjcPGrqrI2hRlN/icons/status-page.svg?fit=max&auto=format&n=vjmjcPGrqrI2hRlN&q=85&s=c8db49c87ae6d796466130117650fde4" width="20" height="20" data-path="icons/status-page.svg">
    Keep customers and stakeholders informed during incidents. Public, private, and internal status pages that update
    automatically as your incident progresses. [Learn more](/status-pages/overview)
  </Accordion>

  <Accordion title="AI SRE" icon="https://mintcdn.com/incidentio-18bb4170/CMzKlCodQQCOljYC/icons/ai-sre.svg?fit=max&auto=format&n=CMzKlCodQQCOljYC&q=85&s=133b1891a8d34fda7eed5fea0066d6a5" width="20" height="20" data-path="icons/ai-sre.svg">
    An AI teammate that investigates incidents alongside your engineers. AI SRE automatically finds problematic code
    changes, queries your observability tools, and suggests causes directly in your incident channel — so your team can
    resolve issues faster. **Coming soon**
  </Accordion>
</AccordionGroup>

## Migrating from another tool

Already using an on-call or incident management tool? We've got guides to help you move across.

<AccordionGroup>
  <Accordion title="Migrating from PagerDuty" icon="https://mintcdn.com/incidentio-18bb4170/DH5ZgM9gtjvWKAzh/icons/integrations/pagerduty-mono.svg?fit=max&auto=format&n=DH5ZgM9gtjvWKAzh&q=85&s=23b4c426751d608a8da0b84cd6678f7f" width="20" height="20" data-path="icons/integrations/pagerduty-mono.svg">
    Follow our [PagerDuty migration guide](/getting-started/migrate-from-pagerduty) to bring your schedules, escalation
    policies, and services across to incident.io.
  </Accordion>

  <Accordion title="Migrating from Opsgenie" icon="https://mintcdn.com/incidentio-18bb4170/DH5ZgM9gtjvWKAzh/icons/integrations/opsgenie-mono.svg?fit=max&auto=format&n=DH5ZgM9gtjvWKAzh&q=85&s=5b570bcf7febc9fd6bc440b1c58f5704" width="20" height="20" data-path="icons/integrations/opsgenie-mono.svg">
    Follow our [Opsgenie migration guide](/getting-started/migrate-from-opsgenie) to move your on-call configuration
    over to incident.io.
  </Accordion>
</AccordionGroup>