This is part 2 of an ongoing series. Find part 1 here.

Evaluating what support questions can be automated with a chatbot starts you off on the right foot to developing a minimum viable product (MVP). Clearly defining ROI, which channels to implement, and use cases puts developers and product managers in the right frame of mind to create a project that customers will use and benefit from. As a continuation of the go-to-market strategy, it’s important to identify the best tools to build your customer service chatbot.

![in-house or agency for customer service chatbot mvp](
### **In-house or agency?**

Now that it’s actually time to start building the customer service chatbot MVP, there are two main options to consider: in-house or agency. Some are going to want a larger role in the way the chatbot is built, and it’s worth mentioning that it’s easier to keep a close eye on the chatbot being built in-house. If there’s a very specific vision of the project, having the team close and accessible provides more control of the development. Instead of sending emails to an outside vendor and waiting for the routine scheduled meeting for an update, the in-house team can be easily reached by walking across the office. Less back-and-forth to communicate an idea means there’s a lower chance of wires getting crossed. In addition, all the insights gained from this chatbot project can be shared throughout the company and applied to future projects as well.

If speed is a main objective for the project, hiring an agency to build the chatbot would ensure that development happens in a timely manner. Assembling a team and figuring out a workflow requires time, which might bottleneck the project before it even got started. Agencies are already staffed with experienced developers and designers, allowing you to bypass the process of finding each new hire. It’s also worth mentioning that agencies are typically the more cost-effective option for smaller companies that lack development teams.

page image ### Choose an NLP engine

Building a chatbot– big or small– that understands human language instead of relying on conversation trees requires a Natural Language Processing (NLP) engine. The NLP engine will create a model tailored to your purpose, so the chatbot will be able to understand phrasing or vernacular that’s specific to your industry. Without it, a chatbot would be unable to extract the relevant information and ascertain meaning from an Utterance.

NLP engines are abundant, so it won’t be hard to find one that will best fit each use case. If building for a Facebook Messenger bot, Facebook’s own is actively being developed and already part of the infrastructure. Dialogflow, another widely-used option, is Google’s solution to natural language understanding. It has 35 domains of knowledge available and supports voice interfaces as well. If you’re looking to build something within the Amazon platform, Amazon Lex can create a chatbot in minutes with just a few phrases and has pre-built integrations with many services on the AWS platform. These options are free, so they’re good choices for MVP projects.

In 2016, Microsoft introduced Language Understanding Intelligent Service, or LUIS. Some might want to integrate their customer service chatbot with an enterprise software, and LUIS is well-suited for that. IBM Watson, another enterprise solution, has a wide range of pre-built customer care and other common Intents. If your company is already using the Microsoft or IBM suite of products, these options would be an easy addition to begin chatbot development.

Projects that benefit from a high level of customization would see a lot of value from using something like RASA, an open source machine learning tool. Since it’s not an out-of-the-box tool, there are a lot of opportunities to customize and fully integrate RASA into existing systems.

Designing your conversations

After deciding on an agency (or not) and an NLP engine, it’s time to start building content. This is an especially important step for customer service chatbots, since users will reach out for support on this platform. In order to lower escalation rates and ensure most users get the answers they’re looking for, build content around topics that customers are asking about on current channels.

Determining what customers are asking will point the conversation designers in the right direction. In part 1, we discussed examining historical live agent logs to determine what support questions could be automated. That same data is also viable to inform design, providing insight to where customers need the most support. If there’s a high volume of logs, consider using a tool like Phrase Clusters. Phrase Clusters will group common messages together based on semantic meaning so designers will know which Intents users will trigger most often.

It goes without saying that not every single Intent can be predicted before launch. No matter how much preparation goes into the chatbot, there are going to be some surprises once users start interacting with it. Optimizing the content to meet user expectations will be key to ensuring high customer satisfaction along with longevity of the project. In order to do that, examine user conversations using a conversational analytics tool to identify common unexpected Intents among transcripts.

Launch is day one

Keeping customers in mind at every step of the way will embed value in every aspect of the customer service chatbot. A thoughtfully made, tailored MVP designed specifically for your users will perform better than one developed impatiently. Picking the right NLP engine and Intents to create content for is a step in the right direction, but the work is far from over.

The more a user interacts with a chatbot, the more expectations they’ll have. Constant optimization is key to maintaining or even increasing customer satisfaction. This requires a powerful analytics tool like Dashbot that provides a granular look into each conversation. There’s a very high chance of customers running into obstacles right after launch, and it’s helpful to have visibility into each conversation as to catch these pain points early on. Having the ability to track KPI’s such as escalation and user satisfaction from the start will go a long way toward taking a chatbot beyond just a MVP.

This is part 2 of Dashbot’s series on chatbot development. Stay tuned for part 3 and catch up on part 1 here.

About Dashbot

Dashbot is an analytics platform for conversational interfaces that enables enterprises to increase satisfaction, engagement, and conversions through actionable insights and tools.

In addition to traditional analytics like engagement and retention, we provide chatbot specific metrics including NLP response effectiveness, sentiment analysis, conversational analytics, and the full chat session transcripts.

We also have tools to take action on the data, like our live person take over of chat sessions and push notifications for re-engagement.

We support DialogFlow, Alexa, Google Assistant, Facebook Messenger, Slack, Twitter, Kik, SMS, web chat, and any other conversational interface.

Contact us for a demo