The headline numbers
- 1,123,059 AI sales replies sent since launch. Each one is a message the AI wrote and sent to a real prospect in a live conversation. Not "interactions", not API calls, not imported history: sent AI replies.
- 106,466 conversations have had at least one AI reply.
- 377,000+ contacts managed across the platform.
- Median AI reply time: 36 seconds (90th percentile: 77 seconds), measured across 17,288 inbound-message-to-AI-reply pairs in the last 30 days.
- 8x growth in 12 months: from roughly 21,700 AI replies per month in August 2025 to 175,000 in July 2026.
The same AI delivering this read is one click away. Ask it anything. Push back. See if you can break it.
Why the reply time is 36 seconds and not 3
This is the number most tools would brag about in the wrong direction. DM Champ could reply in under 5 seconds; it deliberately does not. Instant walls of text are the number one thing that makes a prospect realise they are talking to a bot. The default configuration waits a humanized 15 to 30 seconds, splits long answers into chunks, and types like a person. The 36-second median is a feature: fast enough that no lead goes cold, slow enough that the conversation reads human. Sub-5-second replies are a vanity benchmark; staying out of the "this is a bot" bucket is the one that closes deals.
Where the replies happen
The distribution is the quiet headline. The AI-setter category grew up around SMS follow-ups inside CRMs, but the actual conversations customers reply to happen on WhatsApp and Instagram. If your AI tool treats WhatsApp as an afterthought routed through a CRM integration, it is an afterthought exactly where 84 percent of this dataset's selling happens.
The growth curve
How we counted (the part vendors skip)
All numbers were queried from the production Postgres database on August 3, 2026. The counting rules:
- An "AI reply" is a message row flagged as written and sent by the AI agent. System events, tool calls, human agent messages and inbound messages are excluded.
- Imported conversation history (chats synced into the platform from before a customer joined) is excluded from every time-series and reply-time figure.
- Reply time is measured from an inbound customer message to the next AI reply in the same conversation, capped at pairs under one hour, over the last 30 days.
- Cumulative counters only ever go up. That is true for every vendor's counter, including ours. The honest questions to ask any tool are: what exactly is one unit, who counted it, and can they show the query. We can.
What this page does not claim: we do not publish a platform-wide "appointments booked" or "revenue closed" figure, because bookings often land in customers' external calendars and revenue lands in their CRMs, where we cannot mechanically count them. Where we have a customer's own verified numbers, we publish them as named case studies instead, like FueGenix's $5M to $10M and its deal-by-deal CRM receipt.
What to do with this
If you are evaluating AI sales tools, use this page as the checklist: ask every vendor what one unit of their headline number is, whether imported or test traffic is excluded, and what their median reply time is with the humanization delay disclosed. If a vendor's number cannot survive those three questions, the number is marketing. If you want the tool behind this dataset, DM Champ starts at $27/mo or $59 one-time on AppSumo.