HubSpot Service Hub Knowledge Base, Part I: Misconceptions, Mistakes, + Opportunities

Do you live in a world filled with corporate data? Are you plagued by siloed apartments? Are your lackluster growth strategies demolishing your chances for success? Are you held captive by the evil menace Lord Lack? Lack of time, lack of strategy, and lack of the most important and powerful tool in your superhero tool belt knowledge. Never fear, Hub heroes. Get ready to don your cape and mask, move into action, and become the hub hero your organization needs. Tune in each week to join the league of extraordinary inbound heroes as we help you educate, empower, and execute Hub heroes. It's time to unite and activate your powers.

Are we activated yet?

Oh, we're.

Too excited.

Exhausted your powers? Yeah.

And fully activated.

It sounds like it, brother.

Well, good morning, everybody. As you can tell, we're just ready to go. What were we, Max? Terrified.

Fully activated now.

Fully activated.

Yeah. Terrified, tired and frustrated. And that's a new one. Excited to talk about HubSpot.

Yeah. That is a new one.

Yeah.

All the things.

Yeah. And I'm very excited about this week because Chad, after we hopped off recording last week, made a really good point. It has been a while since we have given love to the HubSpot service hub. Now, I personally have a soft spot for HubSpot service hub, even though I don't really get to use it. My entire background before I went into marketing for about eight, nine years was in customer service. And without naming companies, I will say, if you were asking for a supervisor, it was usually me. And I was really sorry and there was nothing I could do. Yikes. Oh, my gosh.

No.

Service team. One of the things I love about HubSpot Service Hub. And George, I'm going to have you give a quick primer on it here in just a moment.

Yeah.

But one of the things I love about HubSpot is, is they went out of their way to make sure service teams who are so critical to the life cycle of customers get love, get support. Because as someone who has been in customer service for a very long time, the tools are usually just trash. Like it. It's awful. So, George, before we dive into today's conversation about the knowledge base.

Yeah.

As I was putting today's conversation together, I could not help but wonder how many people are really that familiar with the HubSpot service hub. Maybe they've. Maybe they've heard about it, maybe they haven't, but just give us a quick primer on what it is. And just in your experience, are we still seeing folks maybe not jump on it as quickly as we think they should be?

Yeah, it's interesting because part of the answer might even be in the way that you maybe mistake stakingly or. What's that? Freudian slipped. How do I.

Yes, it's a Freudian slip.

You're like knowledge base. Whoa. Hey, hey. Service Hub is way more than that. Right. A service hub has grown into kind of this all in one obviously toolkit. It's, it's, it's about delivering exceptional customer service, but it's also become really about communication. And dare I even say that when I think of the service hub, it's like relationships and there's a lot of things that have been built in and added over the last six months to a year that you might have been sleeping on it. And you're like, holy crap, I didn't know that it did all that. And what I would say is I want people to think of it as a bridge between the teams and the customers that they have to service and, and the tools that they need like ticketing, live chat. Liz, you mentioned knowledge base, customer feedback surveys, the automation as part of the tool. And, and so like think about how can we support or service these humans in a way that it just becomes seamless and in HubSpot's words, delightful. That's, that's how I would say it. Now here's what I am also going to have to throw out here. If you go over to HubSpot.com forward/products, forward/service-varb. I'm not sure what VARB stands for, ladies and gentlemen.

Barb.

Yeah, but, but if you open up the product description of the product that I just described, it says customer service software powered by AI to scale, support and drive customer retention.

AI.

Cheers. Thanks. Like. Anyway, so, but, but it is a suite of tools that a lot of organizations and, and by the way, I'll add in very smart tools lately that, that people need to just not be sleeping on and be checking it out.

Yeah.

Chad, what are your thoughts on that? I know you have a soft, you also have a soft spot like me for Service Hub. I'd be curious your thoughts on adoption and whether people are actually kind of like catching the vision of what it really is.

