Implementing Self-Service Support Tools

🧭 ITIL 4 Guiding Principles in Action Rolling Out a Self-Service Password Reset Portal 🔐💻 Let’s see how all 7 guiding principles play out in this one initiative👇 🔹 1. Focus on Value 💡 Ask: “What problem are we solving?” 🎯 Users are frustrated with long wait times for password resets. ✅ We plan to build a self-service portal that reduces downtime and boosts productivity. Analogy: Like installing an ATM so customers don’t need to visit the bank just to withdraw money. 🔹 2. Start Where You Are 💡 Ask: “Do we already have tools or resources?” 🔍 We check and find that our Identity Management tool already supports password reset APIs. ✅ So we don’t buy a new product — we integrate what we already have. Analogy: Like realizing your phone already has GPS — no need to buy a separate navigation device. 🔹 3. Progress Iteratively with Feedback 💡 Ask: “What’s the smallest valuable thing we can launch first?” 🚀 We roll it out to 10% of users (like HR), collect feedback, fix bugs, and improve UI. 🔁 Then expand gradually to the rest of the organization. Analogy: Like testing a new dish with a few friends before serving it at a big party. 🔹 4. Collaborate and Promote Visibility 💡 Ask: “Who needs to be involved and informed?” 🤝 We bring in Service Desk (who handle reset calls), Security (to review risks), and HR (first users). 📣 We document updates on Teams and Confluence for all to follow. Analogy: Like assembling IKEA furniture — everyone follows the same manual, instead of guessing. 🔹 5. Think and Work Holistically 💡 Ask: “What’s the bigger picture?” 🌐 We ensure the portal links with Active Directory, audit logs, onboarding guides, and knowledge articles. ⚠️ The change touches multiple systems and support documents — not just a single app. Analogy: Like renovating a kitchen — you don’t just change the tiles; you consider plumbing, electricity, and storage too. 🔹 6. Keep It Simple and Practical 💡 Ask: “Can we remove friction for the user?” ✅ Instead of multi-layered approvals, we use 2FA for verification. 🧼 Clean design: “Forgot Password → Verify ID → Reset → Done” Analogy: Like designing an elevator with just two buttons — up and down — instead of 50 options. 🔹 7. Optimize and Automate 💡 Ask: “Can we make this smarter over time?” 🤖 Add triggers like offering a chatbot reset option after failed login attempts. 📊 Monitor usage data to refine the process and user experience. Analogy: Like using a smart thermostat that learns your habits and adjusts automatically. ✅ Outcome: 📉 60% drop in password-related tickets 🙌 Happier users with less downtime 🕒 Service Desk now has more time to handle complex issues This is ITIL in real life — practical, agile, and always adding value. Whether you're in Ops, Dev, or Service Management, these principles scale. #ITIL4 #ITSM #GuidingPrinciples #DigitalTransformation #ServiceManagement #ValueCreation #Automation #ProcessImprovement

How did you handle support as a 3 person team? I often get this question about Userflow which we bootstrapped to $4.6M in ARR with 3 people. The answer 1. In-app onboarding - We of course used Userflow to build self service onboarding in Userflow. This included tooltip guides, a resource center and hotspots. By having great onboarding we reduced the # of support questions a lot. 2. Quality over fast response - Most customers like fast responses. But if the response does not resolve their issue, speed does not matter. we always got back to our customers within 24 hrs (and we mostly got back much quicker) and when we did it was with an answer by a founder who could provide high quality support. 3. A solid knowledge base - Whenever we launched new features or got recurring support questions we always made sure they were covered in our public knowledge base. In that way we enabled customers to help themselves. When we gave answers on support we often referenced these articles. 4. Fixed the root cause in the product - Besides covering recurring questions in the knowledge base we also made sure to fix the root cause of many questions by enhancing the UX in our product itself. Having the founders (including the founder who coded the product) close to support enabled us to do this. approximately 40-50% of dev time was spent on improving UX. Doing this had the highest impact on reducing our support load. 5. Scaled with an AI support assistant - When OpenAI came out with GPT4 we immediately built a support AI assistant that used our knowledge base as a source. Besides from using this ourselves it also became a successful feature of the Userflow product. #PLG #SaaS #Support

