At WeTravel<\/a>, adopting agile has allowed our small support team to focus on delivering big value to our customers. Rather than blindly following procedures and relying on team hierarchy to resolve issues, agile principles have enabled our team of eight to scale our support and process to handle hundreds of millions of dollars annually for over 3,000 global group and multi-day travel companies.<\/p>\n \u201cStrong support teams put the customer\u2019s needs at the heart of everything, from the processes they develop to the software they choose to implement them\u201d<\/p><\/blockquote>\n Adapting your service to this framework empowers your team to become more autonomous, solution-oriented, and fast, so they can swiftly resolve customer queries in a way that works best for them without impacting support team morale or productivity. By improving our internal workflows we\u2019ve improved our overall customer experience and helped our customers to spend less time and money on admin so they can focus on building meaningful relationships with customers to meet their expectations and reduce churn.<\/p>\n Strong support teams put the customer\u2019s needs at the heart of everything, from the processes they develop to the software they choose to implement them. Listening to your customers and weaving their needs into your solutions is key to providing the high-quality support experience they expect.<\/p>\n Agile and customer support are a natural fit; collaboration and communication are at the heart of both agile principles<\/a> and high-quality conversational support experiences<\/a>. Let\u2019s take a closer look at the nine agile principles adapted from the 12 principles of agile software<\/a> that we use to continuously improve our customer experience and support team workflows:<\/p>\n Your team should resolve customer queries as quickly as possible at all stages of the customer journey. At WeTravel, we use the Intercom Messenger<\/a> at key conversion points where customers have frequently shown a need for additional support. We also use relevant proactive messaging<\/a> to help new website visitors easily find the answers they\u2019re searching for while reducing the number of repetitive queries reaching our team. This frees up our reps to handle more valuable, complex queries that require human support.<\/p>\n \u201c<\/span>It\u2019s important to acknowledge when a customer hasn\u2019t had the greatest experience with our product, so they know we empathize with them\u201d<\/span><\/p><\/blockquote>\n To continuously deliver the right level of support, we always look to our previous conversations with a customer, including any notes<\/a> or tags<\/a> associated with these conversations in the Inbox<\/a>, to gain full context on their situation before we speak with them. This helps us provide better, faster support. It would be tone-deaf to attempt to resolve a customer query without fully understanding the bigger picture of where they are in their customer support journey with our company.<\/p>\n For example, if we noticed that a particular customer had recently experienced multiple bugs in our software, we would review their conversation history to get a better understanding of their situation before responding to their query. In that case, it would be best to provide timely, human support. It\u2019s important to acknowledge when a customer hasn\u2019t had the greatest experience with our product, so they know we empathize with them. We\u2019ve discovered that people often just want to feel that they\u2019ve been heard and for us to hold ourselves accountable for mistakes when they arise.<\/p>\n Agile methodologies encourage you to respond to change rather than simply following protocol. If your product team is agile, they\u2019re most likely fast-moving and shipping often. Regularly improving your product is excellent for customers. But when new features are frequently added or removed from a product, it can have the unintended side effect of rendering support materials inaccurate or obsolete.<\/p>\n \u201cAt WeTravel, we encourage our teammates to attend product sprint reviews to get the latest information on upcoming changes to our product\u201d<\/p><\/blockquote>\n It may not seem important to a busy support team to stay abreast of upcoming product changes. But to ensure that agents continue to provide accurate advice to customers, your team needs to embrace these product changes as opportunities to provide better, faster support.<\/p>\n At WeTravel, we encourage our teammates to attend product sprint reviews to get the latest information on upcoming changes to our product. By staying in the know on what features have been implemented, we can communicate these updates directly to the clients who requested them to create a more personalized support experience and keep support materials up to date.<\/p>\n Whether it\u2019s a macro or an article for your knowledge base<\/a>, teammates are encouraged to update omissions or inaccurate information in our support materials instead of waiting for someone else to do it.<\/p>\n Collaboration is the cornerstone of agile. We recommend sharing customer feedback with your product team and trusting them to make the right decisions for your customers when designing new functionality in response to this feedback.<\/p>\n \u201c<\/span>Tagging conversations is a convenient way of providing direct feedback from customers to your product team to highlight common feature requests and opportunities for innovation\u201d<\/span><\/p><\/blockquote>\n We regularly share customer feedback from our support conversations in the Intercom Inbox with our product team through Jira<\/a>. Tagging conversations<\/a> is a convenient way of providing direct feedback from customers to your product team to highlight common feature requests and opportunities for innovation.<\/p>\n The product team, project manager, designer, and developers then discuss this feedback to find the easiest solution to resolve the customer\u2019s underlying problem. Our support team has faith in our product team\u2019s ability to strike a balance between satisfying our customers\u2019 expectations and keeping our business on track by identifying the most impactful features to ship and adopting the right product strategy.<\/p>\n Hiring motivated people who are focused on solving problems is the first part of building a high-performing support team. At WeTravel, we have a thorough and transparent hiring process. Candidates speak with multiple people on our team (starting with the recruiter and ending with the CEO) to find out if they\u2019re a good fit for our company and vice versa.<\/p>\n Once your team is established, you need to give them the freedom to triage and resolve customer queries independent of rigid hierarchies. We encourage our team to make their own decisions and solve customers\u2019 problems in a way that suits them best while remaining aligned with our company values:<\/p>\n Allowing your team to be creative and take ownership of their solutions is empowering and can boost team morale and productivity<\/a>.<\/p>\n Face-to-face conversations aren\u2019t too plentiful these days, but you can use video calls for your one-on-one meetings, mentoring teammates, maintaining morale, and building relationships with your team while remote.<\/p>\n \u201c<\/span>Creating virtual office hours can help facilitate this virtual face-to-face collaboration while teams are apart\u201d<\/span><\/p><\/blockquote>\n Workflows, automation tools, and day-to-day rituals have all been impacted by the switch to remote working. So it\u2019s more important than ever to have regular check-ins with your team to help you effectively manage team dynamics and protect productivity<\/a> by maintaining morale.<\/p>\n Creating virtual office hours can help facilitate this virtual face-to-face collaboration while teams are apart. At WeTravel, we try to communicate beyond simple messages by using live chat, video chat, GIFs, and more to foster connection while apart.<\/p>\n For many support teams, CSAT, average response time, and time to close<\/a> are key metrics for assessing support team performance. Understanding the value of your support service isn\u2019t just about tracking cold, hard figures, it\u2019s about tracking the metrics that drive meaningful change<\/a> for your customers to foster loyalty, retention, and advocacy.<\/p>\n In agile support, solved problems are the primary measure of progress. Producing an effective workaround is sometimes better than an elegant long-term solution. Have the confidence to make these calls and try different approaches with customer queries until you find the right solution for the issue at hand. Leveraging self-serve and proactive support will win back time for your team, so they can harness opportunities for stronger processes or produce better support materials to reduce conversation volume and increase customer satisfaction.<\/p>\n Automate where possible. Where this isn\u2019t possible, prioritize. You should indicate which clients and problems are considered high priority and when to escalate queries. Understanding the context of customer queries will allow you to identify the appropriate points in your customer journey where introducing automation will maximize the amount of work not done by your support reps.<\/p>\n \u201c<\/span>At WeTravel, we\u2019ve implemented Custom Bots to capture leads and triage conversations for 24\/7 support\u201d<\/span><\/p><\/blockquote>\n By resolving simple, repetitive queries with automated bots or self-serve materials, and routing more complex queries to the appropriate support rep, you can protect your team\u2019s time while ensuring that they\u2019re having the conversations that move the dial for your business.<\/p>\n At WeTravel, we\u2019ve implemented Custom Bots<\/a> to capture leads and triage conversations for 24\/7 support. Automation ensures that all queries are routed to the right resources or team to support our customers even when we\u2019re offline.<\/p>\n Automated Custom Bots handle everything from advice to bugs to new feature requests. We\u2019ve found them helpful for prompting clients to give us as much information as possible up front, so our team has the context they need to quickly resolve a query before they\u2019ve even spoken with the customer.<\/p>\n We\u2019ve also found Macros<\/a> helpful for protecting our team\u2019s resources. These pre-written responses save time and energy that would otherwise be wasted on repeat common issues \u2013 you can close out queries in a few quick clicks with Macros.<\/p>\n According to agile methodology, the best architectures, requirements, and designs emerge from self-organizing teams. Self-organizing teams are empowered to make their own decisions and collaborate with people outside of their team to solve problems in a more meaningful way. Working with people at all levels of our company, from junior engineers to the CEO, exposes us to a wider range of perspectives and helps us create more informed, scalable solutions that increase customer satisfaction.<\/p>\n We\u2019ve found that in addition to providing a better customer experience, self-organizing teams have helped foster stronger relationships within our company. In a more traditional organization, where an agent can only talk to their manager or communicate with their engineering team through tickets, building personal relationships can be a challenging experience, and it can be difficult to learn from others.<\/p>\n \u201c<\/span>We believe that embracing a less rigid support team structure and building cross-functional relationships is essential to our success, particularly while we\u2019re all working remotely\u201d<\/span><\/p><\/blockquote>\n You can help your team to build relationships in the broader organization by facilitating proper introductions and providing relevant tools. We use Intercom\u2019s Inbox<\/a> for effective collaboration, it helps us to quickly loop teammates into a conversation using notes or search conversations by tags, users, teammates, or date ranges to get a big picture overview of the customer\u2019s journey.<\/p>\n This ease of communication helps us to quickly triage queries before approaching other teams to effectively resolve them. For example, if one customer experiences a payment processing error in our software and another receives an incorrectly formatted email from our platform, we know we can quickly decide which issue to escalate first. Sometimes we tag our engineers directly in conversations to help them understand the context of an issue ahead of speaking with them, but in this instance we know we could approach our engineers directly to get the payment issue resolved as a priority.<\/p>\n We believe that embracing a less rigid support team structure and building cross-functional relationships is essential to our success, particularly while we\u2019re all working remotely.<\/p>\nThe 9 principles of agile support<\/h2>\n
1. Satisfy the customer through early and continuous delivery of support<\/h3>\n
2. Embrace product change to provide better support to your customers<\/h3>\n
3. Support, product, and developers must work together<\/h3>\n
4. Build your team around motivated individuals<\/h3>\n
\n
5. Nurture your team with regular face-to-face conversations<\/h3>\n
6. Solved problems are the primary measure of progress<\/h3>\n
7. Simplicity \u2013 the art of maximizing the amount of work not done \u2013 is essential<\/h3>\n
![](\"https:\/\/www.intercom.com\/blog\/wp-content\/uploads\/2021\/06\/lVVnfoOY.png\")
<\/p>\n8. Collaborative, self-organizing teams produce better solutions<\/h3>\n
9. Reflection creates effective teams and processes<\/h3>\n