I don't think that a lot of people really truly understand the depth and configurability of that tool. And I think that also stems from the same kind of issue that a lot of CS reps feel when they work in customer success and customer service. Like some people use service based tools for customer success. Unfortunately, some people use sales based tools for customer Success too, which that's a whole nother couple of episodes. Diving into to some other things like the CS workspace, which is built on top of Service Hub, like not on top of, but adjacent to Service Hub to get people out of Service Hub who don't belong in Service Hub. Because a lot of people end up putting a lot of processes into Service Hub that don't belong in Service Hub. Right? But I would say like the issue that I end up seeing a lot is it's quite configurable to fit a large array of businesses as with most of HubSpot, right. And because of that, and that's the same for many, many service tools out there, right? Many service tools have this problem where they are poorly configured because I don't think they have like an internal user journey map for all of the weird types of problems that come in and a good way to handle the stuff that doesn't fit the map. Right. This is this type of an issue. It should do these things. That's that type of an issue. It should do these things. Here's our other bucket. And we got to like have a process for cleaning up everything that's left over that didn't fit what we were expecting to handle. And I think when people like don't have those things built into whatever their service tool is, let alone HubSpot Service Hub, you know, it causes issues of like not being able to use it that well. And like people don't realize that now HubSpot is really trading blows with the big boys in the, in the marketplace, with the Zendesks, with the intercom, with, you know, like all these different tools out there that really are known as the industry standard for service ticketing. There might be a few things here and there that that can't quite do comparatively, but it's really trading blows. And like if you're asleep on it, you know, like now it's going to be able to be configured to do those things. But also know the rest of your customer journey to give you that much more insight because like a lot of times right now, man, a support ticket problem comes in and it has anything to do with sales, you gotta chuck that sucker over the fence and wait for somebody in salesforce, you know, to tell you whatever happened in the sales cycle, right? So you can get an answer back to this customer. Like what do we actually sell this customer? Right? Yeah. So if you're asleep at the wheel on that, man, we have some really cool stuff in Service Hub in general now compared to what we had even literally 612 months ago.

Max, what are your thoughts?

Yeah, I mean, I think we did just see in HubSpot's earning call that the recent one they just had, that they're selling more platform than ever, which means they're selling marketing, sales and service more than they ever have. Um, however, I don't necessarily think that's an indicator that people are less, are sleeping less on the service hub. Right. I think it's more of an indicator of people like to save money and you end up saving money when you do the bundle. Right now to be fair, you know, in that last year that I worked at HubSpot as a, as a se, I was seeing a lot more people come to HubSpot for the first time trying to run their service team on it than I had in the past, which makes a lot of sense considering the tool grew up as a marketing tool, then kind of transitioned into a sales CRM. And yeah, you know, the, the, you saw service hub stuff continue to kind of get piled onto it and like now it's, you know, it's trading punches with the, with the bit, with the big ones. Right. But do I think the same age old problem that we've seen where, you know, folks still look at customer success or customer support or, you know, any sort of part of the organization that's just dedicated to helping customers is a money maker or like a money pit? They probably still see it as a money pit and they probably rather put a lot more of their money into marketing and sales because to them it's easier for them to draw a line to this helps us make money versus the more and more we just take care of people. We're wasting money and not making anything right, which is a really unfortunate way to look at.

Not the way to look at it.

Not the way to look at it, but unfortunately it's the way a lot of people look at it. Right. So I'd like to see that really change. I'm hesitant to say that it will given that we're torpedoing ourselves into some pretty tough economic times and people are going to be making some decisions on where money goes and what's valuable. And you know, I don't think that bodes well for the provide good service to people, you know, thing at least in terms of like the way people are probably thinking about where they got to cut costs and stuff like that. But I think the folks that really understand the value of doing right by your customers and taking care of your customers and the positive impacts that that have might also realize it's going to be one of the most important things that they can continue to focus on doing as we head into a time of uncertainty and turmoil and things like that. Right.

You know, so, so let's dig into the specific piece of service hub that we're going to be talking about today, which is Knowledge base. My Freudian slip gave that away earlier. Oops. But George, what's the tldr, the quick summary of what knowledge base is or maybe in your mind what people think it is versus what it should be.

