# Marcus Reyes, Head of Customer Success at Threadline — read of HelpDesk AI, May 9, 2026

> 9 years in B2B SaaS support, currently managing a 6-person CS team for a 40-person project management tool with about 3,200 paying customers. Coaches U10 soccer on Saturdays. Two kids. Commutes 42 minutes each way and uses that time to catch up on industry podcasts.

## How I got here

Monday morning, 114 tickets in the queue after a rough product release. I searched "AI helpdesk automation Zendesk" sometime around 8:30 AM before standup. This came up on the second page of results. I clicked it because the meta description didn't say "revolutionize" or "10x your support." That's a low bar to clear, but here we are.

## What I clicked first

The headline "Stop losing time to repetitive tickets" landed fine. Nothing special, but it's honest. Then I hit the math paragraph: "if you handle 500 tickets a month and 60% are routine, you are burning 300 person-hours on work a chatbot should handle." I actually stopped and ran it in my head against our numbers. We're closer to 900 tickets a month. That part worked on me. The math framing is more persuasive than any feature list they put below it.

## Where I paused

The FAQ answer to "How long does setup actually take?" says "Five minutes. Connect your email or ticketing account, upload 10 past customer tickets so the AI learns your tone, and you are live." I've heard this claim from four vendors in the last two years. Not one was five minutes. I've come to read "five minutes" as "five minutes if everything goes perfectly and you have no edge cases in your data." What I actually want to know is: what does week 3 look like? What breaks? That's where every one of these dies.

## What I distrusted

Two things, and they're different levels of bad.

First: "75% of tickets close without escalation." That number is sitting there with no sourcing, no qualifier, no "across customers in our beta." It could be true for a specific customer with a very narrow support scope. It could be the best customer they have. I don't know, and the page doesn't tell me. That's just a number someone decided sounded good.

Second, and this one stopped me cold: at the very bottom of the page, after the $299/month pricing table, there's a completely different pricing section that says "Browse Free. Unlock for $5. Adopt for $99." And below that: "Estimates only. No live customer revenue claimed." And then: "probability of meaningful success around 13%, by Fermi heuristics." And: "Year-1 ARR mid-case around $71K."

So this isn't actually a product. This is a studio called Wishdeal selling me the CONCEPT of a product, with a starter kit, for $99. The entire homepage I just read is a pitch for an idea, not a live tool I can log into. The $299/month pricing section is... for a product that doesn't exist yet? I had to read that bottom section three times. I'm still not sure I'm reading it right.

"You will love it." is on there too. That line should be deleted by anyone with a UX conscience.

## What would convince me

If this were a real product: one named customer in my space, roughly my company size, with a support volume quote I can sanity-check, and a number for what their escalation rate actually dropped to after 90 days. Not a testimonial. A mini case study with a before/after. Two paragraphs. I don't need a PDF.

If this is the studio selling a concept: I'd need to understand what I'm actually buying for $99. What does "working code starter" mean? Is it a repo? A no-code template? Does it connect to Zendesk on day one or is "connects to Zendesk" part of what I build? That's not clear anywhere on the page.

## What I'd ask in an email reply

1. The bottom of the page says "no live customer revenue claimed." Does that mean the product isn't live yet, or just that you're not claiming revenue figures for it? Because I just read a pricing table for $299/month that implies there are customers paying it.

2. The "10 past tickets" setup claim: what's the actual failure mode? What happens when the AI misclassifies a billing dispute as a feature request and a customer's refund request sits unactioned for 48 hours?

3. If I pay the $99 adoption tier, what do I actually receive? Is it a working Zendesk integration or do I need a developer to finish it?

## Verdict: dismissive

Not of the idea, which is real and the market timing is fine. Dismissive of this page, because I genuinely don't know what I'm buying. By the time I hit the bottom, I realized the whole thing was a studio selling concept kits, and now I don't trust anything I read above it. That's a hard hole to dig out of.

---
*Memo by skeptic persona, generated 2026-05-09. Studio breaks own self-grading loop.*