Please Install our extension to get started.
The Google Groups tool was meant to make it easy for people to work more efficiently in groups. With the tool, email ids such as firstname.lastname@example.org could be mapped to a Google Group comprising email ids of individual team members.
Anyone in the group could read and reply to incoming mail. Access was easy, right from the Gmail inbox. Not surprisingly, businesses using Gmail as their email platform adopted Google Groups for use especially by business functions such as Customer Support whose work is email intensive.
But the best intents and plans don’t always pan out as expected. And this has been true for Google Groups as well. It was not (and still isn’t) designed for use as an email client.
Its UI is quite different from that of Gmail or other Google applications. This means that it is not very intuitive to use, and users need to be specially trained. Nor has the tool’s UI changed much; the last major update was in 2015.
But the real challenge is this: although the tool is useful for sharing/broadcasting information within a group, its current UI and features do not make it truly useful for collaboration- even for Customer Support.
In most organizations, a team of customer support executives is responsible for supporting customers. When emails come in, one of the team members must respond within the stipulated time so as to comply with SLAs/TATs. Anyone in the team can respond, but it is important that:
Google Groups, which began as a collaborative space for online discussions, seemed like a natural solution when businesses started looking for ways to do customer support from Gmail.
While it does have a few features that would make teamwork a little easier, the real problem is managing Google Groups using Google's UI. Allow me to describe the problems for you:
All incoming emails go to everyone in the Google group. But unless the agent who responds to a customer mail copies his/her reply to the group email address, others in the group will not know that a reply has been sent or what the reply is.
This increases the risk that some other agent in the group inadvertently replies to the same customer email.
Not only is this a waste of the team’s time (the second agent could have potentially handled another customer email), it also increases the risk of annoying customers and reducing satisfaction- a key metric to evaluate the team’s performance.
The situation gets worse if two different responses are sent by two different agents to the same customer!
Using the Google Groups UI, you cannot automatically track whether a ticket has been closed or who from the team responded to a specific customer email.
When businesses are looking to automate processes and data capture, isn’t it rather inefficient to have to check with the team about the status of each ticket or to figure out who replied to an email?
There may be situations when an agent needs to check with a colleague who has prior experience in handling a similar customer issue.
With Google Groups, the agent seeking assistance will need to forward the email to the teammate; all these exchanges become part of the email thread.
If the company’s email policies/infrastructure are lax, agents may even be able to send emails to their personal addresses and from there to people outside the organization.
In addition to raising the risk of confidential information going outside the company, this can put the customer’s privacy at risk.
Unless every agent is careful to cut-paste only the final response onto the original customer email every single time, the risk of the entire email thread (including internal communications amongst team members) being sent to the customer cannot be ruled out.
Unfortunately, such “leaks” are more common than one would expect- or like.
Let’s face it- for businesses, not all customers are equal (though they really should be). Customers who contribute significantly to revenues or profits or are otherwise “strategic” are more valuable for businesses and accordingly, afforded priority treatment.
Or maybe there’s a customer who has had a series of problems (or the same one recurring). In all such cases, the support team will want to ensure priority attention and resolution.
The Google Groups UI does not allow emails to be flagged as a high priority. All that is possible is to send another mail to the group announcing the priority status.
You could, of course, shout out to your colleagues if they are close by, but you could have agents around the world or someone could be working from a remote location or maybe has gone for a coffee break!
Everyone swears by analytics these days, and yet, managing Google Groups with its native UI does not offer much information for generating analytical insights.
Managing customer expectations and providing them with support goes far beyond just replying to their emails in time; the content of the response is important as well, as is the time taken for the first response, tonality and factual accuracy of the email, follow-ups, etc.
There are so many factors beyond average response time that need to be looked at to determine the overall quality of customer support and performance of individual agents. And you just cannot do that with the current Google Groups UI.
This is a major lacuna for growing businesses that have diverse customer sets and are keen to learn from past mistakes and improve constantly.
Basically, Google Groups are sufficiently useful only when you have to broadcast information to a group of people. The moment you want to act on it by collaborating on the information, it becomes a mess.
Hiver addresses the above shortcomings and helps transform Google Groups into a powerful collaboration tool
It converts your Google Groups into shared inboxes — you can manage Google Groups right from your Gmail inbox.
Not only is it so much more intuitive and hence easier to use than the Google Groups UI, but it also provides various features that help the team do a better job of providing customer support. It also helps team leaders manage the team more efficiently.
Google Groups with Hiver addresses all the gaps described in the previous section and gives your teams the collaboration and information-sharing capabilities they need to take their performance to a higher level.
Specifically, when you use Hiver to manage your Google Groups, you can do the following:
Let’s look at how Hiver actually helps Customer Support teams achieve the above.
The moment an email arrives into your Google Group, it appears in the Hiver Shared Inbox, which is easily accessible from the Gmail sidebar.
Anyone who is a part of the shared inbox can access and process all the emails in the Google Group, so there is no risk of work being adversely impacted if the “Administrator” is on leave or not available. All it takes is two clicks from the Gmail sidebar.
Every member of the Group can easily see how many emails are unassigned, how many are assigned to him/her, how many have already been assigned and how many have been closed. This virtually eliminates the risk that an email gets missed.
Anyone in the team can access the shared inboxes from the left pane in Gmail to view assigned and unassigned tasks.
If someone wants to know the status of an open ticket or needs to find out who responded to an old email, you will no longer have to ask everyone in the team chat and rely on their timely responses (or potentially unreliable memories).
When an email is assigned to someone, the entire team will simultaneously know who it has been assigned to. Other team members can, if necessary, provide information to the individual or from a continuity perspective, get the email reassigned to him/herself. This also minimizes the risk that two (or God forbid, more!) agents respond to the same email.
Asking colleagues for help or advice when dealing with a customer situation is not a bad thing. But when you manage a Google Group using the Google UI, e-mails are often the easiest way to give a colleague the context and seek advice.
With Hiver to manage Google Groups, internal communications between team members become easier, less obtrusive and significantly less risky. Hiver offers the ability to write Email Notes that are chat messages that live right next to your email communication. The advantage is that they are not part of the email threads; besides, they are easy to trace and refer back to.
Using Hiver’s Notes feature, you can communicate with anyone who’s a part of the shared inbox. Notes are useful in a variety of situations, such as these:
Even if a customer interaction is closed, the Notes stay alongside the email conversation. This makes it easy to go back to old interactions as well (for training purposes or if they were handled by people who have since left the organization).
E-mail collisions are every customer support team’s nightmare. They arise because of blind spots, caused because nobody (other than the agent working on it) knows who is working on a particular customer email.
More information may be needed from the customer- and two agents write back asking the same question. The customer is annoyed, but replies to one of the emails. And then, the other agent follows up on his/her first mail, further aggravating the customer.
When you use Hiver to manage your Google Groups, the risk of e-mail collisions is all but eliminated, thanks to the Collision Alerts feature, which lets you know when someone else is replying to the same email or has replied a while back.
Lack of customer complaints does not necessarily mean your team is doing a great job. Studies show that less than 5% of customers speak up or complain about poor service. A majority of them simply move to competitors.
Hiver is useful not just as a communication tool for the team; it also provides relevant data that can be used to objectively assess individual/team performance, and thus ensure that your customer support levels don’t get hit.
When you use Google UI to manage Google Groups, the only data you can get is the number of messages received and sent.
Hiver’s shared inbox analytics gives you data to track metrics such as average response times and number of queries resolved. The latter is important because not every email sent leads to satisfactory resolution of the issue.
Also, because you can assign emails to individual agents, you can track indicators such as how many emails an agent takes on average to close a ticket, or how many tickets each agent is able to handle per day. You can compare data across months and shifts.
All this enables managers to objectively and transparently monitor the performance of individual members of the customer support team. As is often said, only what is measured can be improved.
Harsh is the content lead at Hiver. He's jocular, loves dogs, and is always up for a road trip. He also reads sometimes.