A LinkedIn Live series with IT leaders. Save a seat for episode 2 with Derek Rose, Group Head of IT & Deputy CIO, V.Group. Register Now

Start a new topic

Feedback on upcoming Freshservice + Slack Integration

To better support IT agent productivity & improve service levels for requestors, we are working on a Slack-Freshservice integration. 

Here are some of the scenarios we're considering:

- Allowing incident creation on Freshservice, from Slack : Requestors/Agents can create a ticket from a slack channel.

- Allow agents to receive notifications on Ticket Assignment/ updates/ upcoming SLAs etc (based on existing automation rules) on a Slack channel. 

- Agents can push an announcement created on Freshservice to users, on a Slack channel. 

- Send notifications to a Slack channel when a change/problem/release request is created.

We'd love your thoughts/feedback - specifically on whether the above functionality would be valuable to you. Also open to suggestions on any other use-cases you'd like us to consider.

(PS - Thanks Alan Burman for all your inputs! )

- Freshservice Product Team

5 people like this idea

Excellent, I already have mine up and running.  Thanks again.

Great start to the Slack integration. I imagine there are more features forthcoming? I wanted to add two that came to mind immediately.

1) Ability to start a Slack DM with the end user/requester and save back the conversation to the ticket from the time the Slack was initiated until a command is given, i.e. /freshservice-save

2) The documentation states "When someone sends you a message stating their issue on Slack via Direct Messages(DMs), simply type in the command /freshservice-ticket and hit Enter. Et Voila! The messages sent and received 24 hours prior to entering the command would be captured and converted into a ticket in Freshservice."

Two problems I see with this.

a) The probability that the messages from up to 24 hours ago apply to the ticket is not high. It is more likely a Slack conversation of 5 minutes will turn into a ticket for further research and resolution. If a user initiates multiple conversations in a period of 24 hours, all messages would all be saved back to a single new ticket.

b) End users/requests are not supposed to message/email individual users if there is a support question. It is more likely to have a public support channel, i.e. #tech-support, that multiple techs are able to respond to, whomever is on duty. But this public channel could get messy fast...https://goo.gl/HguR6P

Ideally though, an end user/requester could have the option to open a chat with the support tech(s) on duty. Slack or Freshservice would know who is on duty (probably via a command entered). A new Slack message would be queued to the next available tech. Something like...http://get.slaask.com/

Bottom line. Slack for notification of new tickets or updates is great, but for chatting with requesters, I think more than the current feature is needed before we'd adopt for end user chat support.

Hi great to see its here, but I think it needs a little work:

  • For the agent to have to type in "/freshservice-ticket" on each interaction feels and sounds cumbersome. It means that ticket creation from Slack is entirely dependant on the agent on the other end.
  • What I'd prefer to see is the end user be able to DM the FreshService Bot, then create the ticket themselves by completing the message with "/freshservice-ticket". 
  • Ability to rename the bot and commands to suit our support desk syntax would be hugely beneficial in driving adoption.
  • It would make more sense to cap the 24 hour message limit for ticket creation down to 10 minutes at most.
Currently in its current state we wouldn't roll this out as it would be seen as more of a cumbersome burden on the support them than an aide to provide better support with.

Excited to see where this goes, keep it up.

Also, the ability to use different commands instead of /freshservice-ticket or different bots, to assign to different groups would be extremely beneficial.

@Zuriel Reyes - Great to know that!

@Brendon McCarthy and Amonzure - Great suggestions. I have tried to address each of your feedback, do checkout out my comments below. 

Ability to start a Slack conversation from the ticket page is a great feedback. We will take it up in our next enhancement. 

The rationale behind having 24 hour timeframe is to give more leeway to agents incase the agent sees the messages 10 minutes or an hour later. The best would be to make it configurable. We will definitely revisit this and come up with a best possible fix. 

In case of public channels, conversations are many-to-many, it would be difficult to capture the right context, hence we support ticket creation only from DM. 

As we’re programmatically creating bot and commands, it is not possible to custom name them. We will see if we can keep the names generic.

We had a constraint in enabling end-users use slack command as Slack allow only authenticated users to slash command. And authenticating all end-users via Freshservice cannot be supported, hence we are authenticating only agents. 


Freshservice Product Management

Thanks @Viminya for the reply. Why it works the way it does right now is helpful. For us, we need a support chat feature in FreshService (FreshDesk has had one for a long time). We thought some sort of integration with Slack might be able to provide some form of this, but ideally a web-based chat support tool would work best. If this web-based chat creates a private DM with the support agent assigned (on duty), then the Slack integration as is current could probably work. At the end of the day though, however it is implemented, we require a support chat tool that does not require the end user/requester to have Slack.

Brendon - Take a look at Chatlio - https://chatlio.com. That's what we've been using to provide a live support tool that integrates with Slack. It works great although we still have to take that and manually create a ticket in FS. 

Login or Signup to post a comment