To help our Product team accurately understand customer needs and prioritize improvements, please submit product feedback using the following guidelines.
A well-written product feedback ticket focuses on the problem or limitation the user is experiencing — not only the requested solution. This helps ensure Product understands the full context and can design the most effective outcome.
Example: Problem-Focused vs. Solution-Focused Requests
❌ Example of a Solution-Focused Request
“Add an Undo button to the Job Editor.”
This only describes a feature idea — it doesn’t explain the user’s problem or why it matters.
✅ Example of a Problem-Focused Request
Description: Add a way to recover deleted jobs.
Problem / Context:
A user accidentally deleted a job and couldn’t recover it. They expected an option to reverse the action or confirm before deletion.
What are the use cases?
Any user editing job data, particularly project admins.
Impact:
Prevents accidental data loss and reduces support requests for recovery.
Urgency:
Moderate — occurs weekly but causes high frustration when it happens.
Application:
Workflow
This format gives Product visibility into the root issue, context, and scale of impact.
Why This Matters
By documenting the problem first:
Product can identify patterns across customers
Design solutions that address the underlying need
Prioritize work based on real impact rather than surface-level requests
Accurate, context-rich requests mean faster validation, fewer clarifications, and better outcomes for everyone.
Help me write my ticket!
If you ever need assistance on submitting product feedback, reach out the support team via the help center messenger using the “Something Else” button and we can help you workshop your request.