Choose a listed idea or write your own
The current request UI supports both predefined service ideas and a custom option for a need that is not listed.
Feature Requests
Help shape what we build next
Describe the service or workflow you need. Your request is recorded for review and may move into implementation when it fits the product and benefits creators.
How to ask
Describe the need, not just a feature name
Share the service name, category, and a clear description of the workflow you need. Submission records a request; it does not book a live consultation.
Make the problem easier to understand
Explain the problem, the affected part of your workflow, and the benefit you expect. Useful context helps review without implying a fixed scoring model.
After you submit
Every submission is recorded for review
The team can assess the request without promising that every submission receives a personal reply. Submission is the start of a product decision, not a delivery commitment.
How a request may progress
A request may remain pending or reviewing, move through approval and implementation, or be rejected or marked as a duplicate. Implementation is one possible outcome, not the default.
Needs review
Pending or still being assessed
Planned / implementing
A possible route, not a promise
Not now / duplicate
Recorded with the review outcome
Need help now?
Contact supportSupport is a different route
Product bugs, account problems, and urgent help belong in Contact or support. The feature-request flow is for future product and workflow needs.
Good to know
Feature-request questions
Signed-in creators through the Services page.
Give the next useful workflow a clear starting point
Create an account, describe the need in context, and submit it for product review without treating submission as a delivery promise.