Feature Requests
Feature requests often start as support conversations: a customer asks whether something is possible, describes a missing workflow, or explains why an integration is blocked. Woes helps preserve that signal by connecting the conversation, customer, account, and issue.Capture Pattern
1
Create or update an issue
Use an issue when the request needs tracking beyond the conversation.
2
Tag the theme
Apply tags such as
feature-request, product area, integration, or endpoint family.3
Add customer impact
Include the affected account, plan, urgency, and any implementation blocker.
4
Link back to the source conversation
Keep the customer’s original language available for product review.
5
Follow up after a decision
Use the conversation, portal, or account notes to tell customers what changed.
Useful Fields
Avoid
- Treating every question as a feature request.
- Losing the source conversation.
- Mixing bugs and requests under one vague tag.
- Promising roadmap dates in support replies unless they are approved.