Well, let me even, let me even take a step back because I want everybody to realize that first of all, Max, you're talking about these like times of uncertainty, which, which really leans into the conversation about maybe having a system where you can do a self service experience. Right. You can provide more with less. And so while we're going to dive into the knowledge base, we can't really have this conversation without talking about the Breeze customer agent and the fact that the new knowledge base, which I'll allude to here in a minute, can be powered by the Breeze customer agent. And also if you've been paying attention that, which I'm sure you have been, that the customer agent is actually being pulled outside of even the service hub and going to be kind of like a thing that just can be jamming along, along the way. So just you know, like between Breeze customer Agent, between help desk and ticketing, between like omnichannel messaging, between call tracking and then of course, knowledge base. Like there's a plethora of things that you can create a self service experience and, and augment the humans and the process. Right. Yeah, Max.

And not to, not just spoil anything.

Yeah.

But customer agent has a new best friend.

Yes.

Very related to the topic that we're talking about today.

Yes, go ahead.

Knowledge base agent.

Yes.

Which is frankly one of the craziest things I've ever seen.

Yeah. Don't know what to write anyway.

Yeah, it's in your CRM. You know what I mean? Like it's there. I'm sure we'll get to it. Yeah.

Yeah.

So that's the first thing I want to do is for anybody who has tried Service Hub historically is the old knowledge base. Like that's not where it's at and you really need to think about how to. And if you have been using it, how do I go from the historic knowledge base to what is the bridge, you know, like the, the beta version of the knowledge base because that's where it actually will work. With the knowledge base agent, the customer agent, all of that. And so that's the first part. But, but knowledge base, listen, literally it's, it's. And, and people use it in different ways. So I'm curious how Chad and Max will throw down on this as well. But when I think about a knowledge base, it's a place where I can create content that I can use in the service process or people can Google. We've all done this, Googled and we end up at knowledge, you know.HubSpot.com and there's a knowledge article and it's where we can educate people on the intricacies of doing business with us using a product we might have or a service we might provide. And so it's like step by step. And when I think about the HubSpot knowledge base, it's like this might be text, it might be image and text, it might be image, video and text, it might be links to other things. Like there's, there's just so much. But think of it as a repository. Maybe the cousin or brother or sister, I don't know. Use whatever analogy or metaphor that you want to. Like your, your blog article, right? If you're, if you're doing some type of resource center with blog articles, it's like that, but different in particularly like a deeper customer centered scenario. So that's just knowledge base in general and some, some pieces that come to mind.

Yeah, I think that the, the way I always like to think about it is that it's a heat shield for your human beings that actually help people with problems. Right. So like there's this concept a lot of like ticket deflection, right? You see it a lot with like customer agents. Knowledge bases or not knowledge bases? Well, yes, knowledge bases, but you see it a lot with like, you know, chatbots and, and the earliest version was an FAQ section of your website, right? It was a list of. A list of questions people asked you frequently. And if they were asking you those questions frequently, it means you were frequently taking people away from doing their job to answer them. Right. And so like knowledge base is the, you know, the, the ultimate version of that. Right. But it still serves the same purpose, right? One. Sure. People like we are in an age where people would rather not talk to you human being and find out on their own. So it solves that piece of the utility, right. But then the big piece is that you got to remember how much time is taken away from your employees from doing really important hard stuff that they need to do. Right? Answering the same questions over and over and over and over again, right? So they call that like ticket deflection, right? Where instead of, like, opening up a ticket and taking someone's time, you're deflecting that away. It's acting as like a heat shield, right? So you've got all these people coming at your customer service folks with all these questions, but 90% of them can be answered in an article, right? And the whole idea is that if there's 10% of those issues that are really difficult to solve that you can't just solve with an article or telling people what the answer is, right. It's going to be really, really, really difficult for your limited amount of customer success, people with a limited amount of time to be able to focus on those 10% of really, really bad issues when they also have to focus on 90% answering the same question over and over and over again, right? So, like, the physics of it is the knowledge base. Heat shields, all of that time and wasted effort that people would spend on bullshit that can easily be answered in an article so they can focus on the tough stuff, right? And so those really tough problems don't end up becoming really, really big ones.

