Every category where a model named incident.io for a mid-market B2B company. Share is first choices across the direct, paraphrase, budget and scale prompts; rank is within every product named in that category.

Category	Function	Share	Rank	Negative rate	Labels	Quadrant
Incident management and on-call	IT operations and endpoint	25%	1 of 53	0%	50	accepted challenger

Movement

This is the first edition on this tier, so no move can be computed for incident.io yet. From the next edition this section shows, per buyer segment, whether its share moved by more than the measured noise floor.

By model

How each model treated incident.io across every prompt where it was named for a mid-market B2B company. Twelve models, six prompts per category.

Model	First choice	Alternative	Mention	Labels
Claude Haiku 4.5	0	2	0	2
GPT-5.4 mini	2	0	0	2
Gemini 3.5 Flash	5	0	0	5
Perplexity Sonar	2	3	0	5
Grok 4.1 Fast	2	4	0	6
Mistral Small	3	2	0	5
DeepSeek V4 Flash	2	3	1	6
Llama 4 Maverick	0	0	3	3
Qwen 3.7 Flash	0	3	0	3
Kimi K2	1	2	2	5
GLM 4.7 FlashX	0	4	1	5
MiniMax M2.5	1	2	0	3

By framing

Which of the six questions produced the naming. By model says how often; this says asked what. The first-choice count on the right carries the marks of the models that produced it.

FramingLabels by classFirst choices

Direct27 labels14

Paraphrase21 labels6

Comparative33 labels14not counted in share

Budget-constrained25 labels8

Scale-constrained14 labels6

Negative21 labels5not counted in share

First choiceAlternativeMentionNegative141 labels in all, every segment counted; 34 of the 53 first choices count toward share, since the comparative and negative framings do not. The bar is one segment per label class, to scale within the framing.

What the models said for it

Verbatim evidence the judge attached to positive labels.

“my default pick is incident.io if you want the best balance of ease of use, modern workflow automation, and strong Slack-native coordination” GPT-5.4 mini · Incidents · direct prompt · first choice

“If you want a single recommendation without more context, I'd pick incident.io for most mid-market B2B companies” Perplexity Sonar · Incidents · direct prompt · first choice

“I'd recommend starting with incident.io if you're Slack-centric, or Hyperping if you want flat-rate pricing” MiniMax M2.5 · Incidents · paraphrase prompt · first choice

“For all-in-one, modern workflows: incident.io is the most popular choice, especially for Slack-centric teams.” Mistral Small · Incidents · comparative prompt · first choice

And against it

Verbatim evidence attached to negative labels. A warning on a product with few labels is a warning; on a product with many, it is one voice among them.

No model argued against it.

Named alongside

The products named in the same answers as incident.io, over the 141 answers that named it. Took the first choice instead counts the answers where the other product was the first choice and incident.io was named but was not.

ProductSame answerTook the first choice insteadHead to head

PagerDuty132 of 14129Compare →

Rootly93 of 1414Not in the top three

Opsgenie72 of 1412Not in the top three

Jira Service Management60 of 1410Not in the top three

Better Stack53 of 1419Not in the top three

Squadcast48 of 1415Compare →

FireHydrant41 of 1410Not in the top three

Hyperping34 of 1416Not in the top three

ServiceNow33 of 1411Not in the top three

Grafana IRM30 of 1410Not in the top three

A head-to-head page exists where both products are in a category's top three. The other rows are the same fact without a page behind them, so they link to the product instead.

What carried it into the answer

The sites and pages cited by the answers that named incident.io. A fact about retrieval, not a lever on the model.

Citations exist only for the models that return a source list, four of the twelve in this edition, so these counts come from 124 of the 141 answers that named incident.io and are not a share of its labels.

Domains cited

rootly.com87

incident.ioYour site83

hyperping.com76

monday.com64

xurrent.com55

augmentcode.com52

guideflow.com38

complyjet.com36

expertinsights.com33

g2.com31

472 of the 555 domain citations in answers naming incident.io came from somebody else's page.

Pages cited

monday.com/blog/service/incident-management-software64

hyperping.com/blog/best-incident-management-tools60

augmentcode.com/tools/best-incident-management-software52

xurrent.com/blog/top-incident-management-software48

rootly.com/blog/15-best-incident-response-software-platforms-for-modern-engineering-teams-45

complyjet.com/blog/best-incident-management-software36

expertinsights.com/it-management/the-top-incident-management-software32

guideflow.com/blog/incident-management-software25

Pages are listed as the models cited them.

Names read as incident.io

What the judge wrote, as written, with how often. The vendor table decides that these count as incident.io; a claim can dispute any of them.

Incident.io 6incident.io Team 1

Is this your product?

Claim this page

Claiming is free and changes nothing in the data. A claimed page shows a verified contact who is told when each edition publishes and when incident.io's standing changes by more than the noise floor; the right to propose corrections to the vendor table, meaning names the judge wrote that should or should not read as incident.io, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.

It does not get any change to labels, shares or verdicts, any preview, or any say over which quotes appear. A verification link goes to your work email; an address at incident.io is approved on the spot, any other address is reviewed by hand.

Your name and company appear on the claimed page, or the company alone if you ask below. A title and a LinkedIn address appear there too if you give them, and are left off if you do not. Your email address is never published.