Gupshup Reviews

My primary use case is managing the infrastructure for our omni-channel communication pipeline, specifically automating multi-factor authentication, delivery transaction alerts, and automated customer onboarding notification via WhatsApp Business API and SMS channels.

In our digital lending and supply chain finance platform where real-time alerting is critical, we configured our microservices running in AWS EKS to trigger Gupshup's REST API whenever a milestone occurs. We built a high-throughput webhook architecture using AWS API Gateway and Lambda to consume Gupshup's real-time delivery status reports. This allows us to track message delivery latency and instantly failover from WhatsApp to SMS if a customer is offline, ensuring compliance with the financial notification timelines.

We use it to abstract communication infrastructure for our product team. Instead of developer teams writing custom logic for various telecom operators, we provide them with a single internally managed wrapper around Gupshup's API.

It is a communication platform as a service. Our microservice hosted on AWS EKS connects directly to Gupshup cloud endpoints, and Gupshup streams transactional data back to our public cloud VPC via secure webhooks.

The best features in my experience are the Unified Omni-channel API, robust webhook framework, WhatsApp template management, developer sandbox, and intelligent routing.

The Unified Omni-channel API provides a single API payload structure that can route messages seamlessly to WhatsApp, SMS, or RCS, which has helped significantly. The unified WhatsApp Business API gateway completely eliminated the operational complexity of managing direct telecom carrier lines and dealing with disparate WhatsApp onboarding processes, allowing us to deploy communication channels in hours instead of weeks.

It has vastly improved our communication engagement metrics, lowered communication delivery latency, and simplified compliance auditing by centralizing our messaging logs.

We have achieved a 97 to 98 percent successful delivery rate for business-critical OTPs and transactional notifications. We also significantly reduced message delivery latency down to sub-three seconds globally, which slashed user drop-off rates during onboarding.

I would appreciate more granular error code documentation for edge case API delivery failures, deeper out-of-the-box integration with cloud monitoring tools such as AWS CloudWatch or DataDog for native metric scraping, and a more responsive administrative console when querying massive historical message logs.

The core API routing engine is incredibly resilient. Most of our desired improvements are around developer experience, such as updating older SDK documentation and providing self-service, multi-tenant sub-account management controls.

The security controls are solid. Given that we have to operate in the fintech space, data privacy is non-negotiable. Gupshup supports secure HTTPS API requests, robust API key management, and data encryption in transit. However, more advanced enterprise role-based access control inside the dashboard would further strengthen governance.

I have been using Gupshup for more than a year.

We negotiated and purchased our licensing directly through the vendor to tailor volume commitments to our scaling requirements.

Invest early in building a resilient webhook consumer architecture on your cloud backend. If you handle delivery status reports effectively, you can build a highly powerful, self-healing message routing logic.

For any DevOps or engineering team tasked with building a scalable, omni-channel notification pipeline, especially in a region where WhatsApp dominates customer engagement, Gupshup is a highly scalable, capable, and dependable utility. I would rate this solution an 8 out of 10.

I typically use Gupshup for the quick connect chatbot tool they have. I just have to drag and drop the conversations in order to make a whole flow of a conversation and depending on that I can take decisions on my end. So, it becomes a really neat helper for my application, which I can make with low-code or no-code using Gupshup.

While using Gupshup's drag and drop chatbot tool in a real project, we had KYC, and instead of making a user guess what their KYC is actually going to be, we gave them a chatbot to chat with so that they can explore the different pathways. There were different kinds of KYC standards: silver and gold. Users could select the options from the chatbot and it would tell them all the features they would get with the acceptance of any one of the KYC options, so the user may have greater insight into which type of KYC they should do for our application.

I have covered most of what I have used Gupshup for. There might be vastly more things which Gupshup could do but my use case was only related to the chatbot, and I did not have to vastly explore it. My use case was very easily solved by Gupshup, and that is what I have used it for.

