Choose a listed idea or write your own
Pick an idea from the list. If you don't see what you need, write your own.
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
Tell us what the problem is, which part of your work it affects, and the benefit you expect. The more detail you give, the easier it is for us to review.
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 should go through our contact or support page. Feature requests are for future product and workflow needs.
Good to know
Feature-request questions
Who can submit a request?
Signed-in creators through the Services page.
Can I request something not listed?
Yes. Choose the custom option and describe it.
Will every request be built?
No. Submission starts a review, not a delivery commitment.
Can I get a price or deadline?
The current product does not publish either for feature requests.
Where do I report a bug or account problem?
Use the contact or support page instead.
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.