> ## Documentation Index
> Fetch the complete documentation index at: https://docs.woes.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Feature Requests

> Capture and prioritize product requests from support conversations.

# 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

<Steps>
  <Step title="Create or update an issue">
    Use an issue when the request needs tracking beyond the conversation.
  </Step>

  <Step title="Tag the theme">
    Apply tags such as `feature-request`, product area, integration, or endpoint family.
  </Step>

  <Step title="Add customer impact">
    Include the affected account, plan, urgency, and any implementation blocker.
  </Step>

  <Step title="Link back to the source conversation">
    Keep the customer's original language available for product review.
  </Step>

  <Step title="Follow up after a decision">
    Use the conversation, portal, or account notes to tell customers what changed.
  </Step>
</Steps>

## Useful Fields

| Field                | Why it helps                         |
| -------------------- | ------------------------------------ |
| Product area         | Groups related requests.             |
| Customer segment     | Shows which accounts are affected.   |
| Revenue or plan tier | Helps prioritize business impact.    |
| Workaround exists    | Separates blockers from preferences. |
| Status category      | Keeps the request lifecycle visible. |

## 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.