Reviews from AWS Marketplace
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
External reviews are not included in the AWS star rating for the product.
SMS Verification Worked Without Fail
What do you like best about the product?
The instructions for integrating the Nexmo sms verification were straight forward and easy to use. Nexmo added the power to my customer onboarding process and was instrumental in my business success.
What do you dislike about the product?
Nexmo sms verification had everything we needed to be successful
What problems is the product solving and how is that benefiting you?
Nexmos SMS verification process allowed me to easily on board customers globally. Nexmo offered a low cost, always available solution.
- Leave a Comment |
- Mark review as helpful
Its ok, handles large volumes nicely
What do you like best about the product?
Very fast and has lots of features to select from SMS/Voice messages. Lots of lines to buy for this.
Easy interface
Easy interface
What do you dislike about the product?
Nexmo does no work nicely with Canadian carriers, meaning they do not know if a line is a Cell/Landline or even who is the carrier of the destination line. Now your thinking why do I care about this??? because in Canada there is a carrier Freedom who will not accept Toll free SMS messages but when we send the SMS we get a success and no failure because Freedom does not respond. But Nexmo returns that the carrier was Telus/Bell/Rogers etc when it really was Freedom. So if we knew it Freedom we could send out on a normal line and get a success but we dont know this.
Also Nexmo does not know if its a landline or cell line in Canada so we get a success but really the carrier noticed that it was a landline and threw away the SMS and did not respond with a failure message. If Nexmo knew then we could inform our client and the phone number can change. Right now we just fail repeatedly sending to this number with no help from Nexmo or Carriers.
Now you think this is just 2 issues so how much could this impact us, well we send out 80,000 SMS a day and we get floods of support calls about how the SMS never made it to the destination and we don't know why and Nexmo support takes about 3-4 business days to respond with an answer because they dont even know if its a Freedom or landline and have to ask the carrier.
So we are not happy
Also Nexmo does not know if its a landline or cell line in Canada so we get a success but really the carrier noticed that it was a landline and threw away the SMS and did not respond with a failure message. If Nexmo knew then we could inform our client and the phone number can change. Right now we just fail repeatedly sending to this number with no help from Nexmo or Carriers.
Now you think this is just 2 issues so how much could this impact us, well we send out 80,000 SMS a day and we get floods of support calls about how the SMS never made it to the destination and we don't know why and Nexmo support takes about 3-4 business days to respond with an answer because they dont even know if its a Freedom or landline and have to ask the carrier.
So we are not happy
What problems is the product solving and how is that benefiting you?
Its fast and quick SMS responses
Recommendations to others considering the product:
Canadian SMS support is limited. Short lines are way too expensive. Carrier/Network code returned during sending is not accurate.
Nexmo offers easy to use API and SMS structure, but the personal support is a little lacking
What do you like best about the product?
Nexmo prices are incredibly low, and there's no minimum amount of messages per month or a subscription to pay. Their API is very quick to learn and implement on a small scale.
What do you dislike about the product?
Whenever I had a question about something involving the API or restrictions for my country (US) it took several hours to a day to get an email response from Nexmo. Since I work in tandem with an company sourced in India, those few hours usually lead to a day of no productivity because of time zone differences.
What problems is the product solving and how is that benefiting you?
Our company is using Nexmo to send alert notifications to our customers regarding a particular situation that occurs during the use of our products. We have not realized any benefits yet, since we are still testing the Nexmo API with our use case. However, the price difference between Nexmo and our current platform (Red Oxygen) is substantial
Recommendations to others considering the product:
Get in touch with a customer representative and have them walk you through the API process if you're confused. Make sure to read all documentation, as the support will usually link you to one of the documentation pages.
Great product, nice integrations and good documentation.
What do you like best about the product?
You have a great product,I like the nice integration that it has with Laravel. I've used other solutions like Plivo but this, in my opinion, has a far better quality product. Also, the documentation is very good and very easy to use. Another thing that I like is the size of the community around your product. If you need help there are a ton of resources to look up with, and if not, you could always post a question in StackOverflow and get a proper response from developers already familiar with the service. This is really great. A great product needs to have a great community.
What do you dislike about the product?
You offer greate services, but there are only avaliable in some countries. If I need to make an advise, I'd say provide more API coverage for foreign countries like Peru. Also, we'd like to have a better pricing and a low entry barrier for stutends to start playing with the products to ease the transition to your platform.
What problems is the product solving and how is that benefiting you?
At the moment you solve or most importante needs (related to your offered services) that is User notifications. We also want to implement the Voice API soon in order to improve our application.
Recommendations to others considering the product:
Review the nice documentation that Nexmo offer in order to integrate the service in no time.
Great delivery, I hate they split up from Telerivet though.
What do you like best about the product?
I like that it can deliver SMS pretty much anywhere through rented numbers. While this is fantastic for us with our employees, I suppose it wouldn't be very appreciated from a spammer. It's just too good.
This review is my own opinion, and does not represent the view of IBM or its affiliates.
This review is my own opinion, and does not represent the view of IBM or its affiliates.
What do you dislike about the product?
We used to be able to contract with Telerivet through Nexmo, but no longer. That was nice, because Telerivet offers a great UI for the Nexmo APIs.
What problems is the product solving and how is that benefiting you?
We use SMS messages for essential updates to our employees.
Recommendations to others considering the product:
Get Telerivet if you don't already have a UI
A solid SMS gateway, super nice
What do you like best about the product?
Very good support, very good dashboarding abilities. I loved the extra capabilities (not-only-SMS-sending).
What do you dislike about the product?
too many price changes, mostly upwards. Also, the abstraction of SMS sending details is kind-of lost, and dropped on the client (e.g., if we're trying to send an A2P SMS in USA, there's a different API for that - that's a fact I didn't want to know).
What problems is the product solving and how is that benefiting you?
We had to implement a 2nd factor authentication to existing user on-boarding flow.
Recommendations to others considering the product:
Make monitoring (including balance and delivery receipts) mandatory from day 0, otherwise you'll need to fight the team to get this one prioritised.
Easy to integrate and send SMS from our application
What do you like best about the product?
The dashboard makes it easy to provision and keep current with our SMS numbers. The API is URL based so it's easy to make calls to it.
What do you dislike about the product?
They didn't have a reporting API initially, but they have since added it.
What problems is the product solving and how is that benefiting you?
Our point-of-sale applications need to send SMS messages and Nexmo lets us deliver that feature to our customers for a reasonable price.
Great API
What do you like best about the product?
The API is really easy to use. I mostly use it for SMS.
What do you dislike about the product?
SMS logs should be directly available on the website. Right now, I need to export SMS to visualize the history.
What problems is the product solving and how is that benefiting you?
We send notifications to our clients. They are mostly reminders for bookings. It helps us engage more with them.
Great product!
What do you like best about the product?
The ease and use of Nexmo is amazing, and I find the day to day use really easy
What do you dislike about the product?
The top up minimum amount could be lower, so that I can do small chunks instead of one big payment
What problems is the product solving and how is that benefiting you?
mass messaging is perfect for my needs
Experience from implementing the nexmo api
What do you like best about the product?
I appreciate the vast offer of different voices and different languages, as well as the vast offer of different endpoints and features. When having problems with the implementation and therefore contacting nexmo support I got responses quite fast and I it seemed like the support really wanted to help.
What do you dislike about the product?
The documentation is not thorough enough, the endpoint docs should contain more details and there should be more examples and exact descriptions added as well as more explanation would make the implementation faster and easier. There was one nasty bug in the api that slowed thing down or maybe a super strange feature/documentation error.
What problems is the product solving and how is that benefiting you?
Sms and voice call confirmations are required for the platform and thus there is a need for a stable, cheap and available provider.
Recommendations to others considering the product:
Be careful with the api documentation and don't make wrong assumptions.
showing 111 - 120