On-call schedules and escalation policies live in the same project as your errors, logs, monitors, and incidents. On-call is in beta: Squasher does not send texts or calls yet.
Free plan. No credit card required.
acmecheckout-apiIncidents
Search⌘ Kcheckout-api: error burst
SEV-2ResolvedTimeline
Created14:06
Monitor checkout errors failed: 41 error logs a minute.
Notification sent14:06
Posted to #incidents in Slack.
AI summary generated14:07
Squasher completed the automatic investigation.
Acknowledged14:09
Lina acknowledged the incident.
Resolved14:31
Monitor checkout errors recovered.
Example incident. On-call is in beta.
Schedules say who owns an incident at each moment. Policies say who to reach next.
Weekly rotations with members in order and a time zone, from the dashboard or the CLI.
Add layers for daily or custom-length shifts. A clear rule says which layer wins.
Hand one shift to a teammate without editing the whole schedule.
Up to 10 levels, each with schedules or people as targets, and steps with their own waits.
Each paged responder gets a high-priority inbox item. A policy step can post a page card to Teams.
When triage fails, the item goes to the person on call, and the timeline says so.
Until text and voice delivery is live, notification routes carry the incident to people.
#incidents
12SquasherAPP2:06 PM
checkout-api: error burst
Severity: SEV-2Status: Investigating
Started 4m after deploy of checkout-api@a41c
▸ Impact
Error logs on checkout-api went from 3 to 41 a minute. Checkouts return 500.
▸ Root cause
The errors began 4 minutes after checkout-api@a41c deployed. That release is the likely cause.
▸ Recommended action
Roll back a41c, or open the TypeError issue and run Create fix.
Monitor: checkout errors · Opened 2:06 PM
SquasherAPP2:31 PM
checkout-api: error burst
Severity: SEV-2Status: Resolved
Example alert.
On-call is in beta. This is the plain state of each part.
Checked against the product on 2026-10-20.
Create a schedule, write a policy, and attach it to a route.
Select On-call under Alerting, add rotation members in order, and set the time zone.
squasher on-call create --project "$SQUASHER_PROJECT_ID" \ --name Primary --timezone America/New_York --member <user-id>Add levels with schedule or person targets. Add a Teams step to post a page card.
Escalation policiesAdd an On-call escalation destination to a notification route. Keep PagerDuty on the route while paging is in beta.
Install Squasher for this project. If Squasher skills or MCP are not configured in this agent environment, run `bash <(curl -fsSL https://squasher.ai/install.sh) --agents -y`. Then read https://skills.squasher.ai/squasher-onboard/SKILL.md, map every runnable app/service/worker/frontend/agent in the repo, choose the matching Squasher SDK, log drain, OTLP, or Agent SDK path, initialize with SQUASHER_API_KEY and SQUASHER_PROJECT_ID from environment variables, send one real verification event, and report the files changed plus the verification step. Do not hardcode or reveal real API keys.
bash <(curl -fsSL https://squasher.ai/install.sh) --agents -yNot yet. On-call is in beta. Schedules, rotation layers, shift swaps, and escalation policies work, but Squasher does not send text messages or phone calls yet. Until it does, keep your paging tool and send incidents to PagerDuty from a notification route.
Through notification routes: a Slack channel, a Slack war room, Microsoft Teams, Telegram, email, a webhook, or PagerDuty. A page also puts a high-priority item in each paged responder's Squasher inbox, and a policy step can post a page card to a Microsoft Teams channel.
Each one is recorded as blocked on the page timeline, and escalation moves on to the next step. If nobody acknowledges by the end of the policy, the route's other destinations get an on-call page not acknowledged message.
When a triage run fails on an incident or an issue that is still assigned to Squasher, it is assigned to the person who is on call now. The incident timeline says so. Squasher does not notify that person; they see it in the dashboard.
No. There is no importer. Create the schedule in the dashboard or with the CLI, then add rotation layers for daily or custom-length shifts.
No. Squasher plans have no seat fees, so every responder can be on a schedule.
Start free. Invite the whole team. AI triage is included on every plan.
For side projects, evals, and internal tools.
$0/ month
No card needed. No overage charges.
Start freeIncluded
For small production apps that want one tool, not five.
$29/ month
Flat price. No per-seat fees.
Start on ProEverything in Free, plus
For product teams replacing Sentry, replay, and status tooling.
$99/ month
Flat price. No per-seat fees.
Start on TeamEverything in Pro, plus
For high-volume teams with security, procurement, and support needs.
$299/ month
Flat price. No per-seat fees.
Start on ScaleEverything in Team, plus
Need more volume, a security review, or custom terms? Get in touch.
Create one schedule and route your next incident to the person on call.
Free plan. No credit card required.