In my experience, the best features Gupshup offers include the ability for a user with no prior knowledge of code to also use this platform if they are creative. The only thing that Gupshup's use case is limited to is the person's own creativity. It can be used in any way a person sees fit. It is a very versatile tool.

Gupshup has impacted my organization positively by bringing QA really closer to the developers because the one thing which kept us apart was the ability to affect the code and behavior of the application. Now the QA themselves can also affect the behavior of the application in the chatbot area. So they also feel ownership towards the product without actually writing the code. This has brought QA and the developer into a parallel mindset and it is not QA versus developer as it is in a typical situation. It has become QA and developer, so it has brought people closer.

Nothing directly comes to mind about how Gupshup can be improved because for my use case it was the perfect solution and not all of our apps have chatbots integrated into them. For the ones in which we have chatbots integrated we try to use Gupshup itself, but that is a very specific use case. I do not think that is the whole solution that Gupshup provides, so I am not the one to comment on how to improve it, but it really did fit very neatly into my requirement of application.

I have been using Gupshup for the past year and a half.

In my experience, Gupshup is stable since there has been no downtime or issues reported by the customers, and we also have not faced any downtime with it. There might be downtime in the off hours that might not affect the customer, so that is fine.

Gupshup's scalability has been good in my experience. However, I will not be able to comment on the scalability in detail because when we introduced the chatbot, our customer base was already mature and customers have not increased vastly so as to comment on its scalability. However, the amount of customers which we have, Gupshup is handling it pretty well.

I have not interacted with Gupshup customer support as of yet because we have not had any such problems.

Before using Gupshup, we tried making a chatbot on our own, but it was really static and clunky. During my college, I had used Gupshup for my personal project. So I suggested that to my BA and then we got to use it in our organization as well because it was a one-stop solution, and we did not look for any alternatives.

I have seen a return on investment with Gupshup because our business expanded with gold customers. All these metrics are being measured by the BA, so more details will be with them.

Regarding my experience with pricing, setup cost, and licensing, I am just the developer. I am not involved with all of these processes. Our BA might know that. So, I am not the right person to answer it.

Regarding evaluating other options before choosing Gupshup, there were different people with different tools. We just provided our inputs to the BA and the decision was taken by the BA.

My advice to others looking into using Gupshup is to dive right in, get your hands dirty, and you will find yourself understanding why you are going to use Gupshup in your organization.

Gupshup is a pretty neat software for people who are looking for integrating a chatbot or other AI capabilities into their applications, and it is a pretty neat solution.

I found this interview to be a pretty neat kind of interview. It is really new, and I have not had any voice-assisted reviews for any products earlier, so it was really refreshing.

I would appreciate a short poem or haiku that summarizes my review. My review rating for Gupshup is nine out of ten.

My main use case for Gupshup is for integration with WhatsApp.

A quick and specific example of how I use this integration with WhatsApp in my day-to-day work is that we use the integration with OTEC call centers. OTEC is a national manufacturer from Florianópolis that has a PBX, and we use Gupshup's broker to do this integration with OTEC's system and have customers communicating on WhatsApp through it.

I do not have anything else I would like to add about this use case or any detail I consider relevant.

In my experience, the best features that Gupshup offers are support in Portuguese, relatively fast support, and ease of integration. It is much easier to carry out the integration via Gupshup than to do it directly through Meta.

The ease of integration that I mentioned contributes to my team's day-to-day work because using their webhook makes the integration process fast. You create the account in a much more agile way. Regarding support, whenever we needed changes, alterations or even assistance in cases of blocking or banning, they were very quick in supporting us, even with calls and hands-on service. This was very positive.

I believe Gupshup has made the process of integrating WhatsApp for customers more agile.

I do not have anything else I would like to add about Gupshup's features.

I think Gupshup could be improved with online support or WhatsApp support so that we can talk directly with an agent, instead of working only by email.

I do not have anything else I would like to add about the necessary improvements.

I have been using Gupshup for approximately three years.