The Jira Service Management Portal will become a Self-Service Powerhouse! Status pages inside of Atlassian JSM will communicate service health and incident updates to keep your customers informed and reduce support ticket volume. During major incidents, technical teams work to resolve the root cause while service desks often receive repeated inquiries such as, "Is the system down?" Effective communication is as critical as resolution in ITSM. The latest Jira Service Management (JSM) portal announcements reflect Atlassian’s shift from a basic portal to a proactive employee experience hub. My favorites are: - 𝐍𝐚𝐭𝐢𝐯𝐞 𝐒𝐭𝐚𝐭𝐮𝐬 𝐏𝐚𝐠𝐞𝐬: JSM now offers integrated Status Pages accessible directly to users, reducing communication challenges in all Enterprise plans. This significantly reduces incident-related noise and duplicate tickets. - 𝐀𝐈-𝐏𝐨𝐰𝐞𝐫𝐞𝐝 𝐔𝐩𝐝𝐚𝐭𝐞𝐬 by Atlassian Rovo in JSM can automatically draft status updates and recommend appropriate stakeholders, streamlining communication during critical incidents. - 𝐑𝐨𝐯𝐨 𝐄𝐦𝐩𝐥𝐨𝐲𝐞𝐞 𝐋𝐢𝐯𝐞 𝐂𝐡𝐚𝐭: When a Knowledge Base article is insufficient, and a formal ticket is too slow, live chat provides a timely alternative. Employees can initiate a chat within the portal. If the AI agent (Rovo) cannot resolve the issue, the conversation transitions smoothly to a human agent. Agents have access to the full transcript and context, reducing the need for employees to repeat information. For leaders, these features represent a shift toward High-Velocity Service Management. Empowering employees to stay informed and resolve issues independently allows expert teams to focus on innovation and stability.

Your ServiceNow self-service portal has 12% adoption. Here's why. The portal works perfectly. IT tested every workflow. Every button clicks. Every form submits. But your employees still call the help desk. I analyzed quite some organizations with low self-service adoption. Same pattern everywhere: The portal was designed for IT efficiency. Not human behavior. Real example from last month: Employee needs a new laptop. Simple request, right? The self-service portal journey: 1. Find the portal (bookmark? intranet? email?) 2. Navigate to "IT Services"  3. Click "Hardware" 4. Select "Computing Devices" 5. Choose "Request New Device" 6. Fill 16 fields (half are unclear) 7. Submit 9. Get cryptic confirmation number 10. Wait in silence Time: 24 minutes. Frustration: Maximum. The shadow journey: 1. Message IT guy on Teams 2. "Hey, need a laptop" 3. "Sure, what kind?" 4. "Thx. Laptop delivered to your desk in 4 days." 4. Done Time: 2 minutes. Frustration: Zero. One client flipped their adoption from 12% to 89% with three changes: ✓ One search box on homepage: "What do you need?" ✓ Universal form: 1 form for all, 3 questions max, rest auto-filled ✓ Human language: "Get a laptop" not "Request Computing Devices" The portal became invisible. Which is exactly what great self-service does. ServiceNow has incredible capabilities. But capability without usability is just expensive shelf-ware. Your employees don't hate self-service. But they hate self-service that creates friction! 💡 Design for the human, not the ticket. 🔥 Prioritize experience. What's your self-service adoption rate? And be honest - what do employees do instead? ✏️ I'm your independent ServiceNow success partner. DM me if you're ready to move beyond 12%.