The only thing I want to point out, though, and this, this is taking me back to the time when I used to manage a customer service team. And I'm about to bring up one of your favorite words, George, and that's mindset. Well, I understand tactically what we're saying about it being like a ticket deflection. I have found, like, whether I was training service teams or creating documentation for service teams, the more we use language around the idea of trying to prevent us from talking to our customers, the more I noticed our service teams did not want to talk to people and would actually act annoyed anytime the phone rang, particularly if it was something valid. So there is, like, it's a. It's all about messaging, right? Which we know is one of my favorite things. And I'm not saying it's spin. I think it's more important to think about, like, how are we giving our customers the best experience possible and making it easy for them to get their problem? So I'm not, by the way. I'm not saying that you are.

No, I get it.

Deflect, deflect. But, like, I've noticed that little subtle language shift is really important because inside those teams, and I used to have to call the people on my team out on this all the time. I'd see one person pick up the phone like, oh, God, I'M like, no, no.

Well, those people shouldn't be working customer service.

But that's the thing, though. Service teams, depending on the size of the organization, tend to be very densely populated. So you can have a number of folks who actually would be fantastic in that role. But given the pressure they're usually under, given the fact that they're often under resourced. But negative energy and mindsets are incredibly toxic because they are also very contagious, even with your best performers. And so that's where the language around how you use these tools gets so critical. Because I had one person, the one person I was thinking of, I'm like, yeah, she didn't last like two to three months, but her damage was lasting. And it started with, well, why are. Oh, God, these people are so stupid. Why couldn't they just look it up on the site like it's, it becomes very problematic very quickly depending on how you talk about what your relationship with your customers is.

Oh yeah, 100%. But, and, but in the thing is, is like a lot of the times when we talk about ticket deflection. Yeah, you're. There is a, there is a concept of, yes, free up their time so they can focus on the really hard stuff too. But there's also this whole, you know, managing burnout and building negative sentiment. Right? Because think about that same frustrated customer when they pick up the phone seven times in a row for people trying to figure out how to reset their password. Right. That's only going to make that ten times worse. Right.

See, I want to.

I agree. It's not about, it's not about. When I say ticket deflection, a lot of that sounds like we don't have to deal with them. Well, no, it's not that.

It's, it's really empowering the customer to handle it. Right.

Yeah, it's all in how we talk about it.

Yeah, for sure. And you also, like, you have opportunities to create really good experiences for them, right? Because when they go, wow, I went to their knowledge base and I found an answer to my question in a second and I was able to solve the problem. That feels way better than, oh, I, like, had to wait on hold to get on the phone with somebody and they told me something that like, ended up being super easy, but it took me five hours to figure out the answer. Right? Oh yeah, like, and so like that to me it's, you know, the, the deflection part is more like avoiding all the negative stuff that comes from just having human beings be the bottleneck to be the answer. Right. And the negative effect that that has not only on the customers. Right. But on the actual reps themselves. Like, that is such a grueling job. You get it. You've seen probably the nicest people in the world turn into monsters at the end of the day from answering phone calls. Right.

I mean, you would be surprised. Like, so I'll. I'll name it. It's been years and years now. I worked at a cut. I ran a customer service team at a very small publisher. It was only like three or four of us and we dealt with the same type of negative energy. And I was also a supervisor at a call center for Comcast.

Like, I have done the Spectrum.

Oh, yeah.

Oh, I can tell you, you were working, you were very sorry and that there was nothing that you could do about it.

And I literally was sorry and there literally was nothing I could do. Like, it was absolutely tragic. So, like. But what's fascinating about it is that I think some folks listening to this conversation might say, oh, well, we don't have a big customer service team, or, oh, we have a big customer service. I will tell you, the problems were the same, the volume and velocity. And I will say there was a distinct difference in company culture. But, like, you see the same things, like service teams, whether it's a team of four or a team of 400 across a massive call center floor, you have more in common than you think you do.

Yeah.

