Front vs. Jira Service Management

I had a customer who has an urgent concern about their account. They already reached out to different departments but their resolution is unsatisfactory. [Its] good thing they tried to reply to our email campaigns and when a member of our team received it, it was answered and resolved quickly. Fronts really is a good tool to ensure timely resolution.

Incentivized

I think using a ticketing system is very easy to use and allows multiple teams to create help desks in the same portal. In terms of internal usage, I think this is a great option. However, suppose you're trying to keep internal items and external helpdesks in the same instance. In that case, this is not ideal, as there is no effective way to separate the two instances to protect internal data better.

Incentivized

• 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.

Incentivized

• Integration with many of the most common tools companies are using (Slack, MS Teams, Salesforce, ... etc)
• Natural workflow with Jira (as product development / project management tool) which makes the full fix and follow up of the tickets / issues very easy to follow
• Allow multiple different entry points and work flows for as many different needs your teams / company have

• 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.

Incentivized

• Navigating through issues outside of a kan ban board can be confusing and task heavy.
• It's easy to clutter up the tool. It could use some easy clean up capabilities.
• User interface is decent, but could use work to make it more intuitive.

Incentivized

We are very happy with Front and don't anticipate changing

Incentivized

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.

Incentivized

I have given this rating because, in my opinion, I don't see any downsides of Jira until now. We can customise workflows based on the project needs, including task workflows. Jira is very extensible, which is one of its most important features.

Incentivized

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.

Incentivized

I gave JIRA a 9 rating since for me JIRA works according to its purpose. Since there is a customer portal, our clients can leave a comment or communicate with us using the PR ticket that way it is easier for us to also request any additional information we need for our investigation.

I have only used Gmail in the past and Front is any day better than Gmail in terms of the interface and ease of usage. The ability to send scheduling links and comments between the email threads makes it better than Gmail. The shared inbox also makes it easier for the entire team to understand the kind of email each CSM is receiving and sending

Incentivized

Zendesk is a similar ticketing system that our organization used before JIRA Service Desk. The main drawback of Zendesk was that it can only be used as a cloud service. This means that our company data would be living on the internet at the hands of their security team. Another drawback of this is the price is significantly more expensive rather than hosting it yourself. Zendesk does have some additional features such as commenting on multiple tickets at once that JSD does lack. However, switching to JSD was significantly more cost effective because we have the ability and the infrastructure to host our own ticketing system, something that Zendesk could not provide. Ultimatley switching to JSD saved us money and allows the ability for integration with all of the other Atlassian Suite products that we use on a day to day basis.

Incentivized

• Saved our executive team considerable amount of time chasing support questions through different channels.
• Gave our team clear accountability for who was lead on a support issue and how to escalate.
• Customer regularly say our support is the best in the industry.

Incentivized

• It is definitely cheaper than Salesforce
• It allows the IT service desk to be more organized and respond more quickly to tickets, which can save time for both agent and requester.
• Some things are "not quite there" developmentally, so this means that internal IT will need to spend more time developing and testing the product.

Incentivized