We Turned Our SOPs Into a Chatbot

Last week my team took 30 of our internal procedures and rewrote every one of them for a client-facing knowledge base. 

Adding a vehicle. Removing a driver. Filing a claim. Billing questions. Thirty of the most common things people contact us about, written in plain language, fed into our HelpScout AI chatbot so clients can get an answer without waiting on a human. 

The part that surprised me was how fast it came together. Because we had already documented our internal SOPs, we didn't have to start from scratch. The foundation was already built. What took the most time was the review pass, reading through each article, tweaking the language for a client audience, making sure nothing assumed knowledge the client wouldn't have. That part took real attention. But we weren't staring at a blank page, and that made all the difference. 

Here's why we did it. My team spends a meaningful part of everyday answering questions that have the same answer every single time. How do I add a car? Can you send me proof of insurance? What do I do if I get a letter from the MVA/DMV? These aren't bad questions. They're just questions that don't need a licensed agent to answer them. 

When a licensed agent is explaining how to return license plates to the MVA or DMV, that's a conversation that shouldn't be happening. Not because the client doesn't matter, but because that agent could be doing an account review, walking someone through a claim, or having a real coverage conversation with someone who hasn't thought about umbrella or life insurance yet. 

That's the trade-off we're trying to make. Free the humans for the conversations that actually require a human. 

We're early. We don't have results yet. The chatbot is live, and we're watching to see whether people actually use it or just pick up the phone anyway. Next up is feeding this into our AI receptionist, and we'll keep you posted on what actually works. 

There's a lot of noise out there right now around AI and tools. That's not going away. But I don't think the answer is to chase every shiny thing or ignore all of it. The answer is to stay experimental, be honest about what's working and what isn't, and keep asking the same question: is this making things better for our clients and our team? If yes, keep going. If not, move on. 

If you've been putting off documenting your SOPs because it feels like too much work, this is the reason to start. You don't build it for the chatbot. You build it, so your team isn't the only place that knowledge lives.