In my experience, Gupshup is stable.

I think Gupshup serves both small and large projects. We have customers that send thousands of messages per day and customers that send fewer, and it works stably in all scenarios. I think it is very good.

Today, Gupshup's support is essentially via email, so most of the requests we send are by email. In critical cases where we had a customer banned, we managed to schedule a call with the analyst. However, ninety-nine percent of the time requests are by email, and it takes twenty-four to forty-eight hours to get a response.

At UANET, I have not used a different solution; we have always used Gupshup from the beginning.

I was not involved in the cost part. The only part that I got involved in was the credit and balance part for sending messages for customers. It is relatively simple, as they have a wallet with the balance for sending messages and we can monitor the sending and how much the customer consumes. We do not have server, storage, cloud, or any costs with Gupshup.

I was not the one who made the decision to choose Gupshup. When I joined the company, Gupshup was already being used.

I do not have any specific metric or feedback that stood out about how this agility has impacted business results or customer satisfaction.

I do not have that metric available regarding return on investment using Gupshup.

I was not involved in the cost part. The only part that I got involved in was the credit and balance part for sending messages for customers. It is relatively simple, as they have a wallet with the balance for sending messages and we can monitor the sending and how much the customer consumes. We do not have server, storage, cloud, or any costs with Gupshup.

At UANET, I have not used a different solution; we have always used Gupshup from the beginning.

On a scale from one to ten, I would rate Gupshup an eight. I rate it eight because I imagine they could have improvements to get to ten. I understand ten as something that is perfect, and eight I understand as something that is very good. I really think it is very good, but I think it can still be improved.

I recommend that others who are thinking about using Gupshup consider that the ease of integration makes using Gupshup worthwhile. It is a stable platform and has good support.

My company has a solution that our clients use to talk with clients, and we use Gupshup as a broker to send a message to Meta and receive a message from Meta because we thought that it was easier to use a broker than to develop our integration with Meta.

I don't have anything else to add about my use case because I've been using Gupshup for just six months, and it's not every day that I use the integration with Gupshup, so I am learning a lot about Gupshup.

I think the best feature Gupshup offers is the very good documentation, and I appreciate how they provide assistance when we need it, as well as the architecture of the documentation.

The documentation is very easy to read and is very specific, and I don't have any trouble when developing our features using Gupshup, such as using webhooks.

Gupshup has improved a lot how our clients can talk to other users. When we implemented the integration with Gupshup, almost all our clients approved the integration and they appreciate it. Plus, we use almost all the features about Gupshup, which I think is the most important for our clients.

I don't know what could be better about Gupshup. Our solution uses almost everything, as we can send stickers, images, PDFs, and audios, and we receive almost any type of message.

I remember that I was trying to get the webhooks about account information, and I had trouble finding in the documentation how I could receive webhooks about the account, such as when we have an account that could be blocked or when the limit of messages might be erased.

I have been using Gupshup for maybe six months.

I have never experienced downtime or disruptions with Gupshup, except for the case where I received the same webhook three times.

I think that Gupshup is very good when it comes to accuracy. Sometimes I have trouble, such as when I was testing a new feature and received webhooks three times, which means we need to improve our code to prevent sending the same message to the user.

We have a WhatsApp group with some people from Gupshup Brazil, and when I have a question or need assistance, I send a message there and they respond quickly and accurately. I don't have any problems with the customer support, which is very good at Gupshup.

I think there isn't anything else I appreciate about Gupshup's features.

My advice for others looking into using Gupshup is to read the documentation very carefully and try to integrate using it because it's very good.

I don't remember anything else to add about Gupshup.

I think that I just don't give a ten because everything needs to improve—there's always something to enhance. I think Gupshup is very good, but I believe that if we think about the ten, it might lead to complacency, so I give it a nine because maybe they can surprise me in the future by adding a feature that would impress me. I would appreciate a short poem or haiku that summarizes my review.

I rate this review a nine out of ten.