# Quickstart Guide

{% hint style="info" %}
**What you will have after this guide:** a verified notification channel, a team with an on-call schedule, a connected inbound integration, an active escalation policy, and a confirmed incident notification.
{% endhint %}

***

{% stepper %}
{% step %}
**Create your account**

There are two ways to get started with ITOC360:

**Invited by a teammate** If you received an invitation email from an existing ITOC360 user, click the invitation link, complete your registration, and accept the invite. You will be added to their organization automatically.

**New organization** If you are setting up a new tenant, go to <https://itoc360.app> register with your work email, and complete the onboarding steps including payment. Your organization will be created and ready to configure.

After registration, confirm your email address to activate your account.
{% endstep %}

{% step %}
**Invite your team members**

Open **Management > Organization** and invite teammates by email.

| Role       | Access                                                       |
| ---------- | ------------------------------------------------------------ |
| **Admin**  | Full access to configuration, billing, and member management |
| **Member** | Manages schedules and responds to incidents                  |
| **Viewer** | Read-only access to dashboards and incident history          |

Invited users receive an email to complete their own registration. Each member should verify their notification channels (Step 3) before going on-call.
{% endstep %}

{% step %}
**Confirm notification channels**

Each on-call engineer must add and verify at least one notification channel before they can receive alerts.

1. Go to **Management > Channels** and click **Create Channel**.
2. Select the channel type: voice call, SMS, or email.
3. Enter your contact details and complete verification:
   * **SMS / Voice:** enter the OTP sent to your phone.
   * **Email:** click the confirmation link in your inbox.

Repeat for each channel you want active. Each engineer configures their own channel preferences.

{% hint style="warning" %}
Unverified channels cannot be used in escalation policies. Complete verification before moving to the next steps.
{% endhint %}

{% content-ref url="<https://docs.itoc360.com/communication-and-shift-management/channels>" %}
<https://docs.itoc360.com/communication-and-shift-management/channels>
{% endcontent-ref %}
{% endstep %}

{% step %}
**Create your first team**

1. Go to **Management > Teams** and click **Create Team**.
2. Give your team a name (for example, "DevOps Team").
3. Add members to the team.

{% content-ref url="<https://docs.itoc360.com/communication-and-shift-management/teams>" %}
<https://docs.itoc360.com/communication-and-shift-management/teams>
{% endcontent-ref %}
{% endstep %}

{% step %}
**Set up an on-call schedule**

A schedule defines who is on-call and when. Escalation policies can reference a schedule directly to determine who to notify.

1. Go to **Management > Schedules** and click **Create Schedule**.
2. Highlight the date and time range on the calendar.
3. Assign users to the selected time range.

{% content-ref url="<https://docs.itoc360.com/communication-and-shift-management/schedules>" %}
<https://docs.itoc360.com/communication-and-shift-management/schedules>
{% endcontent-ref %}
{% endstep %}

{% step %}
**Connect an inbound integration**

A Source is the connection point between your inbound integration and ITOC360.

1. Go to **Management > Sources** and click **Create Source**.
2. Give the source a name and select your inbound integration from the provider list.
3. Copy the generated webhook URL or integration token.
4. Paste it into your inbound integration's alert notification settings.

ITOC360 will receive alerts as soon as your inbound integration fires one to that endpoint.

<details>

<summary>Supported inbound integrations</summary>

Grafana, Zabbix, Prometheus Alertmanager, Datadog, and any tool that supports outbound HTTP webhooks. Use the **Custom Webhook** option for integrations not listed.

</details>

{% content-ref url="<https://docs.itoc360.com/incidents-and-alerts/sources>" %}
<https://docs.itoc360.com/incidents-and-alerts/sources>
{% endcontent-ref %}
{% endstep %}

{% step %}
**Create an escalation policy**

An escalation policy connects your Source to your on-call team and defines what happens when an alert is not acknowledged.

