# Request a Feature ### Your feedback helps shape Aardvark Aardvark is actively evolving, and many of the best ideas come directly from the people using it. If there’s something you wish Aardvark could do — or do differently — we’d love to hear about it. *** #### What makes a helpful feature request You don’t need to write a perfect proposal. Helpful requests often include: * What you’re trying to accomplish * Where you feel friction today * Why the feature would be useful for you (or your audience) Even a short message is enough to start the conversation. *** #### What happens after you submit When you request a feature: * We read every submission * We look for patterns across requests * We use feedback to guide product decisions and priorities Not every request can be built right away, but every request is valued. *** #### A quick reassurance Requesting a feature doesn’t mean you’re asking for too much — it means you’re engaged and thinking about how Aardvark fits into your workflow. That’s exactly the kind of input we want. --- # 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://help.joinaardvark.com/help-and-troubleshooting/request-a-feature.md?ask= ``` 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.