Salesforce Experience Cloud Formerly Salesforce Community Cloud vs Twilio

Salesforce Experience Cloud is well-suited for organizations that have clients who periodically or routinely need to access historical data or documents. The product also offers an exceptionally effective tool to engage with customers around support/service issues and the entire Case management functionality built into the Salesforce platform. The product might be less well-suited in environments where there is exceptionally high staff turnover within customer accounts, or where there is a substantial lack of very basic computer skills.

If you have a business page on Facebook, having Twilio’s chat not feature is a must! No more missed chat messages or clients getting upset because of a delay in replies. Twilio has helped on several occasions answer simple questions, so I didn't even have to answer the chat message manually. It also enables you to recognize when spammy messages are trying to get through.

• Complete integration with the Salesforce ecosystem. Data displayed in your Community portal reflects records from a Sales Cloud organization
• Highly customizable. A Community Cloud portal can be totally customized both visually and with different funcionalities with little to no coding skills required

• Easy to see my team in one place, when they log in and out and what call status they are in.
• Twilio is a simple, user friendly way to log in and out of work activities.
• Excellent services and support.
• The omnichannel feature which allows agents to get request from all channels.

• The documentation for implementing Experience Cloud can be a bit confusing as their rebranding hasn't made it's way into all articles, resulting in different terminology being used to refer to the same thing
• Some things are not as intuitive regarding their customizability, so there's a bit of a learning curve (i.e. Lightning apps can't be used to customize layouts in Experience Cloud)

• Setting up response sequences should be more intuitive like an email sequence software or a chatbot service where you can send users through flows based on actions.
• Less code setup or having a graphical user interface to set it up would be nice then to be able to just export the code of what we need and send it over to developers.
• Easier multi-media sending for images, videos, or files needed.

Usability is pretty streamlined, especially if you're familiar with other Salesforce products, but even if not, take it from me, as I just entered the technological space about two years ago, that this product is pretty simple to learn. You don't have to jump in with your head underwater. Small wins and learnings along the way are what foster long-term understandings and enable your evolution alongside the product. I definitely recommend Salesforce Trailhead along with it

Twilio has well documented APIs and examples. There are several tutorials, videos and Q&As regarding their services. So, usability is very good. I must say that advanced knowledge of telephony, API/Programming and error-handling is essential to make good use of Twilio. It's not just plug-and-play unless you are integrated with a system that has all of the programming built for it.

It's delivered on our original requirements and we've found ways to grow its usage. We continue to build on our original success and we can report our data out to leadership to show a true return on investment which is great for growing support and expanding uses for the system.

We have weekly calls with our Salesforce reps. They bring new ideas to the table and help with taxonomy builds. They have also answered many questions and connected us to the right people for us to grow our knowledge and utilization of the platform. They are a good partner overall in comparison.

I have not had to communicate with Twilio support in the last 3 years but my past experience with them has been very positive. They replied to my previous requests promptly and kept me well informed to resolve my inquiries. With their documentation that's available, I hardly imagine why anyone would need to contact support since it's all there in a concise and easy to understand format. It would probably take you longer to type out a support ticket than to just open their doc websites.

I have used Datatel/Colleague/Recruiter before. There were issues because only one person at the institution was able to have the student's record open at a time. This was problematic when collaboration between departments was necessary especially in the case of admissions, financial aid, and registration. We also had to do our work and then log out before asking a questions of another department. Sometimes simultaneous use was necessary. However, this was years ago and they may have since updated the program.

I receive regular unsolicited communications from Twilio competitors but I do not have the time to review them, given there is no reason for me to switch. Twilio works great and its pricing is acceptable for our situation. Investigating point solutions for text only or voice only would complicate our infrastructure and vendor management and would require some expensive system changes.

Being in South Africa, direct local currency support would be nice

• Improved online admission application completion rates from mid-60%s to mid-80%s.
• Positive user experience from start-to-finish to leverage one data system for all prospective student data
• Fewer data integrations transforming and loading sensitive student data by leveraging Salesforce Community Cloud to access already existing data

• Twilio WebRTC allowed us to move a bulk of our communication to the cloud, giving us a lot of visibility on how we were communicating with our customers.
• It also gave us analytics on how much time users spent on communicating with each other over calls and helped us build features around it.
• Twilio became the center of all communication on our platform. From chat messages to phone calls, it powered everything.