Product feedback
Tell us which agency workflow needs improvement
Describe the job, the current obstacle and the result that would solve it. Send a feature request with enough context to evaluate the underlying need.
Reviewed by Agency Pilot ·
Open Ideas & Roadmap in the appDescribe the job before the interface
Explain who is trying to do what, how often it happens and where the current process fails. Include the relevant feature and an example using non-sensitive sample information. A request such as “compare two approved periods in one client report” is easier to evaluate than a general request for more automation.
Explain the impact and a workable outcome
Describe the time spent, the handoff affected or the client decision that is delayed. Separate required behavior from a preferred screen design. Include constraints such as permissions, data freshness or a required export format. This helps the team understand whether the solution belongs in an existing workflow, an integration or a new feature.
Use Ideas & Roadmap in your account
Sign in to Agency Pilot and open Ideas & Roadmap to suggest a feature, vote on existing ideas and follow the changelog. Search for a related request first so the supporting context stays together. For a reproducible error, open a support ticket with the steps and expected result. A feature request helps the team evaluate a need; it does not commit the team to a delivery date.
Frequently asked questions
Does submitting a request guarantee a release?
No. A request is input to product evaluation, not a promise of scope or a delivery date.
Should a bug be sent here?
For an error in an existing workflow, contact support with reproduction steps. Explain what should have happened and what you observed.
Can I include a client example?
Use anonymized or sample information where possible. Confirm permission before sharing identifiable client details and never send credentials.