I built an AI that answers support questions. Founders still hated it. Here's what I learned.
Early version of Velor was a great question-answerer.
Customer asks "how do I add a team member?" — perfect response, cited the right doc, even knew about the edge case with SSO.
Founder still got a support ticket the next day. "Can you just add me manually? I can't figure it out."
That's when I realized I'd been solving the wrong problem.
The questions that kill founder productivity aren't the ones that need answers.
"What's the status of my refund?" → needs an answer
"Can you just issue it?" → needs an action
"Where's my order?" → needs an answer
"Can you reroute it to my new address?" → needs an action
"Why did my payroll run fail?" → needs an answer
"Can you reverse the charge?" → needs an action
The answerable questions are annoying but fast. You paste a doc link and move on.
The actionable ones are the ones that ruin your afternoon. You have to log into Stripe, find the transaction, check the amount, decide if it's legitimate, then actually do the thing — all while you're supposed to be building.
So I rebuilt it.
Instead of just grounding answers in docs, it now connects to Stripe, Shopify, Zendesk, and a few others. When a customer asks for a refund, it doesn't say "here's how to request one." It checks the order, confirms with the customer, and processes it — with a signed audit log of every action it took and why.
It still answers questions. But it also does the thing.
What changed:
Deflection rate went up (fewer tickets escalated to founder) — expected.
The surprise: the tickets that did escalate were completely different. Before, founders were getting "can you just do X for me" all day. After, those were gone. The escalations left were genuinely nuanced judgment calls — the kind a founder should be involved in.
If you're running support for an early-stage product, curious what your most draining ticket category is. For most founders I've talked to it's some variation of "I know what needs to happen, I just have to be the one to make it happen."
That's the problem I'm trying to kill.
Demo at velorplatforms.com if you want to see it — no signup, just talk to it.
The reframe from answer to action is the real finding here. Most support AI stops at the first one because it is safer to build. The part worth pushing on is the confidence boundary on the money moving actions specifically. A refund is reversible and cheap to get slightly wrong. A payroll reversal is not. Does Velor use the same threshold for deciding when to act on its own across Stripe, Shopify, and Zendesk, or does it get more conservative specifically where the dollar amount or reversibility changes, even when the question sounds equally clear cut on the surface?
The distinction between answering a support question and actually resolving it is pretty significant. It sounds like the bigger shift was in what remained for the founder to handle after the easy tickets disappeared.