1. Go to **Management > Escalations** and click **Create Escalation**.
2. Select the Source you created in Step 6.
3. Add a rule using the Visual Builder:
   * Set the **notification target**: select a user, a team, or a schedule.
   * Set the **timeout**: how long ITOC360 waits before escalating to the next level.
4. Add additional escalation levels if needed.
5. Save the policy.

{% hint style="info" %}
An alert that reaches a level with no available on-call engineer will escalate to the next level immediately. Make sure at least one level always has coverage.
{% endhint %}

{% content-ref url="<https://docs.itoc360.com/on-call-management-and-escalations/escalations>" %}
<https://docs.itoc360.com/on-call-management-and-escalations/escalations>
{% endcontent-ref %}
{% endstep %}

{% step %}
**Trigger a test alert from your inbound integration**

Send a test alert from your inbound integration using the webhook URL or integration token configured in Step 6.

1. Open **Monitoring > Alerts** — the alert should appear within a few seconds.
2. If the alert matches an active escalation policy, ITOC360 automatically creates an incident.
3. Open **Monitoring > Incidents** and confirm the incident was created.

{% hint style="info" %}
No incident created? The alert may not have matched any escalation policy. Verify that the Source selected in your escalation policy matches the Source that received the alert.
{% endhint %}
{% endstep %}

{% step %}
**Validate incident notifications**

Confirm that notifications were delivered correctly.

1. Check the notification channels you configured in Step 3.
2. Open the incident in ITOC360 and review the **Activity Log** — it shows every notification sent, the channel used, and the delivery status.

{% hint style="warning" %}
**Notifications not arriving?** Check the following:

* Channel verification status in **Management > Channels**
* Escalation policy assignment in **Management > Escalations**
* Alert routing rules on the Source detail page
  {% endhint %}

{% hint style="success" %}
If the activity log shows the notification was sent and you received it, your on-call setup is working correctly.
{% endhint %}

{% content-ref url="<https://docs.itoc360.com/communication-and-shift-management/channels>" %}
<https://docs.itoc360.com/communication-and-shift-management/channels>
{% endcontent-ref %}
{% endstep %}
{% endstepper %}

***

### 🎉 You are ready!

Your first on-call rotation is fully configured. From here you can:

<table data-view="cards"><thead><tr><th></th><th></th><th></th></tr></thead><tbody><tr><td><strong>On-call schedules</strong></td><td>Add recurrence, multi-team rotations, and shift swaps.</td><td><a href="https://docs.itoc360.com/communication-and-shift-management/schedules">schedules</a></td></tr><tr><td><strong>Sources</strong></td><td>Connect additional inbound integrations and customize alert field mapping.</td><td><a href="https://docs.itoc360.com/incidents-and-alerts/sources">sources</a></td></tr><tr><td><strong>Escalations</strong></td><td>Build multi-level escalation logic for different alert severities.</td><td><a href="https://docs.itoc360.com/on-call-management-and-escalations/escalations">escalations</a></td></tr><tr><td><strong>Alerts</strong></td><td>Monitor all incoming alerts from your integrations in real time.</td><td><a data-mention href="../incidents-and-alerts/alerts">alerts</a></td></tr><tr><td><strong>Incidents</strong></td><td>Track escalation executions and your team's response activity.</td><td><a data-mention href="../incidents-and-alerts/incidents">incidents</a></td></tr><tr><td><strong>Maintenances</strong></td><td>Suppress notifications during planned downtime or deployments.</td><td><a data-mention href="../incidents-and-alerts/maintenances">maintenances</a></td></tr><tr><td><strong>Silences</strong></td><td>Mute a specific alert fingerprint for a defined time window.</td><td><a data-mention href="../incidents-and-alerts/silences">silences</a></td></tr><tr><td><strong>Integrations</strong></td><td>Connect your monitoring, observability, and DevOps tools via webhook.</td><td><a data-mention href="../integrations">integrations</a></td></tr></tbody></table>

<br>