Now, I want to move this conversation along here because we've already started dipping our toes into this part of the conversation. But I'm going to throw this out to all of you and whoever wants to jump in first, go crazy. I want to know about the biggest mistakes companies are making when they're building out their knowledge base, especially when they're just getting started. I do have a little baby one that is not very exciting. So I'm just going to throw it out. Organize your stuff, organize it and name it consistently. It's like when George talks about folders and because you talk a lot about how to do, like, data hygiene and make it proactive. Yeah, I have noticed. Whether it's an internal, only an internally accessible knowledge base or only an externally accessible knowledge base, how things are titled, how things are structured, are entirely dependent on the individual who created that piece. Because nobody sat down and said, hey, here are the rules. And it makes, especially if you have a knowledge base that's customer facing, it makes it look really unprofessional.

Yeah.

So that's my little one.

Organization is key. Chad. Chad and Max, I'm curious to your answer on this one. I too have some things that I want to throw out there, but what do you guys think?

Yeah, I mean, I still hate the argument. I hear of people going like, oh, we don't want to put too much on the knowledge base because then all competitors will somehow be able to destroy inside out. Chill out, dude. The thing is, it's good to have your knowledge base open to the public because again, in this day and age, you know, trying to get a sense of what support's gonna look like is something that people think about when they're buying stuff. Yeah, right. So, like, show them, hey, we got the answers if you have problems, right? Like, if you're unsure how it works, here's a place you can figure it out, right? Yeah. Instead of this whole like, oh, we think that if someone sees some screenshots and questions about how the product works, that all of a sudden we're gonna get destroyed. If you really think it's that easy to like, take your company down because you posted some knowledge base articles about stuff works, there's. You're. You're ignoring bigger problems somewhere else. Right? So I just, I hate, I hate hearing that, you know, and still there's like people that just, you know, they just still just ignore building the knowledge base in favor of just having some insane ticketing system that is difficult to manage.

So, yeah, Max, to your point, while it looks like Chad is about to like drop some wisdom there, but I'm gonna let it.

Buffering more.

Yeah, Buffering.

No. I had a client last week I was working with, and it's still surprising to me how much fear is baked into the content that, that people and companies will create. So, for example, they have an incredibly talented team, a team who is publicly displayed on their website. Everybody knows who they are. And in a piece of content recently, he wanted to talk about the fact that, like, when we say our people are greatest differentiator, we mean it. And then he wrote it and went, no, this is too good. Our competitors are going to come and pick off our people. I'm like, what? I'm not going to talk about this in a piece of public facing content that would help you make money. We ended up striking the whole section, but wow, Brutal.

Now.

Crazy, no?

Yeah. All right, well, I completed my buffering. I was buffering.

Buffering.

Thank you.

Right. It's. It wasn't 4K, unfortunately. I think I was only buffing buffering 480p.

But how's that DSL line holding up?

Yeah, I'm just, I'm traveling right now. So I guess the old dial up, you know, can't talk on the second phone line. Anyway, I was thinking, like, where my brain's going is like actually just in the actual config because, like, obviously I'm just a turbo nerd and like, I've been the guy who's actually like, set up HubSpot knowledge base. Like the frameworks and the fold, like, you know, the folders and the styling and like, you know how it's basically like a CMS webpage toolkit. Right. And just for, for the listeners out there, if they don't know, like there was HubSpot knowledge base. I don't know, I'd probably call it 0.5, to be honest. But there was a V1 and then there's like a V2 knowledge base, right, that they have where it has additional styling and a better drag and drop manager and more options and like that knowledge base, if you were on the old one, even though they released a new one, you had to like create a brand new one from scratch to get on the V2. But now they finally have like a migration tool where they can migrate your old one to the new one. So if you were stuck on the old one, saw the new one, couldn't get on it. Keep in mind, there's a migration tool now, but it has to do with like, really making your knowledge base feel like your brand, which I feel like is a little bit difficult in the HubSpot knowledge base, if I'm being perfectly honest. Like, I feel like I can't get it, you know, to stop, like style, like, oh, like the webpage, you know, you really gotta like, put a lot of dollars into it if you want to try and get the HubSpot knowledge base styled more differently. I know there's some like, themes and templates and things out there, but like, usually your website theme company doesn't always pump out a knowledge base theme in addition. Right. Or anything like that. Right. So it's hard to get it to feel like the same functionality or like same. Same Persona, I suppose as your brand. It almost feels like it's the, the. I don't know how to say it, like the, the offshoot, the less well kept, you know, less looked after, little website page that is on a subdomain, you know, help.yourdomain.com or whatever.

