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

# Receive your first alert in 10 minutes

> From zero to your first acknowledged incident: organization, team, service, schedule, alert source and a test alert.

This guide walks the complete product path once. By the end you will have sent a real alert, watched an incident open, been notified, and acknowledged it.

<Info>
  **Estimated time:** 10 minutes. **You need:** an aciona.me account and a terminal with `curl`. No monitoring tool is required for this test.
</Info>

<Steps>
  <Step title="Create your organization" icon="building">
    When you create your account, aciona.me asks for an organization name. It is your company's isolated space — everything you create from here belongs to it.

    If you were invited to an existing organization, skip this step.

    [Details](/en/getting-started/create-organization)
  </Step>

  <Step title="Make sure you are an active member" icon="user">
    For this first test you will be the on-call person yourself. As the creator of the organization you are already an **owner**, with every permission.

    Inviting the rest of the team can wait.

    [Details](/en/getting-started/invite-members)
  </Step>

  <Step title="Create a team" icon="users">
    Under **Teams**, create a team — say `Platform` — and add yourself as a member.

    The team is the unit of responsibility: it links services to on-call schedules.

    [Details](/en/getting-started/create-team)
  </Step>

  <Step title="Create a service" icon="server">
    Under **Services**, create a service — say `payments-api` — and set the team you just created as responsible.

    Write down the exact name: you will use it in the test alert so routing finds this service.

    [Details](/en/getting-started/create-service)
  </Step>

  <Step title="Set up an on-call schedule" icon="calendar-clock">
    Under **Schedules**, create a schedule for the team with yourself as the only participant.

    For the test, use **24x7** rotation and your team's timezone (for example `America/Sao_Paulo`). That way you are on call right now, whatever the hour.

    <Warning>
      Without an active schedule holding a valid participant, the incident is still created but has no owner — and falls back to a notification to the organization owners.
    </Warning>

    [Details](/en/getting-started/create-schedule)
  </Step>

  <Step title="Create an alert source" icon="webhook">
    Under **Alert sources**, create a source of type **Generic** named `Test`.

    On save, aciona.me shows the **webhook URL** and the **token**.

    <Warning>
      The token is shown **only once**. Copy and store it now; afterwards it can only be rotated.
    </Warning>

    [Details](/en/getting-started/create-alert-source)
  </Step>

  <Step title="Send a test alert" icon="terminal">
    Replace `<alertSourceId>` and `<sourceToken>` with the values you just copied, and set `service` to your service's exact name:

    ```bash Test alert theme={null}
    curl -X POST "https://ingress.aciona.me/webhooks/<alertSourceId>" \
      -H "Content-Type: application/json" \
      -H "X-Aciona-Token: <sourceToken>" \
      -d '{
        "externalId": "test-001",
        "title": "Latency above threshold on the payments API",
        "description": "p95 above 2s for 5 minutes",
        "severity": "critical",
        "service": "payments-api",
        "status": "firing",
        "labels": { "env": "prod", "team": "platform" },
        "url": "https://example.com/dashboard"
      }'
    ```

    The expected response is `202 Accepted`. Any other code means a configuration problem — see [Webhook returned an error](/en/troubleshooting/webhook-error).
  </Step>

  <Step title="Confirm the incident" icon="siren">
    Open **Incidents** in the dashboard. Within seconds a `critical` incident should appear with the title you sent, linked to the service, the team and you as the responder.

    Open it and read the timeline: alert received, incident created, responder notified.
  </Step>

  <Step title="Acknowledge the incident" icon="circle-check">
    Click **Acknowledge** (ACK). This records that someone is looking, moves the status to `acknowledged` and **stops automatic escalation**.

    Then resolve the incident to close the loop.
  </Step>
</Steps>

## Done. What now?

<Columns cols={2}>
  <Card title="Connect your real tool" icon="plug" horizontal href="/en/alert-sources/overview">
    Grafana, Prometheus, Datadog, CloudWatch, Zabbix or New Relic.
  </Card>

  <Card title="Invite your team" icon="user-plus" horizontal href="/en/organizations/members">
    Roles, invites and permissions.
  </Card>

  <Card title="Build the real schedule" icon="calendar-clock" horizontal href="/en/on-call/schedules">
    Weekly rotation, timezones and overrides.
  </Card>

  <Card title="Set up notifications" icon="bell" horizontal href="/en/notifications/overview">
    Mobile push, Slack and Microsoft Teams.
  </Card>
</Columns>

## Checklist

* [ ] Organization created
* [ ] Team created with at least one member
* [ ] Service created and linked to the team
* [ ] Active schedule with a participant
* [ ] Alert source created and token stored
* [ ] Test alert returned `202`
* [ ] Incident appeared in the dashboard
* [ ] Incident acknowledged