01. Schedule the First Session
Introducing a new solution to your school is always going to be a time investment. However, Amarillo College liked the fact that the Gecko implementation could align with their schedule. They blocked out time in their diary for it, but they also took breaks during busy periods so that their team didn’t feel under too much pressure. Maria explains…
“Gecko’s Head of Implementation, Jonny Richardson, told us from the start that it could take as little or as much time as we needed, it was just about scheduling the time. It took about 18 hours in terms of the total meeting time. That covered everything, from learning how to build the questions and answers to managing and training the bot.”
02. Get the Right People in the Room
When it comes to introducing any new technology solution at an institution, it’s important to get the right mix of stakeholders in the room. For Amarillo College, that meant making sure they included people from all levels of the admissions department in the process.
“We had myself, office managers, trainers and end-users in the room. We had a team of about six people involved in the build because you get different questions at all levels. We want to definitely be aware of the escalations, but the end-users helped us recognize the most common, regular questions that they are asked in the office every day.”
03. Build Skills Trees
One of the biggest parts of building a successful chatbot is building a skills tree. A skills tree is a list of pre-defined options that students can choose between in the chat conversation – core topics like undergraduate admissions, order a prospectus, book a campus tour, and financial aid. They enable chatbots to direct students to the information they’re looking for quickly and easily.
“We had to decide what information we wanted to make immediately available to students, and what questions we wanted to build to point students to from those skills trees.”
04. Find the Common Questions
This is where you have to think of all the frequently asked questions. In the beginning, Maria said that her team were instinctively more focused on the questions that could lead to escalations. As customer service agents, their mind is trained to worry about the what-ifs. But this process is really about finding the common, easy-to-answer questions.
“While we may tend to focus more on the specialized questions, our students often just want to know the simple stuff like, where’s the library? What’s your phone number? What are your office hours? And so it wasn’t until after we’d finished with that exercise and our staff went in there and triggered a lot of questions, that the common questions started to float to the top really quickly. It’s the stuff they’re hearing on the phone all day, every day.”
“One of the great things Gecko’s Head of Implementation, Jonny Richardson, did was tell us to build our questions and then let several people just loose in there to bombard the chatbot with questions.”