How Feature Requests Work
This category is for sharing ideas, improvements, and feature requests for Convai products, SDKs, plugins, APIs, and workflows.
Feature requests help the Convai team understand what developers need, what is blocking projects, and which improvements would create the most value.
What should be posted here?
You can use this category to suggest:
-
New product or SDK features
-
Workflow improvements
-
API or integration improvements
-
Developer experience improvements
-
Better customization options
-
Missing capabilities that would help your project
-
Improvements to existing Convai behavior
If you are reporting something that is broken or not working as expected, please post it in the most relevant support category instead.
What makes a good feature request?
A helpful feature request explains the problem clearly, not just the desired solution.
When creating a request, please include:
-
What you are trying to build
-
What is currently difficult or missing
-
Why this matters for your project
-
Who would benefit from the feature
-
Any current workaround you are using
-
Examples, screenshots, or references if useful
The more context you provide, the easier it is for the Convai team and the community to understand the request.
Does every request go on the roadmap?
No.
A feature request being posted, liked, or discussed does not guarantee that it will be added to the roadmap.
The Convai team may review requests based on factors such as:
-
How many developers would benefit
-
Product direction
-
Technical feasibility
-
Impact on production teams
-
Existing workarounds
-
Similar or duplicate requests
-
Engineering and product priorities
Some requests may be planned, some may stay open for discussion, and some may be declined or merged with another request.
How are feature requests tracked?
The Convai team may update feature request topics with statuses such as:
-
New — The request has been submitted.
-
Under review — The team is evaluating the idea.
-
Planned — The request has been accepted into planning.
-
In progress — Work has started.
-
Shipped — The feature or improvement has been released.
-
Declined — The team does not plan to move forward with it.
-
Duplicate — A similar request already exists.
These statuses help keep requests easier to follow, but they should not be interpreted as a guaranteed timeline unless explicitly stated by the Convai team.
How are duplicate requests handled?
If a similar feature request already exists, the Convai team may link your topic to the existing request and close or redirect the duplicate.
This helps keep discussion, feedback, and updates in one place.
How can users support a request?
You can support a request by:
-
Liking the topic
-
Replying with your use case
-
Explaining why it matters to your project
-
Sharing what workaround you currently use
-
Adding technical context that helps the team evaluate it
Replies like “+1” are helpful, but detailed use cases are much more valuable.
What happens when a feature ships?
When a requested feature or improvement is released, the Convai team may update the topic with relevant details such as:
-
What changed
-
Where the feature is available
-
How to use it
-
Version or release information
-
Links to documentation or announcements, if available
Thanks for helping us improve Convai. Feature requests are one of the best ways for the team to understand what developers need in real projects.