# Product Feature Requests

Have an idea for a new feature or a workflow improvement? Welkin actively uses customer feedback to shape the product roadmap. Feature requests are one of the primary inputs into prioritization decisions.

***

## How to submit a feature request

You can submit a feature request in two ways:

### Via your Customer Success Manager

The quickest path is to share your request directly with your **Customer Success Manager**. Your CSM will:

* Log the request in Welkin's internal feedback system
* Confirm it has been received and is under consideration
* Keep you informed if it's added to the roadmap

### Via the customer feedback portal

1. Navigate to the **Welkin feature request portal** (link available from your CSM)
2. Search first – if a similar request already exists, **vote and add a comment** rather than creating a duplicate. Votes help prioritize
3. If no existing request matches your need, click **Submit new request**
4. Include the following to maximize impact:

| Field                  | What to include                                                 |
| ---------------------- | --------------------------------------------------------------- |
| **Problem statement**  | Describe the workflow pain point, not just the desired solution |
| **Desired outcome**    | What would success look like for your team?                     |
| **Frequency & impact** | How often does this affect your team? How many users?           |
| **Workaround**         | What do you currently do instead?                               |

***

## What happens after you submit

1. **Logged** – Your request is added to the product feedback backlog
2. **Reviewed** – The product team reviews requests quarterly as part of roadmap planning
3. **Prioritized** – Requests with higher vote counts, broader customer impact, and strategic alignment are prioritized
4. **Communicated** – If your request is added to the roadmap, your CSM will notify you with an estimated timeline

{% hint style="info" %}
Feature requests do not have guaranteed timelines. Welkin cannot commit to implementing specific requests, but all feedback is reviewed and influences product direction.
{% endhint %}

***

## Tips for effective requests

* Focus on the **problem**, not a specific solution – this gives the product team flexibility to find the best approach
* Include **business context** – regulatory requirements or patient safety impact get elevated attention
* **Vote on existing requests** before creating a new one – combined votes carry more weight than duplicate submissions

***

## Related

* [Support Plans & SLAs](/support/about-support/support-overview.md) – understand your support coverage
* [Support Tickets](/support/submit-a-request/support-tickets.md) – for bugs, not feature ideas
* [Work Requests & Licenses](/support/submit-a-request/jsm-work-requests.md) – for operational changes


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.welkinhealth.com/support/submit-a-request/product-feature-request.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.