MindTouch is a customer experience management platform with content management and help authoring capabilities. Formerly known as MediaWiki, it is optimized for building knowledge bases for customer self-service and agent assistance purposes.
N/A
Twilio
Score 7.7 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
MindTouch
Twilio
Editions & Modules
No answers on this topic
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
MindTouch
Twilio
Free Trial
Yes
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
Yes
Yes
Entry-level Setup Fee
No setup fee
Optional
Additional Details
—
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.
If a company doesn't want to make their knowledge base public-facing, you lose a lot of the value of using MindTouch in a closed environment. MindTouch is not ideal for extremely structured content management scenarios that are strong DITA advocates. Companies that require localization might not be good fits either.
I found Twilio to be excellent and very easy to use for a programmer in all aspects related to voice, SMS, and other features utilizing their API. I found the node client to be excellent and helpful. We previously used the Apex client for Salesforce before it was discontinued. Although we try not to use Twilio from Apex anymore, using that client was easier than implementing our own.
When we do have a support issue, we frequently need to go through multiple people, contacts, ways of explaining things, etc,. before someone on their end actually understands our problem. It's rare that the first person we talk to understands the big picture or appreciates our use case.
The draft functionality is a promising start but lacks some key features that cause us regular frustration. For example, you can only create one draft of a page at a time. This is fine if changes come to you in perfect sequential order, but it makes it impossible for us to update a live page while a draft exists. More specifically, if we're working on updating content on a page for a new feature being released next month, but then we notice a typo today, we can't fix the typo in production without first deleting the draft or doing some hacky workaround of temporarily copying/pasting the source HTML of the draft page and saving it someplace else.
Existence of, or integration with, true source control would be a huge win, but it's something currently lacking in the product. MindTouch's content reuse feature is helpful in the right situations, but it's not robust enough to scale well for lots of content.
Version history of page changes is not 100% reliable. Sometimes items don't show up at all or there is a delay before the diff is visible. Also, creating a draft does not register at all in the page version history.
In-site search is poor, unless you know the *exact* title of what you're looking for. We tell our customers to use Google, not the MindTouch search. Google is excellent at searching our MindTouch site.
Segment’s email identifier is case-sensitive, which is ridiculous because emails themselves are not case-sensitive. This means that if I send a capitalized email address in an identify call, it will create a duplicate user rather than matching it with the lowercase email. I think this is a technical oversight that should be corrected.
I’d like to see more information about the eventual transition of existing Frontline customers to Twilio Flex
I’d like to see some integrations between Twilio Studio and OpenAI or another open source LLM to provide automated responses, if this hasn’t been done already
I would like to be able to drag and move the actual lines connecting the steps in Twilio Studio, sometimes mine can get pretty messy
I think a Bug Report form would be beneficial for developers
We've put lots and lots of content into the MindTouch system, of course, so that makes it harder to opt out, but we're also very pleased with their rate of development and weekly pushing of improvements, as well as their response and solutions to our questions and input All in all, a winning combination.
Unless we can get this handled quickly -- less than 1 week -- we will likely switch to another provider who, in my opinion, we'll have to spend close to $3,000 in development time to build a new integration for texting. Our clients need texting and I feel Twilio has failed us miserably.
The site is responsive across multiple devices and screens. It has a clear path to contact support. The articles are searchable. Site users do have trouble navigating the site and finding what they need. That may be due to the architecture of the site, but it'd be nice if MindTouch offered more solutions are this. Our content is organized by product line. And many of those product lines have overlapping training content, so we have extensive duplicate content.
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.
MindTouch is a hosted site, so as a heavy user there are times when I notice that pages are slow to load, or something happens like Amazon Web Services crashing the entire east coast for a few hours, that you do notice even if it isn't actually the fault of the MT tool itself. It's the risk of using a hosted tool, but the benefits are pretty amazing and outweigh these performance issues.
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.
It's good. Pretty solid. We got a lot of input to get up and running, but did a lot of the setup and customization work ourselves, because of our high standards. We've gotten good response and results on specific projects related to customization and our CSM is also pretty responsive. Overall, I think that the jobs of CSMs and support folks would be easier if the product weren't wonky in some ways. They seem to have to do more "workarounds" for basic functionality that should just work out of the box
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.
Written documentation and videos are very good and have helped on numerous occasions when I've had to look up how to accomplish a certain task. The reason I have not given a full score is mainly because there have been some inaccuracies in the documentation because updates to the MindTouch framework have slightly changed the way things work. But this is usually the same type of challenges I face when making documentation for the software solution we develop. So all in all I'm very satisfied with both the personal webinars and the online documentation MindTouch provides for their service.
Just know that there is so much more involved than adding your content. There are so many pieces to launching your site -- especially if you are moving from another platform. If you are not a person who typically works in the "website" realm, do your homework, ask your web people, engineers, etc., because there's a lot to do that you won't know about until you are unexpectedly smacked in the face with it. Learn from my mistakes! We are very happy now, but it was a long road getting to launch day for us
I will be brief. DealerTeam is built upon Salesforce and we try to support native apps. We used Desk.com first for basic Help Ticket management. The product did not satisfy how our customers were looking for information. We upgraded to Service Cloud with Knowledge Base and spent one year writing content and developing our support agency. Again, our customers were upset about submitting help tickets and waiting for answers. They wanted access to self-help while working with a customer. Today we continue to use Service Cloud with MindTouch integration and have found complete success. There is simply no other solution I know of that is a flexible and easy to use as MindTouch when it come to providing customer success and product support
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 with Twilio now and have no desire to start over.
Our operational efficiently has improved significantly. Prior to Mindtouch, we managing duplicate content in two separate authoring solutions. Delivering content predictably and consistently was difficult and stressful for writers. In Mindtouch, we were able to optimize our content (remove redundancies) giving us more time to test, review, and improve content quality.
Traffic to our knowledge center is increasing monthly.
Internally, SMEs and customer-facing teams are recognizing the value Mindtouch brings through self-service knowledge. These SMEs want to contribute more to content, either as contributing writers or collaborators with tech writers.