It's like showing up and like it's that movie where you're driving out west and you end up at the gas station and you're like, yeah, wouldn't go up the hill. Like, it's just like, okay, where am I now?

Oh, the knowledge base is up the hill. I mean, it's cool. Yeah. Once you get up the hill now there's like the customer agent where you can ask it questions and it'll scan the knowledge base for you because the search is typically stunk, you know. But now like the customer agent can be trained on your knowledge base articles. That's particularly helpful. Right? And like the chatbot is way better than it used to be. And they even at added another thing where you can like in the chatbot directly search knowledge base articles without having to go dink around in the knowledge base, which is also particularly helpful if you have a specific service chatbot you want to deal with. There's a lot of really great features making the spooky thing over the hill, you know, a little better. Right. And a lot better experience than it used to be. Which again is why I continue saying that like, we're really starting to trade blows at a very meaningful level with the bigger players in this particular category, especially like around, even the, in getting the information to the customer. But right now all it is is like a repository of web pages that isn't as aligned with your brand as I feel like you would want it to be stylistically, which, which, which by.

The way, I'll actually throw out there a couple things. First of all, time flies when you're having fun, but if you, if you go to your like HubSpot portal, go to the right hand menu, go to product updates and filter by app, and that's knowledge base and products Starter, whatever you're gonna see, like customization tools, they, they launched, let's see, March 12th. So what's today later than that? It doesn't matter.

You're.

Who knows when you're listening to this, but customization tools for the new knowledge base, right? And, and it does talk about themes, to talk about navigational menus, it talks about the editor, it talks about management. So I, I think it would behoove you to go dive into that and see what you can do with that. There's also some, some additional article links in there that you can dive in a little bit deeper. But holy crap, I can't believe that. We're almost running out of time and I want to be as the content kind of nerd guy or communication nerd guy, which, by the way, I think Max Chad gave you your next hat idea with. He said what did he say I forget nerd. How did you call yourself?

I don't know, something about a turbo nerd.

Turbo nerd. I think, I think there should be a hat that I'm a turbo nerd. I think that's a new hat idea. But I want to talk about curse of knowledge for a second because when you go to write these articles, what I would beg you to add in is the mindset of simplifying the complex. Because you can't write a knowledge article based on your expertise to show off how knowledgeable you are about the thing. You have to write the knowledge article in a way that I, the human, the non technical person, the person that doesn't work there, the person that doesn't even know that I should reboot before I call you that kind of person. Like I can just read it and I get it. And so you've got to get out of your curse of knowledge. And I don't know if this is by having somebody else that is not you write the words that you dump out of your brain or if you use some type of AI assisted solution to just simply say, hey, take this information that I, the turbo nerd have put in here and simplify the complex for the humans that might be reading it. It's totally up to you, but we've got to step out of the curse of knowledge and we've got to, especially for customer knowledge base articles, simplify the complex. And this is one thing that I will say that I love about what HubSpot is doing too is like you can have an article and then link to or show a video because it's easier to show some things than to tell some things. Anything you tell needs to be simplified. Anything you show should be simplified, but can go to the next level. So if you start to think about that in like putting those kind of mindsets, if you will, in your arsenal of content creation around knowledge articles, you will be far better off. Because here's what's, here's what's worse. I, the customer am frustrated. I have a question. I Google it. I read your knowledge article. I am now even more confused and more frustrated. And now I get on the call, oh my God, like please do everything you can to make me less confused and less aggravated. Even if I do still have to call George.

