Front is a communication hub that helps businesses keep the human touch in every interaction.
$29
per month per user
MindTouch
Score 7.0 out of 10
N/A
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
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
Pricing
Front
MindTouch
Salesforce Agentforce Service
Editions & Modules
Starter
$29
per month per user
Growth
$79
per month per user
Scale
$99
per month (billed annually) per user
Premier
$229
per month (billed annually) per seat (50 seat minimum)
No answers on this topic
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
Offerings
Pricing Offerings
Front
MindTouch
Salesforce Agentforce Service
Free Trial
Yes
Yes
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
Yes
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
Discount for annual pricing on Starter and Growth plans. Scale and Premier plans are annual price only.
MindTouch offers a unique knowledge and information management tool that was different enough from traditional knowledge bases and advanced enough to not be a Wiki while allowing CRM integration and APIs for customization. MindTouch as a company is focused on making their …
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 …
Much more user friendly. Better search. MindTouch contains built in content analysis. Customer support and onboarding from MindTouch far exceeds SharePoint.
I think Front is very useful for every company with multiple teams working together on different emails from clients. Not so useful if a lot of different teams need to work on a request at the same time, because when an email is sitting in multiple shared inboxes things can get messy. Also would not recommend for teams that work is individualized, as team work is the main point of Front.
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 think Service Cloud is best suited for medium to large operations that require both proactive and reactive service. It’s a great fit for post-sales support. However, I wouldn’t recommend it for very small companies because it can be quite costly, and many of the features may go unused. Salesforce also performs best when you have a capable team managing it, so it’s important to consider your organization’s size and readiness before starting. Once you do, I recommend exploring other parts of the Salesforce ecosystem—Service Cloud works even better when integrated with Sales Cloud, since it allows better visibility across teams.
Even if you are just trying to compose a single email, Front gives a smart system that has options such [as] organized templates, tags, alerts, [and] changing your outbound dpt email.
Tasks- with Front you will not miss any interaction. When you are required to get assistance from a coworker, you only need to mention him/her and that notification will appear automatically in their inboxes.
Smart Notifications- sometimes we are just overwhelmed about the several notifications on our devices that we tend to miss some of them, but Front offers a new way to notify every email, discussion, mentioning, or tag that you really would not want to miss.
Email to case is an interesting piece of it. The threading is very strong, sometimes too strong, but it does very well at handling the incoming emails.
The omnichannel routing, using skill-based routing is really effective.
Pathing. So making the workflow and helping the team understand what it is that they're trying to do, what they have to accomplish, those step-by-step pieces. That's really helpful.
Their integration to Salesforce is lacking. As the owner of our productivity tools and how they are used, I have very little control over what things to enforce, or even change what objects are available. For example, we don't use Cases in Salesforce but with the Salesforce integration the Cases object shows up. There's no need to have that there. I've heard there is a roadmap improvement forthcoming.
One of our uses is for our sales development reps to prospect with visitors. Because of the high volume of inquiries it's difficult for our reps to efficiently manage all their follow ups. It would be nice if we could run a "scheduled campaign" where a predesigned cadence of email follow ups can be sent automatically. To be clear, they do have a scheduling capability, but it just can't be used as a prebuilt option.
Integrations to other systems require you have a user account to those systems. We have SSO and therefore we don't always have a user account. For example, out integration to Jira uses SSO so we don't each have individual Jira logins. This is an outage for us.
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.
We had a principle initially to try and use Omni as much as we can from the user experience perspective, but have found that fairly restrictive. It was very difficult to actually get the right customer experience and customer engagement going. So we're actually on a journey at the moment to replace all of our Omni with Lightning web components that gives us that flexibility. That's probably one area where we've had some challenges in terms of how we've used the product out of the box.
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.
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.
It's very easy to understand and use by new customer support agents as well. Be it a technology, product, or marketing person, we have trained most of the company folks to read and respond to customer conversations in their free time with the help of the Front app. It is also easy to set up for an admin and manage his/her team with communication rules.
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.
I had Salesforce experience prior to using Service Cloud which made it a little easier to learn and navigate, but overall my team (some who had no Salesforce experience) caught on very quickly and found Service Cloud to be easy to use.
Working on an application that caters to customer needs requires a platform that acts as a mediator between the actual person and the client. This mediator handles the customer and resolves many of their doubts, helps them map through the entire process, and automates the processes. Such a platform is Salesforce Service Cloud. For queries that cannot be serviced by the platform, it creates a separate ServiceNow ticket for us, and it is assigned.
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.
The Salesforce Service Cloud generally has very good performance, however the overall new Lightning user experience can bring that down. For example, if you have too many tabs open, then it can take a while for the Lightning UI to load. This UI is probably not well equipped to handle loading of all of that information at once, but Users tend to leave their tabs open all day long. It can also be fickle depending on which browser you use, what extensions you have installed, and whether you've cleared your cache. This can be the downfall with any software as a service though, not just Salesforce
The support is good, and it's definitely prompt, but still lags when it comes to technical requirements, as I guess they are slow in developing newer features fast. So no complaints in terms of responsiveness, but yeah, at times it's not very helpful when you need certain features or are blocked on things which can't be unblocked.
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
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.
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.
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.
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.
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 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
This is something I am not familiar but it seems like it is [available] in Gmail. Thus I cannot give any feedback about it. What I am sure about is Front works for our team and I see Zoom using the service in the Customer Success Organization in a long run.
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 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 decision for us.
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.
We have cut our service team in half over the past 5 years due to the efficiency of the tool
The amount of direct inquiries to our technical team is less than 10% compared to the number support tickets that get entered in the system for them to work in a more organized manner
Responses are 100% more timely because tickets can be responded to by any individual in the queue or on the team, as opposed to direct emails to just one person
