On-call and incident management # Schedule your engineers and track the response to every alert. Acktide connects team schedules, engineer acknowledgment and incident reviews. These features are included in Free, Enterprise and Cloud. [Try it with your service ↗](https://app.acktide.com/signup) [Choose your deployment](https://acktide.com/en/pricing.html) Before an incident ## On call, on schedule. ### Rotations and time zones Choose the engineers, start time and rotation interval. Schedules account for time zones and working days. ### Cover for time off Assign a temporary override for the required period. Preview who is on call at a selected time. ### Services and ownership Link a service to its owner, runbook and escalation policy. Alerts reach the people who know the system. During an incident ## No response? Move to the next step. An escalation policy can combine named engineers and the people currently on call. Set a wait time for each step. Acknowledging, resolving or snoozing an alert stops steps that have not yet started. The alert card shows what the engineer did, beyond whether a notification was sent. - **Primary on-call engineer**Receives the notification and acknowledges the incident. - **Backup engineer or team**Receives the alert after the configured delay if nobody responds. - **Further steps**Up to 10 steps and 3 repeats of the chain. If a schedule has no coverage, the system flags the problem and uses a fallback route to active administrators. After the response ## Review incidents and plan improvements. ### Discuss the alert Comments keep the context beside the alert, with an author and timestamp. ### Reviews and follow-up tasks Record the impact, cause and resolution. Assign follow-up tasks with owners and due dates. ### Built-in analytics Dashboards and reports show acknowledgment and resolution times by service, team and engineer. Median and p95 values help you find delays and work on reducing MTTR. Time to ACK starts when Acktide receives the event. Resolution time starts at the incident start time reported by the source. Reports show median and p95 values. Available history depends on the configured retention period. ### Data for your own reports JSON API `/v1/metrics` returns summary metrics for alerts, delivery and ACK. `/v1/reports` provides reports by service, team or owner over a period of 1 to 365 days. For CSV output, add `format=csv`. Access requires authentication to your workspace. ## Test the full cycle Create a schedule for one service, add a backup escalation step and send a test alert. Check escalation without ACK, acknowledgment from the phone and closure after recovery. Then save a short incident review. [Create a trial account](https://app.acktide.com/signup) [Delivery test protocol →](https://acktide.com/en/delivery-check.html)