I have to double click on that so hard because I was going to bring that up. So. Another company I worked at for customer service was Living Social. I was the team lead in one of their customer in their customer service department. But that was also actually where I got into copywriting because I noticed that we were creating internal and external documentation because we used to do like massive national deals for like Starbucks and like people would go nuts and we were getting flooded with calls and the difference in service level that we were able to provide customers when we went from, here's the deal, these are the details, this is what you need to know to creating a piece of content, a piece of documentation that made it easy for them to understand the what, the why, the how and visuals. Like, it changed everything in terms of what we did. The other thing too that you brought up is that the curse of knowledge is very real. I think we see this in regular content, not just customer service content. But you should have the same content strategist mindset. When you are creating a piece of content for your knowledge base, if it's front facing. Those are the same customers you were marketing and selling to. My guys and gals and everybody else, you know, like, they're the same people. They are human beings who now actually have a real acute problem. Right. Empathy, understanding, making it easy for them to understand. George, everything you said there, simplify the complex. Like, it is baffling to me that once we have customers sign on the dotted line and however, the way they do it, like, best of luck femme for yourselves. We hope you like this Wikipedia that hasn't been updated in 17 years. Right? Like it's God anyway.

Yeah. So, well, one thing that I want to at least dovetail into the writing or creation of these articles and then we can go because you're passing off to Max. Max alluded earlier, the knowledge base agent and I just want to like dip my toe in the water here and. And literally I'm gonna just. If you're listening this and you don't know what it is, the Breeze knowledge base agent leverages the customer agent that we again quickly alluded to at the beginning of this to find knowledge gaps and support tickets to create article drafts. It will create article drafts. Now do you need to go and check those? Do you need to think about the things that Liz said? Do you need to like, you know, simplify the complex and empathy and all that? But the Breeze knowledge base agent leverages customer agent, knowledge gaps and support tickets to create article drafts for your knowledge base automatically. You can simply review the article content, make and hit automatically automagically. I should have said thank you. You're welcome. Sorry.

Also, can we get a good human?

It's so so for your humans, your customers, if you will. So again, you can simply review the article, the content, make edits, and then hit publish. So in a world where we're saying a lot has changed, like this is one of the major things that have changed because there's automatically some new content that you didn't know that you needed, that could be a knowledge article that you can then make. Amazing. All right, I'll shut up. Max or Liz or whoever.

I've lost track of the question.

It's okay. So it's what are the biggest mistakes companies make when they're building up their knowledge base?

Didn't he go first?

I feel like I did, yeah.

It was Max, then Chad, then me.

I just don't want this to end, guys. Yeah, I think Timer wants to. I have Hub Heroes anxious attachment style. That's clearly the issue here. But you know what else is the issue here, guys? We now find ourselves in a cute little scenario in which there will be a part two to this conversation. Now, I am going to tease something out for our audience though. The part two isn't going to be coming next week, but next week is when I want you guys to do one of my favorite georgisms, which is to grab a snack and a backpack and probably a pen and paper because we're going to be all over the HubSpot map next week. So I am very excited about that episode. I'm not going to tell you guys what it is these gentlemen know. We all know. We're all preparing. But George, help us close out part one of this knowledge based conversation. What's the one thing you want people to walk away with? Or 14 things depending on how you're feeling this week?

No.

One thing. Put yourself. Put yourself in your customer's shoes. Figure out what they need to know most to get the best out of whatever it is you're providing and then use the HubSpot tools to create the dopest knowledge article. Customer agent, knowledge agent, ticket pipeline, help desk service, Hub related process that you might already be paying for just because you got a discount and put it into place. Okay, Hub Heroes, we've reached the end of another episode. Will Lord Lack continue to loom over the community or will we be able to defeat him in the next episode of the Hub Heroes podcast? Make sure you tune in and find out in the next episode. Make sure you head over to thehubheroes.com to get the latest episodes and become part of the of the League of Heroes. FYI, if you're part of the League of Heroes, you'll get the show notes right in your inbox and they come with some hidden power up potential as well. Make sure you share this podcast with a friend, leave a review if you like what you're listening to, and use the hashtag hubberospodcast on any of the socials and let us know what strategy conversation you'd like to listen into next. Until next time. Next time when we meet and combine our forces, remember to be a happy, helpful, humble human. And of course, always be looking for a way to be someone's hero.