{"id":24414,"date":"2020-08-13T09:10:46","date_gmt":"2020-08-13T08:10:46","guid":{"rendered":"https:\/\/www.intercom.com\/blog\/?p=24414"},"modified":"2024-10-22T19:00:05","modified_gmt":"2024-10-22T18:00:05","slug":"boost-support-efficiency-with-intercom","status":"publish","type":"post","link":"https:\/\/www.intercom.com\/blog\/boost-support-efficiency-with-intercom\/","title":{"rendered":"Boost your support efficiency with Intercom’s new workflows"},"content":{"rendered":"

Yesterday we launched powerful upgrades<\/a> to the Intercom platform for support teams. Teams can now use Intercom to efficiently provide conversational support<\/a> for all types of questions, from simple ones to the most convoluted ones.<\/p>\n

This launch is a meaningful one for us because our Support team partnered hand in hand with the Product team to develop many of the features. We\u2019ve always used Intercom to provide support for our customers and, as our customer base has grown, we\u2019ve seen first hand the needs for better reporting and workflows in Intercom.<\/p>\n

“These new features have supercharged our team’s efficiency while preserving our customer experience”<\/p><\/blockquote>\n

The great thing about Intercom is that it\u2019s always offered great flexibility with its API. So over the years, we\u2019ve been able to build internal tools to cater to our team needs. With this launch, many of the features we built for our team are now available to you as well. These new features have supercharged our team’s efficiency while preserving our customer experience. Here are the top features that we think you’ll find particularly useful, plus insights into how we’re using them here at Intercom.<\/p>\n

1. Customizable Inbox views that help you track key conversations<\/h2>\n

It\u2019s now easier to find your most important conversations in the Inbox. For a long while, our Support team managers didn\u2019t have an easy way to gather all the conversations they consistently care about, such as those assigned to their team or those that pertain to a specific issue. Other teams needed a simpler way to find real-time conversations tied to their product areas.<\/p>\n

“We\u2019ve drastically reduced the amount of time and tools people needed to gather customer insights”<\/p><\/blockquote>\n

Managers can now create flexible and persistent views in the Inbox<\/a> for the conversations that matter on a day to day basis. Instead of opening a browser tab for each of your team members, you can now see conversations of the teammates that report to you in one place. Having this visibility into the conversations your team is dealing with on a day to day basis helps you better understand the issues people are handling, as well as the kind of coaching each person might need.<\/p>\n

\"Intercom<\/p>\n

You can also create custom Inbox views for different product areas, using the new conversation data attributes as filters (more on these later<\/a>). Teams across Intercom use these kinds of views to see in real time the type of questions customers are asking during a product launch, common feature requests by product areas, and features driving negative or positive customer feedback. By capturing related conversations in one place, we\u2019ve drastically reduced the amount of time and tools people needed to gather customer insights.<\/p>\n

2. Conversation reassignments that respect your team setting<\/h2>\n

Conversation reassignments now work better for large teams. Back when we were a small team, we could rely on each other to pick up conversations when we stepped away from the Inbox. Intercom\u2019s automatic reassignment feature<\/a> facilitates this workflow by \u201cunassigning\u201d team members from conversations when their away mode is turned on.<\/p>\n

\"Intercom<\/p>\n

But now our Support org comprise several teams that specialize in different types of conversations. Leveraging the old away mode had became a decision between helping the customer versus staying efficient. If we used away mode, a person had to monitor the \u201cUnassigned\u201d queue and manually reassign conversations to the right teams. On the other hand, if we didn\u2019t use away mode, customers had to wait for teammates to return before receiving a response.<\/p>\n

The new assignee picker solves this dilemma and lets you use away mode to its full potential. It now understands which team a conversation belongs to when away mode is on, keeping the conversation with that team while allowing another teammate to pick it up. Your team no longer needs to spend time reassigning conversations and customers benefit from faster response times.<\/p>\n

3. Our new best friend: the duplicate detection Task Bot<\/h2>\n

Out of all the features released, the one we\u2019re most fond of is the duplicate detection Task Bot<\/a>. This feature was actually first built by a former Customer Support Engineer on the team. Dubbed Vigilante<\/a>, it significantly reduced duplicate work on the team and was a major efficiency win. The bot caught the attention of our Product team, who knew many of our customers struggled with duplicate conversations as well.<\/p>\n

“Since we switched on the new bot, it’s helped us flag 80% of duplicate conversations”<\/p><\/blockquote>\n

With this launch, Vigilante \u2013 which we\u2019re officially calling the duplicate detection Task Bot \u2013 is now available to you as well. It not only scours inbound conversations for duplicates but examines replies to outbound messages as well. Once it spots potential duplicate conversations from the same user, it alerts you by adding internal notes to the relevant conversations.<\/p>\n

Since we switched on the new bot, it’s helped us flag 80% of duplicate conversations, saving our team 40 hours a week.<\/p>\n

\"Intercom<\/p>\n

4. New conversation data attributes to drive customer insights<\/h2>\n

Like many support teams, we spend a lot of time tagging conversations with existing customers to understand what kinds of issues the team is dealing with. We also tag to help Product and Research teams get insights into trending feedback and feature requests.<\/p>\n

But when you have a large team and a high volume of conversations, it\u2019s hard to ensure that every conversation gets properly tagged. Plus our Sales team has their own workflow for gathering feature requests from new customers and we were relying on a hodgepodge of ever-changing SQL queries to collate data for our Product and Research teams.<\/p>\n

Conversation data attributes<\/a> are more reliable than tags when it comes to categorizing conversations according to their product area, issue type, and level of urgency. Not only can team members manually collect these attributes as they chat with customers, but you can also have customers fill out these attributes automatically for you using bots, reducing the amount of work for your team internally.<\/p>\n

\n