Saying no well means being honest it won't happen, explaining the why in a line, and pointing them to something that helps today.
Re: your request for [feature]
Hi [first name], Thank you for suggesting [feature], and sorry for the wait while I got you a real answer. I want to be straight with you: this isn't something we're planning to build. Our focus right now is [brief reason, e.g. core reliability or a different direction], and adding [feature] would pull us away from that. That said, I don't want to leave you stuck. A lot of customers get close to the same result by [workaround or alternative]. Want me to walk you through it? I know this probably isn't the answer you hoped for, and I appreciate you caring enough about the product to ask. Best, [Your name]
A requested feature isn't on the roadmap
You'd rather be honest than leave them hoping
There's a workaround that solves the underlying need
Give the real reason in one plain sentence
Don't dangle a "maybe someday" you don't mean
Lead them to a workaround so they're not stuck
Acknowledge the disappointment without over-apologizing
Selvo's AI agent learns your help center and answers questions like this one automatically, citing its sources and handing off to a human when it isn't sure. You keep the templates for the replies that still need you.
See how Selvo AI Agent worksWhen an issue needs more expertise than you can give it, say so plainly, then name who's taking over and when they'll be in touch.
A good intro makes the customer feel handed off with care, not passed along. Say who's taking over, why, and that nothing they rely on is changing.
Thank them for the idea, get curious about the problem behind it, and be honest: logged, considered, not promised.
A reliable reply does four things: acknowledges the person, answers the question, tells them the next step, and leaves the door open.
Help center, chat widget, AI agent, and shared inbox. The whole support stack on one bill. Free for fourteen days, no credit card.