There were 176 work hours in August. WITHOUT automation and AI, RB2B would have had 350 hours of support tickets to handle. Can anybody guess how many total hours humans spent on tickets in August? IMPORTANT NUMBERS In August, we had 13,681 support requests. 13,359 (97.6%) of them were resolved by self-serve support. Only 322 (2.4%) needed human intervention. But, it wasn’t always that way. In April, with just 7,749 instances, 10.5% required human support. If we maintained April’s rate in August, our one-person team would have faced 350 hours of tickets. (August only had 176 working hours.) Instead, our team handled just 80 hours of tickets. “Wait… HOW?!” Glad you asked. ——— MY MISSION To do as much work as possible by doing as little as possible. When we launched, I knew we needed a robust support infrastructure to avoid being overwhelmed. The numbers confirm it. ——— THREE PRONGED APPROACH Leveraging Intercom, I implemented a three-pronged approach to self-serve support: 🔱 Intercom’s AI support agent 🔱 User-guided workflows 🔱 Comprehensive knowledge base My goal? Empower our users to solve their own issues. “Teach a man to fish,” and all that. ——— KNOWLEDGE BASE Our knowledge base is the heart of our support system. It’s where users first turn for help. It’s the brain behind our AI support agent. Writing structured articles is crucial. We use a custom GPT to ensure our content is top-notch for both users and AI. I'll share the link in the comments — feel free to use it. ——— REFINE REFINE REFINE I don’t always get it right the first time. I’m constantly: - refining our support docs - identifying where the AI stumbles - restructuring for efficiency ——— TAKEAWAYS “The best time to plant a tree was 20 years ago, the second best time is today.” If you haven’t reworked your support infrastructure, start today. In six months, you’ll be reaping the benefits. I can tell you this: I preferred spending 80 hours on tickets in August, versus the 350 hours I would have faced if we hadn’t planned ahead. Gosh.

Customer support teams don’t need more people. They need fewer wasted hours. Most of the time sink comes from repetitive questions, misrouted tickets, and jumping between tools. The result? Slow responses, frustrated customers, and a burned-out team. Here’s how to fix it: Help center articles that actually get used – a self-service portal only works if customers can *find* the answers. The right setup means fewer “How do I reset my password?” tickets clogging up the queue. Canned responses that don’t sound robotic – customers don’t want to feel like they’re talking to a script. A good system lets you send polished, fast replies without losing the human touch. Tags & filters that surface what matters – not all tickets are equal. Urgent issues get buried if your team is sifting through a messy inbox. Smart tagging makes sure high-priority cases get handled first. Routing rules that work behind the scenes – assigning tickets manually is the fastest way to kill efficiency. A solid workflow makes sure the right person gets the right issue—without support leads playing traffic cop. One inbox for everything – every second spent switching between tools is wasted. When email, chat, and social messages live in one place, your team moves way faster. Many tools will do this for you, but there’s a good chance you don’t have this set up yet. If you don’t, DM me—I’ll help you fix it and make your support way more efficient.

The cold start problem plagues many companies when it comes to creating a knowledge base. You know you need one, but where do you begin? Without a knowledge base, your team likely faces these challenges: - Frustrated customers who can't find quick answers - Answering the same questions repeatedly - Inconsistent responses to customer inquiries - Increased response times and support costs - New team members struggling to get up to speed A well-maintained knowledge base is crucial. It: 1. Empowers customers with self-service options 2. Reduces support ticket volume 3. Ensures consistent, accurate information 4. Speeds up onboarding for new team members So, how do you overcome the cold start challenge and begin growing your knowledge base organically? Here are five strategies we've found effective at ServiceTarget: - Mine Support Tickets. If you have a ticketing system, analyze historical support tickets for top preventable questions and unique solutions. These real-world problem-solving instances can become valuable knowledge base articles. - Analyze Search Data. Look at search terms used on your website or app. Failed searches or frequently searched terms indicate information gaps your knowledge base can fill, helping you prioritize content creation. - Leverage Existing Content. You likely have more relevant content than you realize - across your websites, training materials, PDFs, sales decks, spreadsheets, etc, which can form the foundation of your knowledge base. With ServiceTarget, you can quickly index your existing content and make it searchable through the knowledge base, leveraging it to answer sales, support, and customer success questions, and make it available to your customers, partners, and employees with the appropriate access levels applied. - Employ AI-Powered Solutions. At ServiceTarget, our AI Assistant responds to customer queries based on the confidence intervals you set. You can then audit the AI Assistant's responsesand publish them to your knowledge base or not, it's up to you. Our solution also analyzes customer questions and agent responses to automatically draft help articles, turning every interaction into an opportunity to expand your knowledge base. - Implement a "Write It Down" Culture. Encourage all team members to document processes, solutions, and insights as they work. This distributed approach captures knowledge across your organization, growing your knowledge base organically. Remember, a knowledge base isn't built in a day. Start small, focus on quality over quantity, and let it grow naturally based on real user needs. What strategies have you used to build your knowledge base? How has it impacted your business? I'd love to hear your experiences. #KnowledgeManagement #CustomerSupport #ServiceTarget