Pipefy

My main use case for Pipefy  is to manage processes and to follow processes with Kanban style management and for some automations such as when an activity is completed then someone gets an email asking them to complete a field or to submit another document. However, it is mainly for process reasons.

A quick specific example of a process I manage with Pipefy  is that we used to first receive the suggestion of projects and then the suggestion of participants to conduct this project. Pipefy uses an automation to approve the participation of these candidates in the project with their managers and also to approve the project with the direction of the company. It is all fully automated within Pipefy.

The best features Pipefy offers include the possibility of managing the process in a Kanban style, the fields and making fields obligatory, together with the possibility of making automations, such as notifying someone if a card is in a phase of that process for a long time, then someone gets a notification. When this activity or this phase is completed, someone gets a notification. All these kinds of automations within the transition of phases is the main function that we use in Pipefy.

The automations and required fields help my team day-to-day by ensuring that we have our database always fully completed. For example, there are no blank spaces. We always have the information standardized because the way people fill the fields is standardized because of Pipefy. We have the possibility to analyze this data easily because of this standardization.

Pipefy has impacted my organization positively as we have not reduced our headcount, but we could if we wanted to because the number of people managing those processes before Pipefy was a lot. We have reduced this, and these people now have more time to focus on more strategic and tactical activities and not only on operational activities. We have more standardized data to analyze and now we have dashboards because we have a digital process and not just an analytical process. We do not have paper forms anymore, but we used to have paper forms. All of this has helped us a lot.

A specific outcome since using Pipefy is that we have reduced lead time significantly.

Pipefy can be improved with processes not only following Kanban styles but other kinds of processes that have more paths, not just a single, direct path, but they have bifurcations. Pipefy can also focus on more dashboards and the way to extract and create indicators in the dashboard section as this appears to be a gap.

I have been using Pipefy for two years.

My advice for others looking into using Pipefy is to first describe the process and the improvements in the process before developing the system and the Kanban style. Before you develop Pipefy, I suggest drawing and describing the responsibilities and describing all the process information and the instructions before the tool. I give this product a rating of 8.

Pipefy  is used to handle tickets, ticketing, inquiries, and help desk pipes. I currently manage two pipes for ticket handling, and there are upcoming pipes that align with different use cases.

Reporting  is a main tool I use in Pipefy , following through the tickets especially when connecting with outsourced companies to manage them. Pipefy speeds up my process significantly. Previously, managing emails was cumbersome with around 200 to 500 tickets daily. Pipefy categorizes and moves cards into various phases easily, a stark contrast to following progress in Outlook.

Pipefy's scalability is noteworthy too. It increases awareness through auto replies and emails, smooth ticket category automation, and helps different departments with additional pipes.

The user interface and ease of use are typical, much resembling a usual Kanban board. However, Pipefy requires integration with existing workflows to enhance its functionality, which is still developing. What is lacking is direct support, since I am required to go through a third-party outsourcing company to connect with Pipefy. It would also be beneficial if internal integrations were enhanced for tools such as Power BI, avoiding additional payments.

I started working with Pipefy late twenty twenty four, but I gained my admin access late twenty twenty five.

Pipefy is stable.

Pipefy's scalability is definitely noteworthy. It contributes positively to my workload, allowing me to handle more pipes.

My concern is that I am connected to an outsourcing company, so any request to Pipefy goes through this third party. This is cumbersome, and I find direct customer service with Pipefy to be lacking.

I did previously use ServiceNow  in my past work, but in this current employer, it was not Pipefy; it was just Outlook email, which was the best solution for the Outlook migration.

In terms of money and time saved, Pipefy is a great time saver overall, reflecting in analysts handling additional projects beyond ticket management. This has reduced the need for more employees, as I alone can manage the growth using my admin access.

I think it is important to determine first what you need for the solutions because there are also other alternatives, Kanban solutions, or ticketing solutions that you might need; what matters most here is the usability of the interface.

Pipefy is easy to navigate, resembling a more straightforward and user-friendly Kanban board. It could have been better with more integration features in development. It is not Pipefy's fault about some support issues but rather third-party complications. For usability, Pipefy is favorable given its diverse team adaptability. However, lacking innovative features compared to other existing systems is a downside. I rated this review an 8 out of 10.