What do you like best about Blip?
One of the main highlights is the exceptional customer support. Additionally, the relationship and CS team is highly competent and committed to ensuring customer satisfaction. Another strong point is the community, which is very active and well moderated, providing a space rich in information and relevant solutions. In fact, we often find useful information and innovative solutions in the Take Blip community. Review collected by and hosted on G2.com.
What do you dislike about Blip?
When dealing with the builder, the visualization of business rules and exit conditions is difficult, generating a tangled mess of arrows. Creating workflows with integrations that depend on multiple data validations from HTTP requests takes a long time, making projects unfeasible. The platform does not support multi-language and there is no campaign mechanism to initiate contacts in flows or automatic active triggers. Real-time run visualization is not available, and there is no trigger system.
When debugging flows, we do not have access to the HTTP request body result, and there is no visibility of which exit condition was triggered. The log was not designed to distinguish and classify data of the same nature, representing them in the same way.
When dealing with contacts, there is no contact manager by groups or customer segmentation. The mirroring and duplication of router contacts to subbots is a terrible problem, as the contact variables in the router are not always mirrored correctly to the subbot. We do not have access to the execution history of contact relationships.
In data analysis, the segmentation of the data structure for report generation is unfortunate. There are no effective methods for extracting production data, and API endpoints are ineffective for rapid data analysis implementations. There is no recognition of attempts and errors in the relationship journey, without performance indicators or counting for passes at exit conditions in an automatic way. The platform does not have a PowerBI connector.
In NLP, there is no own and free NLP engine. It is not possible to use more than one repository in the same subbot for different purposes without decreasing the confidence of the trained intelligence. There are no open repositories with general content.
The platform does not have automatic media conversion. The layout makes it difficult to manage large projects and modularize flows. Dynamic content, message with buttons, and messenger templates are not processed for viewing on the platform. Review collected by and hosted on G2.com.
