| Category | Function | Share | Rank | Negative rate | Labels | Quadrant | Since September 2026 |
|---|---|---|---|---|---|---|---|
| Sales engagement platforms | Sales | 0% | 13 of 66 | 12% | 17 | accepted challenger | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. |
| Email deliverability and testing tools | Marketing | 0% | 108 of 110 | 100% | 1 | under 10 labels · led by GlockApps at 34% |
| Category | September 2026 | Now | Change | Reading | Rank |
|---|---|---|---|---|---|
| Sales engagement | 0% | 0% | =heldSince September 2026: 0% → 0%, ±0 points. Inside the 11-point floor: within noise. Read over the models both editions asked. | Within noise | Rank 8 → 13 of 66 |
| Email deliverability | 0% | 0% | newNew since September 2026: not ranked then, 0% now. | New this edition | Rank 108 of 110, unchanged |
Shares here are read over the models both editions asked, so they can differ by a point or two from the standing above, which counts every model in this edition.
The floor is 11 points of share, measured: how far the models move a leader on their own when the same questions are asked twice with nothing changed. A larger change is movement; a smaller one is noise, and both are shown. Movement is read over the twelve models both editions asked; GPT-6 Luna, Muse Glimmer 30B joined this edition and are in the standing but not yet in the comparison. How the floor is measured · The editions
| Model | First choice | Alternative | Mention | Negative | Labels |
|---|---|---|---|---|---|
| Claude Haiku 4.5 | 0 | 2 | 1 | 0 | 3 |
| GPT-5.4 mini | 0 | 0 | 1 | 0 | 1 |
| Gemini 3.5 Flash | 0 | 0 | 1 | 0 | 1 |
| Perplexity Sonar | 0 | 2 | 1 | 0 | 3 |
| Grok 4.1 Fast | 0 | 0 | 1 | 1 | 2 |
| Mistral Small | 0 | 1 | 1 | 1 | 3 |
| DeepSeek V4 Flash | 0 | 1 | 1 | 1 | 3 |
| Llama 4 Maverick | 0 | 0 | 0 | 0 | 0 |
| Qwen 3.7 Flash | 0 | 1 | 0 | 0 | 1 |
| Kimi K2 | 0 | 0 | 0 | 0 | 0 |
| GLM 4.7 FlashX | 0 | 0 | 0 | 0 | 0 |
| MiniMax M2.5 | 0 | 0 | 1 | 0 | 1 |
| GPT-6 Luna | 0 | 0 | 0 | 0 | 0 |
| Muse Glimmer 30B | 0 | 0 | 0 | 0 | 0 |
Verbatim evidence the judge attached to positive labels.
“Often positioned as a multichannel engagement tool with strong automation for outbound workflows” Perplexity Sonar · Sales engagement · comparative prompt · alternative
“For a budget-friendly option with AI-driven prospecting, consider Reply.io.” Mistral Small · Sales engagement · paraphrase prompt · alternative
“The Cost-Effective Choice: Reply.io ... Reply is a strong contender.” Qwen 3.7 Flash · Sales engagement · paraphrase prompt · alternative
“Want multichannel automation at a mid-range price? → Reply.io” DeepSeek V4 Flash · Sales engagement · comparative prompt · alternative
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.
“Avoid using Reply.io's *deliverability features* as your primary monitoring tool.” DeepSeek V4 Flash · Email deliverability · negative prompt · hard negative
“Aggressive auto-renewal ... transparency issues make it risky.” Grok 4.1 Fast · Sales engagement · negative prompt · hard negative
“Be cautious with Reply.io due to setup complexity and pricing opacity” Mistral Small · Sales engagement · negative prompt · soft negative
Citations exist only for the models that return a source list, five of the fourteen in this edition, so these counts come from 59 of the 64 answers that named Reply.io and are not a share of its labels.
235 of the 235 domain citations in answers naming Reply.io came from somebody else's page.
Pages are listed as the models cited them.
Search figures are US estimates from DataForSEO, read September 28, 2026; AI search demand is its modeled, directional estimate, not a count of queries to any assistant. The answers are this edition's. Two measurements side by side: neither is read as the cause of the other.
| Kind | Pages | Last 90 days | 2025-10 to 2026-09 | Latest | Categories named |
|---|---|---|---|---|---|
| Blog | 592 | undated | CRM, SEO | ||
| Comparison | 78 | undated | |||
| Report or ebook | 56 | undated | |||
| Webinar or virtual event | 53 | undated | |||
| Glossary or explainer | 15 | undated | |||
| Case study | 7 | undated | |||
| Template or tool | 6 | undated | |||
| Podcast or video | 4 | undated | |||
| Conference or event | 2 | undated | |||
| News or press | 1 | undated |
Every page reply.io exposes, subdomains included. Kind is read from the address and title. The last 90 days, the latest date and the twelve months count pages by when they were published, from the site's feeds, a date in the address, or the page's own publication date, read from up to a hundred of its most recently changed pages; a page that says only when it last changed is counted in its kind but not in when, so the recent counts are a floor, and a kind none of whose pages gives a publication date reads undated. An event counts as online when its address or title says so (webinar, on demand, virtual or online summit); a conference, summit, trade show, expo or roadshow that does not say so is counted as a conference or event, which on a vendor's site is mostly in person. Read September 29, 2026.
An email the morning each edition publishes: where this product moved, where it held, and by how much against the noise floor. One address, confirmed by a click; a stop link in every email.
Already following? Everything you follow, with a stop for each.
Fetched September 14, 2026. These describe the company, not the product's standing, and a claimed page can dispute any of them. · Wikidata · LinkedIn · Crunchbase
What Reply.io's own pages state, read September 28, 2026: reply.io, reply.io/pricing, reply.io/customer-stories, reply.io/integrations. A claimed page can correct any of them.
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 Reply.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 Reply.io, applied by version and listed in the change log; and a one-line description supplied by the vendor and marked as such.
A new claim receives the current edition's vendor brief for Reply.io by email, built from the raw record of the edition. It shows: