Incident management software FAQ
Answers to the questions engineering leads, SREs, security reviewers and finance teams ask before they choose IncidentBot. If your question is not here, write to [email protected].
Answers to the questions engineering leads, SREs, security reviewers and finance teams ask before they choose IncidentBot. If your question is not here, write to [email protected].
Most teams connect their first alert source, build a schedule and an escalation policy, and install the Slack app in an afternoon. Rolling out to every team takes longer because each team checks its own rotation, and that is time well spent. The steps are on how it works.
Yes. Schedules and escalation policies import from Opsgenie and PagerDuty, including overrides already on the calendar. Integrations are re-pointed in each monitoring tool, and we recommend a parallel run before cut-over. See the Opsgenie alternative and PagerDuty alternative pages.
Datadog, Prometheus Alertmanager, Grafana, CloudWatch and Sentry connect directly, and any other tool can send alerts by email or webhook.
Yes. The incident simulator runs a sample incident in your browser: alert, escalation, Slack channel, status page draft and postmortem skeleton, with no account.
By mobile push, SMS, voice, email and Slack. Each responder sets their own order and delays. Starter includes 100 SMS and voice notifications per user per month, and Team and above include unlimited SMS and voice paging under fair use.
The escalation policy moves to the next tier after its timeout, repeats if you configured repeats, and keeps going until someone acknowledges. Policy design is covered on on-call management.
Yes. Rotations, overrides, swaps, follow-the-sun hand-offs and calendar sync are part of on-call scheduling.
Paging does not depend on Slack. Push, SMS, voice and email still reach the on-call engineer, and the incident is still opened, tracked and timed in IncidentBot. When Slack returns, the incident channel picks up from the recorded timeline.
The app needs permission to create channels, invite responders, post messages and respond to the /incident command. It reads messages only in incident channels it creates or is invited to, so it can build the timeline. It does not read other channels.
Yes, on Business and Enterprise, in addition to Slack.
Yes. Starter includes one public status page, Team includes three with subscriber notifications and a custom domain, and Business includes unlimited and audience-specific pages. Details are on the status page page.
No. Stakeholder viewers are read-only and included in every plan without charge. Only responders, the people who can be on call or act on incidents, are billed.
Data is stored with encryption in transit and at rest. Enterprise customers choose data residency in the United States or the European Union when the workspace is set up. The details are on the security page.
SAML SSO and the audit log are on Business and Enterprise. SCIM provisioning, advanced roles and custom retention are on Enterprise.
Yes. Enterprise includes a data processing agreement and a completed security questionnaire. Send requests to [email protected].
No. There is no free plan. There is an interactive demo that runs a sample incident in your browser without an account. Plans are billed per responder seat, monthly or annually, and all prices are on the pricing page.
Per responder seat per month. Annual billing costs half the monthly price per seat. Stakeholder viewers are not billed. Enterprise is priced on request with annual invoicing and purchase orders.
Yes. A monthly plan can be cancelled at any time and ends with the paid period, with no further charges. An annual plan runs to the end of the paid year.
Yes. Add responders when someone joins the rotation and remove them when they leave it. Billing follows the number of responder seats on the subscription.
Run a sample incident to see the workflow, or compare the plans.
Your work email and your team size. That is all we need to set up the account.
One price per seat for alerts, on-call, Slack incidents, status page and postmortems.