Grasshopper is an IP telephony business communication solution that provides companies with a toll-free or local phone number. It has both desktop and mobile applications and includes features such as custom greeting recording, call forwarding, call transfer, call reporting, and voicemail.
$18
per month for a single user
Salesforce Agentforce Service
Score 8.6 out of 10
N/A
Service Cloud is a customer service platform that helps businesses manage and resolve customer inquiries and issues. It provides tools for case management, knowledge base, omni-channel support, automation, and analytics, enabling companies to deliver exceptional customer service experiences.
$25
per month
Twilio
Score 7.9 out of 10
N/A
Twilio offers a CPaaS and CCaaS solution, with the combination of its programmable Voice, Video, and Messaging APIs, as well as the Twilio Flex cloud contact center. Additional capabilities include Twilio's Elastic SIP Trunking, as well as API for WhatsApp.
$0
per min per participant
Pricing
Grasshopper
Salesforce Agentforce Service
Twilio
Editions & Modules
True Solo
$18
per month for a single user
Solo Plus
$32
per month
Small Business
$70
per month
Starter Suite
$25
per month
Pro Suite
$100
per month per user
Enterprise
$165
per month per user
Unlimited
$330
per month per user
Agentforce 1
$550
per month per user
Programmable Video
$0.0015
per min per participant
WhatsApp Business API
$0.0042
Per WhatsApp Template message sent
WhatsApp Business API
$0.005
Per WhatsApp session message
Elastic SIP Trunking
$0.007
Per min for termination
Programmable Messaging
$0.0075
per message sent or received
Programmable Voice
$0.0085
per minute to receive a call
Programmable Voice
$0.013
per min to make a call
Elastic SIP Trunking
$0.045
Per min for origination
Twilio Conversations
$0.05
per active user per month
Twilio Authy
$0.09
per authentication
Programmable Wireless
$0.1
per MB
Twilio Flex (Contact Center)
$1
per active user hour (5000 hours free)
Programmable Wireless
$2.00
per SIM card
Twilio SendGrid Email API
$14.95
per month up to 100k emails. (Up to 40k emails free for 30 days)
Twilio SendGrid Marketing Campaigns
$15
per month for 5,000 contacts and 15,000 emails. Your first 2,000 contacts are free
Twilio Flex (Contact Center)
$150
per named user per month (5000 hours free)
Offerings
Pricing Offerings
Grasshopper
Salesforce Agentforce Service
Twilio
Free Trial
Yes
Yes
Yes
Free/Freemium Version
No
Yes
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Optional
Additional Details
20% discount available for annual pricing.
—
1. Pay-as-you-go pricing: Simple usage-based pricing without contracts.
2. Volume discounts: Discounts trigger as usage grows.
3. Free trial credit that includes full API access.
More Pricing Information
Community Pulse
Grasshopper
Salesforce Agentforce Service
Twilio
Considered Multiple Products
Grasshopper
Verified User
Anonymous
Chose Grasshopper
It came down to price and reliability. Even though it's not 100% perfect, it's significantly better than the other options we have tried.
We moved away from Grasshopper when we implemented an answering service that had an application which provided the same functions as grasshopper for calling and texting. We initially selected Grasshopper as our communication solution because our original answering service just …
I switched because Grasshopper was more reasonably priced and the functionality was better. It is also easier to use and the customer service is better. Overall, the experience with Grasshopper has been great. And I like how I can access my calls and voicemails on my android …
Before using Grasshopper, we were only using personal cell phones. Giving out our numbers to all customers and visitors meant that they could call our cell phones even after business hours. Implementing Grasshopper allowed our organization to make it so that business calls …
Grasshopper stacks up against the competition. With an easy to use portal, low cost, and multiple options to choose from, Grasshopper is a formal contender. We’ve used Grasshopper for the last few years with an amazing amount of success. There is no competition when it comes to …
What went into my decision making process was price, ease-of-use, being able to port or carry over my 800 number no matter what my physical location would be. How I came upon Grasshopper is because I moved from one office location to another and the business number I had for …
It stacks up very well against a traditional phone alternative. No hardware necessary, no complicated setup or training, it's perfect. I honestly did not compare to other internet based companies. They checked all of the boxes and came highly recommended from a colleague, so I …
The amount of features is unmatched by the other service I've used. It's not a fair comparison, however, I will say that the features work very well. I've never had a client complain, only compliments, so as far as I'm concerned. The price for the value is good.
For some small businesses that want a virtual phone number, Skype might also be an option. We use Skype as well, but it is not a replacement for the features of Grasshopper. Skype can give you a virtual number, but it won't provide extensions, caller directory, complex …
In all candor, we only considered an in-house solution and Grasshopper. We have all of the technical wherewithal to implement our own Grasshopper-like system. The deciding factor for us was maintenance. Had we done it ourselves, there would need to be at least two people (a …
Zendesk - I think it's not exactly user-friendly for the final user, but it's user-friendly for the configuration. So it's easier to manage when we have these amounts of data we're going through and it's more AI prepared. So by far Salesforce is more ready for what we want as …
We selected this product because we already had some competencies in Salesforce. We own a Salesforce partner with expertise in this area, and on top of that, Salesforce purchased it — it was originally called Velocity. When Salesforce decided to acquire it, that finalized the …
I evaluated ServiceNow also, but we didn’t see much customization kind of thing compared to Salesforce Service Cloud. And yeah, that’s it — I didn’t evaluate many other products because I’ve been working on this one for the last 14 years. I just evaluated a few things in that. …
I think Agentforce now got a lot of, I mean it will make our lives easier because there's a lot of automation going on at the same time. We're excited about Salesforce voice as well. That will help us in Service Cloud. So it's more of unified service for us that say a Service …
Evaluated ServiceNow. Evaluated Zendesk. We selected it primarily because we already had the Salesforce ecosystem and we didn't want to bring in another vendor. For us it was important to make sure that our data is only in so many different systems and so many different cloud …
Oh, now see, I forget the names of the other ones I've done. I mean I've used C4s, I've used some lower end ones too for local small business and I'd even recommend Salesforce for small business. Say pricing strategy for small businesses is harder for them to keep up with the …
Going back when this product was selected, they went through probably a two year evaluation process. We weren't personally a part of that obviously because we were on the implementation side, but they evaluated many products. Microsoft and Pega were the two main front runners …
I wasn't by the evaluation for years, so not that, but historically I've been here for 13 years, so not a lot, but previous company had a home built solutions for it, so they designed their own and built their own. But that was a big telco in the UK we had our own data centers …
I honestly prefer Zendesk to Salesforce Service Cloud. I find that Zendesk is easier to manage both on the support ticket side, as well as the knowledge center side. It looks and feels easier to use than Salesforce Service Cloud. Salesforce Service Cloud is fine, but it is …
Zoho is not very real-time, it has limited integration capabilities, and the UI is not very satisfactory for any incoming customer. The performance is slow and impacts the overall customer journey. The data stored in the backend is slightly scattered and needs to be cleaned …
Salesforce is a really great case management tool. Made things a lot easier for our team. Wanted something fairly simple that had a variety of capabilities we could customize.
We used Salesforce for years, Left for Hubspot, and then came back to Salesforce (SF). As they say, don't fix it if it's not broken. Salesforce and customizing were better for us.
Salesforce Service Cloud offers deep integration with our current and expanding CRM data, along with numerous pre-built features that didn't exist in Kayako when we used it. (We used to use an instance Kayako installed in a private cloud environment.) Salesforce Service Cloud …
Zendesk has it's own challenges in terms of Administrator difficulties and a completely different back-end than Salesforce Service Cloud. I would recommend Salesforce Service Cloud if you need a clean database of Companies and Contacts. Zendesk does not excel in overall CRM …
I'm not at the level where I would be part of the decision making process for choosing a vendor or product for the organization. Every position I've held, I've come into a company that has already implemented or is in the process of implementing Salesforce. Honestly I would not …
Out of all these other platforms I tried, I used ClickSend the longest before switching back to Twilio. I always kept going back to Twilio because it outperformed and and the savings were always bigger with Twilio.
I'll be honest it wasn't my decision to go with Twilio and I wasn't part of the buying committee. We chose to go with them since a different department of ours used their services previously and recommended and led the process with them when our issues were brought up to them.
It's more customizable and scalable. It's more of an enterprise solution with a complete platform that provides good SLAs compared to other vendors, which often will need to be supplemented to meet the full product suite
This is really geography-dependent. Bandwidth is good in the US, but they had a reliability issue a few years ago. They have similar pricing and are more open to partnering. Sinch is more telco-focused and has great reliability, not big in the US market. Infobip is EU based and …
We have looked at some of Twilio competitors, like Infobip, Sich and Bandwith. Prices on all of them for voice minutes and SMS are way cheaper than Twilio. But none of them seem to offer as many features and ease of use as Twilio. Specially from an API point of view
Some of the products we used were MSG91 and SMSala but the issue with them we got to know after the integrations that at some part of the world these integrations are not able to deliver important OTP sms and also it was hard to find solutions in their site. Then we switched to …
I think Twilio is as stable as Avaya in the sense that it comunicates well, but the market is really more into Avaya, so we had to go into a lot of effort to convince everyone in the company that Twilio was good and would work. I think it doesn't hold up againt Watson, because …
I've also worked with ChatApp which is another communications integration platform for multiple channels such as WhatsApp and Telegram. I did find their integration setup process a bit more streamlined plus they don't have a WhatsApp template approval process. This then begs …
Twilio is the idea solution for our needs, which involves sending targeted SMS messages to prospects who have opted into our ads. We do this to communicate offers/services and also to remind prospects in the lead-up to sales appointments (plus post-meeting communications). We …
Twilio stacks up against competitors with its knowledge and experience in the messaging industry. Others lack the ability and know how, to compete effectively. Twilio knows how to do business in complex regions worldwide, and we are so happy to have Twilio as our partner to …
Twilio is most easy to implement and operate comparing with other solutions in the wide-industry. Easy to use, quickly integration, and excellent API documentation was helpful to developers for integrate Twilio solutions in our applications.
We evaluated many fundraising-based text-to-give programs and found the subscriptions prohibitively expensive for our small scale and uncertain first few years of development. While we may be willing to invest that kind of money after discovering how things work, we're happy …
We needed a tool that could be implemented into our software. Since Twilio offers libraries that can be programmed into any software, we decided to use Twilio. Also, the documentation and prices were better.
Twilio was referred to me by a business colleague, and I can't be more thankful! Twilio has helped my Facebook page by leaps and bounds, and I haven't even considered trying another chat option for my page. It is easy to set up, and customer service is quick to answer any and …
This software is so complex we can say that Twilio works so much better in the interface, also the features provided by Twilio are far better than this software it also includes SMS, MMS, and so many other functionalities which helps a developer to communicate with the help of …
Seems like it is perfectly suited for ANY small to medium business. I can imagine that a business would outgrow the system eventually, but probably around 75-100 employees? Great system for offices that are not managed full time, companies with remote workers, budget conscience start ups, anyone with a need for a registered office line.
Probably where you have a number of service teams that all contribute to a knowledge base is one area that's really useful. AI response, it looks like with AgentForce, that's going to be one of our next deployments. So they're AI based on the trust layer is, I like that it has the trust layer because it's already got some built in safeguards around privacy and security controls for AI, which is very important right now. Where it's probably less useful:gain, round robining a very email heavy conversation, so it's not the best email tool. A lot of our team still uses Gmail and logs to the case rather than actually emailing directly out of Salesforce. Email signatures are not great because you can only have plain text email signatures, you can't have HTML.
I have tried other competitors. But I always end up going back to Twilio because I feel like it is dependable, easy to use, and, has competitive pricing. The only time I wouldn't recommend Twilio to someone as if they are completely inexperienced about using webhooks or APIs. Because you can't really just sign up and start using Twilio without connecting it to another platform first.
Since calls always come into my cell phone from the same Grasshopper number I just saved that number in my phone as my company name. So I always know when a call is coming in for my company and that it's not a personal call. Of course, all calls are saved and logged in Grasshopper so if I need to go back and check the actual caller ID I can do that.
All voicemails are immediately sent as audio files in an email to the email address on file for each extension. I personally love this feature. I can choose to go into the Grasshopper app to listen to them but its use so much more convenient to get an email, open it up and listen right from the email. The caller ID for the call is also included in the email text. So all the info I need for any missed calls is right there. Great stuff.
By far, one of my favorite features is the option to receive faxes to the same business number. Even though fax is being used less these days it is still used quite a bit and being able to receive faxes and having them immediately emailed to me is great.
The ability to transfer calls from extension to extension (as in cell phone to cell phone) is great. It doesn't matter where my colleague is. I can send the call to the right person and it's ringing on their phone in seconds.
Making calls from your Grasshopper phone number - Sometimes (well, most of the time) I'll just make a call directly from my cell phone because the process of opening the app, typing in the number I want to call and then making the call can take more time than the call itself.
Missed Calls - Myself and other coworkers have experienced frustration with Grasshopper and "missed" calls. Sometimes my phone won't ring, but I'll get an email with a voicemail. So it skips ringing my phone all together and goes directly to voicemail. I've had my phone in my hand before, ringer on, and never receive a call but received an email with a voicemail.
Checking Voicemails on your phone - In order to hear a voicemail from your mobile device, you have to log into the app. But the voicemail shows up under missed calls / voicemails like normal phone calls but when you try to listen to it, it's just a recording of grasshopper telling you that you have a voicemail.
Transferring Voicemails - You have to memorize all the extensions and the process for transferring voicemails. While it's just memorization needed to make the process work correctly, it takes a lot of time to remember how to transfer the call, the extension you want to transfer it to, and sometimes after going through all of the steps I accidentally hang up on the caller. It's user error, but I feel like if they made the process simpler, and they gave you a directory when you indicate you want to transfer the call, it'd make it a lot easier.
Authy does not support the "push button" multi-factor authentication from your application's native apps. This means if you want to use Authy, you still need to use TOTP based codes.
Not really a shortcoming of Authy, but it does nothing to help with multi-factor authentication using text messages - those are still sent to your platform's messaging app.
Authy doesn't always display how much time is left before your current token expires, making it difficult to know how much time you have left to enter the current code.
Professional edition works best for a small company with lower call volumes and is very useful but as you grow exponetially I think it has limited ability to do all the things we want to - SLA management, defect, release management to name a few. Reports and dashboards being available in real time.
We are happy with Twilio because the price per message is low. The API is not difficult to implement and the documentation is very complete. Twilio as a company keeps you well informed of issues that happen. They also offer free online workshops or conferences to make notices of new laws, etc.
I love that the Salesforce Service cloud provides all of the functionality that I need when implementing business processes for our customer support representatives. It even has enough functions and features that allow us to customize and expand upon our current processes, giving us the ability to go above and beyond what we've thought we could ever do. Using cases coupled with Salesforce's automation tools help ease the workload and keeps our data integrity intact.
Overall the product API is extremely well documented so it is very easy to build a product with their technology. The website is a little bit cumbersome to use as they have greatly expanded the number of products that they have over the years, but the dashboard UI has not been improved much since.
Salesforce's Trust Center clearly communicates occasional issues to anyone who subscribes, down to an organization's cloud instance. Bundled sandboxes ease updates, and seasonal upgrades are seamless, scheduled well in advance with plenty of information about what's coming. Support agents have noticed intermittent Omni-Channel disconnects due to internet connections, and these are clearly notified.
Load times can be slow, but this is also based on how much customization you have done. We added a lot of custom fields which could cause additional slowness in loading. This was never anything that affected our overall efficiency. I did not notice that Service Cloud slowed down any of the systems we had it integrated with
Twilio executes what it is designed to do: send SMS messages at scale while providing very good deliverability. I believe that Twilio is very good at what we use for adding SMS messages to our comms strategy. We can see those messages get opened and replied to, which is exactly what we are looking to achieve.
When I was setting up my account I contacted support a couple of times. They were also very professional, personable, and helpful. Their response is prompt and thorough. I'm confident I can get any question answered as well as help with any issue I might have. That's pretty important to me.
Salesforce offers support, although it generally gets routed to overseas support teams first, and once they are unable to help, it gets escalated up the chain to higher tiers. Frequently, the answer back from support is that there is no native solution, and we either have to turn to the AppExchange for some solution provided by another developer, or custom build our own solution.
Good interface to connect with different API systems for communication through different channel[s]. Twilio has good market coverage of the client across the globe for generating revenue through multi-channel approach. It works with [a] programmable feature that makes life easy for every user. Automated call is one of the advance[d] feature[s] of this tool.
Our in-person training was provided by our implementation partner and it was quite good. This was in part because we were already working with them and so it naturally leant itself to a good training relationship. And because they were building our customizations and configuring things, they could then provide training on those things naturally.
Trailheads are great but it was often unclear what actually applied to our organization. This made it difficult to get a whole lot out of it. Part of it is that because the basic Salesforce features didn't quite work for us, we had to add customizations, which then nullified a lot of the training.
I would go through an implementation very differently knowing what I know now. It was difficult coming from systems we liked in post-sales service and having to adapt to the clunky and underwhelming feature set in Salesforce. I would trim back our expectations
We moved away from Grasshopper when we implemented an answering service that had an application which provided the same functions as grasshopper for calling and texting. We initially selected Grasshopper as our communication solution because our original answering service just handled incoming calls and did not have an app available to clients.
Zendesk - I think it's not exactly user-friendly for the final user, but it's user-friendly for the configuration. So it's easier to manage when we have these amounts of data we're going through and it's more AI prepared. So by far Salesforce is more ready for what we want as the next level of hyper-personalization in sales and for sales.
We have looked at some of Twilio competitors, like Infobip, Sich and Bandwith. Prices on all of them for voice minutes and SMS are way cheaper than Twilio. But none of them seem to offer as many features and ease of use as Twilio. Specially from an API point of view
Positive, absolutely the speed to market and being able to get the product out there. The continuous improvement that we've been able to deliver in terms of small incremental developments, moving from basically a more rigid homegrown solution that they had where the turnaround time was about six monthly releases. We've got it down to three monthly releases of hoping to go to one month releases very soon. So just that whole speed to market being government, I mean that is just a major improvement in terms of what they've been able to do.
I think the negative part was integrating it and the complexity we had in terms of integrating DevOps as a concept and being able to use the Salesforce DevOps tools to be able to get that all rolled out in their existing current, very structured and rigid environment. And that probably took us a solid year to get those processes up and running. But yeah, now that it's working, it's absolutely fabulous.
We found that associates who had the opportunity to respond to a survey about their assigned job were 37% more likely to return to a job site
We were able to reduce the number of resources required to manually respond to associates using Twilio Studio, so those resources could have more time to complete other tasks
We were able to scale the number of associates who received survey messages at least by a factor of 8 without increasing our resource demand