Acknowledge, defer, decline gracefully, ship-followup.
Feature request: on roadmap
Requested feature is already planned.
Open →Feature request: considering
Request is interesting but not committed.
Open →Feature request: declined
Request doesn't fit product direction.
Open →Feature shipped: original requester
Notify original requester that their feature is live.
Open →Feature request: clarify
Request is too vague to act on; ask for specifics.
Open →Feature request: vote on existing
Customer requests something already requested by others.
Open →Build it via API
Feature can be built by customer using API.
Open →Workaround via automation
Direct feature missing but achievable via Zapier/Make.
Open →Beta invite for requested feature
Requested feature is in private beta.
Open →Feature flag: enabled
Customer asked for early access; flag is now on.
Open →Customer research call invite
Invite requester to a research call to deepen understanding.
Open →Request bundled with another
Request is similar to another we plan to ship together.
Open →Out of scope for product
Request is outside what the product is meant to do.
Open →Priority: paid bump declined
Customer offers to pay for prioritisation; decline gracefully.
Open →email · chat
Similar feature already exists
Customer asks for something we already have.
Open →Feature being deprecated
Customer requests work on a feature being sunset.
Open →Thanks: internal team
Thank a customer who gave deep product feedback.
Open →Promoter: feature ask
Existing happy customer; ask what would push them from 9 to 10.
Open →Customer advisory invite
Invite power user to advisory program.
Open →email · chat
Public roadmap pointer
Customer asks where to see what's coming.
Open →Build a real macro library. Not a Google Doc.
SupportWire's macros learn from your replies. Variables auto-fill. AI suggests the right one.