Problems can also progress through a pipeline and having a Kanban view for problems would help to have a quick overview of your problems and the statuses that they are in at a glance.
As the bot highlighted, Opportunities, Problems and Enquiries have similar pipelineformats. Indeed, I would suggest "problems" have more in common with opportunities than enquiries which are really a customer capture feature (an excellent one). My concern is that "problems" suffer from a reputational/branding issue, everyone wants to be in on an opportunity, no one wants to take on a problem. This is why problems don't have a Kanban view yet because they are not sexy enough. If we rebrand "problems" as "Customer Service" it becomes a much more positive engagement experience for both customers and CRM users. There is great potential to support customers post-purchase in a positive, less "problem" orientated way. Pipelines do this but the Kanban view really leverages the pipelines visualising progress and rewarding success with the rightward movement of each card along the pipeline.
Also - an AI agent/bot inferring that kanban would be good on Problems is pretty impressive! I'll share that internally if only for amusement and "wows" but unfortuntely the bot doesnt yet notifiy the product team when it has a good product suggestion :-)
Also worth adding that if customers log duplicates then we do try and spot that and then merge the ideas - which will also merge (and therefore increase) the votes. I did specifically do a search to see if others had logged this (as I thought they might have done) but couldn't find any duplicates. So, at the moment at least, it's just your votes... but as you say, that may well change over the next few days/weeks as you've only just logged it.
This idea was posted two days ago so it is not surprising it has no votes (is there an explanation somewhere as to how votes work?), the Kanban view for problems was mentioned last October. It would be helpful if someone from the Prospect side could collate the ideas into proposals that users could then vote on? This would be a more structured way to get user input on feature development. I have Bot support for a Kanban view in problem pipelines ;-)...
Hi, this is the idea I referred to in the previous comment. This currently has zero votes. You can remove votes from other ideas to put them on this one. Obviously if it gets more votes or requests we'll look again, but at the moment it's sitting behind some other big UX updates like Tasks, Events and Calendar views (see https://docs.prospect365.com/en/articles/9027673-activities-tasks-events-are-changing for more info) which we're working on at the moment, so I can't give you any specific updates at this stage.
The Kanban view for problems was suggested by Andrew last year when the Opportunities Kanban view was released. Do you have an estimated release date for the Kanban view of problems?
As the bot highlighted, Opportunities, Problems and Enquiries have similar pipeline formats. Indeed, I would suggest "problems" have more in common with opportunities than enquiries which are really a customer capture feature (an excellent one). My concern is that "problems" suffer from a reputational/branding issue, everyone wants to be in on an opportunity, no one wants to take on a problem. This is why problems don't have a Kanban view yet because they are not sexy enough. If we rebrand "problems" as "Customer Service" it becomes a much more positive engagement experience for both customers and CRM users. There is great potential to support customers post-purchase in a positive, less "problem" orientated way. Pipelines do this but the Kanban view really leverages the pipelines visualising progress and rewarding success with the rightward movement of each card along the pipeline.
Also - an AI agent/bot inferring that kanban would be good on Problems is pretty impressive! I'll share that internally if only for amusement and "wows" but unfortuntely the bot doesnt yet notifiy the product team when it has a good product suggestion :-)
Also worth adding that if customers log duplicates then we do try and spot that and then merge the ideas - which will also merge (and therefore increase) the votes. I did specifically do a search to see if others had logged this (as I thought they might have done) but couldn't find any duplicates. So, at the moment at least, it's just your votes... but as you say, that may well change over the next few days/weeks as you've only just logged it.
I can see that you've now voted... which means it will be more likely to be seen in trending etc.
If i remember rightly everyone gets ten votes (but not sure). You can remove votes from other ideas and you can see all your ideas via:
https://ideas.prospect365.com/ideas/?my_ideas=true
and all your votes via:
https://ideas.prospect365.com/ideas/?my_votes=true
This idea was posted two days ago so it is not surprising it has no votes (is there an explanation somewhere as to how votes work?), the Kanban view for problems was mentioned last October. It would be helpful if someone from the Prospect side could collate the ideas into proposals that users could then vote on? This would be a more structured way to get user input on feature development. I have Bot support for a Kanban view in problem pipelines ;-)...
Hi, this is the idea I referred to in the previous comment. This currently has zero votes. You can remove votes from other ideas to put them on this one. Obviously if it gets more votes or requests we'll look again, but at the moment it's sitting behind some other big UX updates like Tasks, Events and Calendar views (see https://docs.prospect365.com/en/articles/9027673-activities-tasks-events-are-changing for more info) which we're working on at the moment, so I can't give you any specific updates at this stage.
The Kanban view for problems was suggested by Andrew last year when the Opportunities Kanban view was released. Do you have an estimated release date for the Kanban view of problems?