Forum Discussion
Hi everyone,
This is really thoughtful feedback, especially around visibility, accountability, and tracking trends. Thank you for laying it out so clearly.
For quotes specifically, have you tried archiving the quote once it has been declined? Archiving will remove it from your active workflow while still keeping it accessible for reporting and history. Some teams use this as their “declined” workflow step.
To track the reason, you could also use custom fields on quotes to capture decline reasons such as price, competitor, timing, or DIY. That way, you can standardize the options now and have clean data when office staff come on board. The same approach can work for jobs, adding a required custom field for cancellation reason so that nothing gets closed out without context.
While it may not be as automated as a dedicated decline or cancellation status with forced reason codes, this workflow can still give you visibility and accountability across your team.
That said, we completely hear the larger point around wanting clearer declined and canceled states built into the core workflow. This is valuable feedback.
We would genuinely love the opportunity to help you get the most value out of your Jobber subscription. If you are open to it, our team would be happy to connect and walk through your current setup to see how we can streamline things or recommend configurations that better fit how you operate.
If you would like to chat, feel free to reach out to Support and we can set something up. We want to make sure Jobber is supporting your business, not creating friction.
Please reach out to our Support team at 1-888-721-1115 option 1 or mailto:support@getjobber.com at a time of your convenience.
Well, mine was kind of grumpy. I'll do better.
The custom field is absolutely the correct way to track the reason for a decline; I'd forgotten about those!
Adding a new status would not be trivial as company resources go. Database schema, logic, reporting, automations, integrations, mobile, analytics, etc. Seems simple from the front end, but it would be a significant to-do list on the back end.
Still though, it would be a great feature and makes sense that it would be there as a standard status option.