<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Casey Phillips on Medium]]></title>
        <description><![CDATA[Stories by Casey Phillips on Medium]]></description>
        <link>https://medium.com/@casphill?source=rss-e3f0721527ec------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*NnUx-lRaQ6wc3f-bBGop8w.jpeg</url>
            <title>Stories by Casey Phillips on Medium</title>
            <link>https://medium.com/@casphill?source=rss-e3f0721527ec------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 10 Nov 2026 19:43:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@casphill/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[Making the Leap from Chatbot to Conversational AI]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/swlh/making-the-leap-from-chatbot-to-conversational-ai-79b12182008b?source=rss-e3f0721527ec------2"><img src="https://cdn-images-1.medium.com/max/2600/1*dsCLua-wdb1qDvvAfz8MmA.jpeg" width="5472"></a></p><p class="medium-feed-snippet">How to grow your chatbot into a full-blown conversational AI machine</p><p class="medium-feed-link"><a href="https://medium.com/swlh/making-the-leap-from-chatbot-to-conversational-ai-79b12182008b?source=rss-e3f0721527ec------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/making-the-leap-from-chatbot-to-conversational-ai-79b12182008b?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/79b12182008b</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Tue, 08 Dec 2020 18:03:25 GMT</pubDate>
            <atom:updated>2020-12-08T18:03:25.598Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The #1 Reason Most Chatbot NLU Models Fail]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/chat-bots/the-1-reason-most-chatbot-nlu-models-fail-2cb8f2d87a4?source=rss-e3f0721527ec------2"><img src="https://cdn-images-1.medium.com/max/670/0*3slAJv_BmuoFenQD.jpg" width="670"></a></p><p class="medium-feed-snippet">Making the case for domain-specific NLU models</p><p class="medium-feed-link"><a href="https://medium.com/chat-bots/the-1-reason-most-chatbot-nlu-models-fail-2cb8f2d87a4?source=rss-e3f0721527ec------2">Continue reading on Chatbots Magazine »</a></p></div>]]></description>
            <link>https://medium.com/chat-bots/the-1-reason-most-chatbot-nlu-models-fail-2cb8f2d87a4?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/2cb8f2d87a4</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Tue, 11 Jun 2019 20:10:21 GMT</pubDate>
            <atom:updated>2019-06-11T20:10:21.033Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Disambiguation is a Chatbot’s Most Powerful Weapon]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.chatbotslife.com/why-disambiguation-is-a-chatbots-most-powerful-weapon-7723ef471a36?source=rss-e3f0721527ec------2"><img src="https://cdn-images-1.medium.com/max/600/1*voN6G46vzB6KcBSxrtr3cg.jpeg" width="600"></a></p><p class="medium-feed-snippet">Arm your chatbot with conversation flows that actually get users to the answers they need</p><p class="medium-feed-link"><a href="https://blog.chatbotslife.com/why-disambiguation-is-a-chatbots-most-powerful-weapon-7723ef471a36?source=rss-e3f0721527ec------2">Continue reading on Chatbots Life »</a></p></div>]]></description>
            <link>https://blog.chatbotslife.com/why-disambiguation-is-a-chatbots-most-powerful-weapon-7723ef471a36?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/7723ef471a36</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Tue, 09 Apr 2019 13:05:59 GMT</pubDate>
            <atom:updated>2019-04-09T13:05:59.740Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Perfecting the Chatbot Fallback Experience]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://uxplanet.org/perfecting-the-chatbot-fallback-experience-f76d119c45d4?source=rss-e3f0721527ec------2"><img src="https://cdn-images-1.medium.com/max/775/0*TwqG-NxBIt-DNGB2.jpeg" width="775"></a></p><p class="medium-feed-snippet">Nailing the most important chatbot flow you&#x2019;ll ever create</p><p class="medium-feed-link"><a href="https://uxplanet.org/perfecting-the-chatbot-fallback-experience-f76d119c45d4?source=rss-e3f0721527ec------2">Continue reading on UX Planet »</a></p></div>]]></description>
            <link>https://uxplanet.org/perfecting-the-chatbot-fallback-experience-f76d119c45d4?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/f76d119c45d4</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Wed, 03 Apr 2019 17:46:58 GMT</pubDate>
            <atom:updated>2019-04-03T17:46:58.750Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[3 Steps to Grow Chatbot User Engagement w/ Personalization]]></title>
            <link>https://uxplanet.org/3-steps-to-grow-chatbot-user-engagement-w-personalization-7d29e70c87ee?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d29e70c87ee</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Fri, 01 Mar 2019 17:41:16 GMT</pubDate>
            <atom:updated>2019-03-01T17:41:16.411Z</atom:updated>
            <content:encoded><![CDATA[<h4>The days of a one-size-fits-all approach to chatbot design are over</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*9lyoHtJ-df8KQgj08iNksA.png" /><figcaption>Create a personalized user experience that takes your chatbot user engagement metrics to new heights</figcaption></figure><h4>Let’s be real; no one wants to talk to a one-size-fits-all chatbot 😒</h4><p>In the early days of the chatbot, we were all treated to the concept of a generic one-size-fits-all chatbot, and oh what a treat that was. It was a pleasant surprise if the chatbot could even refer to the user by their name let alone leverage any meaningful data on the user.</p><p>In the end, we all became frustrated by drawn-out chatbot conversations that ultimately provided little value, and thus our pessimism towards the chatbot industry grew. As a result, today’s chatbots need to prove to users that they’re more than their embarrassing predecessors to garner worthwhile chatbot user engagement numbers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/377/1*VUGNaST-WZCrge9rrMm_Wg.png" /><figcaption>Don’t expect any sort of chatbot user engagement success from a chatbot greeting like this.</figcaption></figure><h4>Step 1: ‘Wow’ users by knowing the meaningless details 😲</h4><p>This is definitely the low hanging fruit in this formula and something everyone should leverage to help with chatbot user engagement. Many users will approach a new chatbot conversation with a heavy dose of trepidation and pessimism; therefore the chatbot’s welcome message is the perfect opportunity to show that your chatbot has some intelligence.</p><p>Greeting the user by their name, mentioning the weather where they live, changing the salutation based on the time of day (good morning, good afternoon, good evening), and displaying multiple variations of the chatbot’s welcome message to help shake things up for repeat users are a great start to improving chatbot user engagement with personalization.</p><p>The key here is to show users that they’re not interacting with one of those pesky one-size-fits-all chatbots without having to do too much heavy lifting in regards to what’s under the chatbot’s hood. You need to get the user to overcome any negative connations they have about chatbots and commit to giving your chatbot a shot by responding and engaging it in a conversation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/1*0mTgleDuMsKHRmrTpMLZ3g.png" /><figcaption>Welcome messages like this help boost chatbot user engagement by showing the user that your chatbot has some intelligence to it</figcaption></figure><h4>Step 2: Leverage historical user data to cut out the unnecessary chit-chat ✂️</h4><p>Any data you have regarding users’ past interactions with your chatbot or the product it supports are perfect fodder for creating a personalized user experience that moves the needle when it comes to chatbot user engagement. This can be as simple as a chatbot that helps users order pizza remembering a user’s last order and their delivery address.</p><p>You’ll often hear people say that past behavior is the best predictor of future behavior and that concept resonates when it comes to chatbot conversations. For example, in the case of the pizza-ordering chatbot, if a user has placed the same order three out of the last four times then the chatbot can save the user a lot of time and typing by asking if they’d like to place that order again upfront. This provides value to the user and will help improve chatbot user engagement.</p><p>The main takeaway here is that a chatbot should not treat repeat users the same as a first-time user. Would you want your fifth conversation with a new acquaintance to feel exactly the same as the initial one? We experience the benefits of conversational context in our everyday conversations with other humans. It’s time for chatbots to get on the same level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*oqY5cJnX5nxqijdDsGKL7g.jpeg" /><figcaption>A great example of how powerful historical user data can be when effectively leveraged in a chatbot conversation.</figcaption></figure><h4>Step 3: Use ‘live’ user activity to provide the ultimate chatbot personalization experience 😍</h4><p>This is by far the most powerful form of chatbot personalization covered in this article and a ‘must’ when it comes to chatbot user engagement for any chatbots tailored for sales or support. The premise is that the chatbot conversation is customized based on how the user is engaging with the chatbot or the product it supports in real-time.</p><p>For example, a chatbot that knows where a particular user is in the product it supports could ask the user if they’re encountering the issue most commonly associated with that specific part of the product. Another great example is a sales-focused chatbot that provides product recommendations based on what the user is shopping for in their current session. If I’m shopping for shoes, the chatbot better not provide me with product recommendations for hats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*aE7FiUvhfE4B_q5F5rdKSw.png" /><figcaption>Now that’s a chatbot greeting primed to boost chatbot user engagement!</figcaption></figure><p>While reaching this state of chatbot personalization is no easy undertaking, the positive impact it can have on chatbot user engagement cannot be overstated. Real-time personalization like this provides tremendous value that will help impress the most demanding users and keep them coming back for more.</p><p>So what are you waiting for? Amaze your chatbot’s users by making them feel as though the conversation is personalized to them, and watch your chatbot user engagement metrics soar as a result.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fupscri.be%2Fb3e808%3Fas_embed%3Dtrue&amp;dntp=1&amp;display_name=Upscribe&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fupscri.be%2Fb3e808%2F&amp;image=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttp%2Fapi.screenshotlayer.com%2Fapi%2Fcapture%3Faccess_key%3Dfe59908dad3baab69ffab249a2224b03%26viewport%3D1024x612%26width%3D1000%26url%3Dhttps%253A%252F%252Fupscri.be%252Fb3e808%253Fscreenshot&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href">https://medium.com/media/96d08ab34921bdd17986cb5c0396842f/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d29e70c87ee" width="1" height="1" alt=""><hr><p><a href="https://uxplanet.org/3-steps-to-grow-chatbot-user-engagement-w-personalization-7d29e70c87ee">3 Steps to Grow Chatbot User Engagement w/ Personalization</a> was originally published in <a href="https://uxplanet.org">UX Planet</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Ultimate Chatbot UX Design Strategy for 2019]]></title>
            <link>https://medium.com/chat-bots/the-ultimate-chatbot-ux-design-strategy-for-2019-b77b85e36f5a?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/b77b85e36f5a</guid>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Sat, 19 Jan 2019 21:24:54 GMT</pubDate>
            <atom:updated>2019-01-19T21:24:54.642Z</atom:updated>
            <content:encoded><![CDATA[<h4>What a chatbot needs to be successful in 2019</h4><figure><img alt="Image result for chatbot" src="https://cdn-images-1.medium.com/proxy/0*oz2e-hQtsHOWzoB4." /><figcaption>The Ultimate Chatbot UX Design Strategy for 2019</figcaption></figure><h4>Disclaimer: This strategy isn’t for the faint of heart… 😲</h4><p>If you’re looking for basic beginner-level chatbot UX design strategies, then I recommend you check out <a href="https://chatbotsmagazine.com/6-must-haves-for-chatbot-ux-design-cc2a21b944e">this article</a> I wrote in 2018 on the ‘6 Chatbot UX Design ‘Must-haves’ for 2018.’ This piece you’re reading is an expansion on the chatbot UX design principles I covered last year and is for those looking to get their feet wet in advanced chatbot UX design concepts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*kSn8yYekxq1rhyyj.jpg" /><figcaption>*Insert obligatory ‘scared cat meme’ here*</figcaption></figure><h4>In 2019 it’s all about the chatbot personalization ✏️</h4><p>Have you ever encountered a chatbot without personalization in the wild? If you have, I’m sure you’ll agree with me when I say that it’s truly a brutal user experience. It feels like a visual cloud-based presentation of those phone IVR queues that we’ve all grown to despise.</p><p>Chatbots without conversational personalization put users through a one-size-fits-all conversation path that generally requires users to select preset response options (usually via buttons) over and over again until they maybe… just maybe… find what they’re looking for.</p><p>It sounds frightening from a user perspective, doesn’t it? Well, it is. Trust me…</p><p>If you want a successful chatbot UX design strategy that promotes user engagement and provides value to the chatbot’s users then you need to make each individual user feel as though the conversation is tailored to their needs and situation. Addressing the user by their name and customizing the salutation based on the time of day (good morning, good afternoon, good evening, etc.) is not going to cut it 2019.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/379/1*nrsWlGt7lPYJz3FRJWF9Cg.png" /><figcaption>This a nice start towards personalized conversations, but users will expect more in 2019</figcaption></figure><p>While the aforementioned personalization examples should still be included in your chatbot UX design strategy for 2019, there are more advanced levels of personalization that will contribute much more to a chatbot’s success.</p><h4>Leverage users’ conversation history to cut the unnecessary chit-chat ✂️</h4><p>This idea is vital to the chatbot UX design strategy of chatbots in the service sector. The concept is simple. Use what you already know about the user from their previous interactions with the chatbot or the product it supports, to create an optimized conversation flow that minimizes the user’s path to their desired solution.</p><p>For example, if your chatbot allows users to order pizza then start off by authenticating the identity of the user, figure out whether they’re an existing customer, and if they’re a repeat customer then take advantage of what you already know. This can involve tailoring order recommendations based on past order history, remembering users’ delivery addresses and payment methods, and much more.</p><p>Not only will this chatbot UX design strategy help more users reach their desired state, which in this case is a hot pizza at their doorsteps ASAP, but it will provide a smoother, more intuitive conversation path that cuts down on the annoyingly unnecessary chit-chat such as asking the user for their delivery address. If this is my fifth time ordering pizza with this chatbot then it better remember my address and at the most just ask me to confirm it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/427/1*v2mUSPLZQCz7ZnJ3rhi9eA.png" /><figcaption>Don’t overlook the power of this chatbot UX design concept</figcaption></figure><p>The applications for this particular chatbot UX design strategy are endless, however, it can sometimes be easier said than done to actually deliver on it. None the less, big results require a big effort. You’ve got this!</p><h4>For truly mind-blowing results, personalize the conversation based on real-time user activity 🥇</h4><p>If you really want to create a chatbot that impresses users then add this nugget to your chatbot UX design strategy for 2019. This is about as good as it gets when it comes to making users feel as though the conversation is tailored to them.</p><p>This chatbot UX design concept is particularly powerful for chatbots aimed at providing sales or customer support. The idea is simple in theory. Customize the conversation design based on the real-time activity of that user with the chatbot and the website or product it supports. Unfortunately, the implementation is likely not going to be simple…</p><p>A great example of this particular chatbot UX design strategy in practice is a support-based chatbot that is able to tailor its conversation based on the current activity of that user in the product it supports. If you know what section of the product the user is in and have data that indicates a high probability of them having a particular issue, then ask that user if that is in fact the problem they’re experiencing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/1*aE7FiUvhfE4B_q5F5rdKSw.png" /><figcaption>Now that’s an impressive chatbot welcome message! This chatbot UX design strategy can be a ‘game-changer’</figcaption></figure><p>Another prime use case for this chatbot UX design strategy involves a sales-based chatbot that provides customized product recommendations in the conversation based on what the user is currently shopping for. If I’m shopping for hats and I start a conversation with this chatbot, it better not start off by recommending pairs of jeans.</p><p>While this chatbot UX design concept is a difficult one to implement, the fruits of your efforts will be well worth it. Not only does this score exceptionally high on the ‘wow-factor’ scale, but it provides genuine value to users that they likely won’t get through alternative means. That’s how you design a winning chatbot.</p><h4>Keep calm and chatbot on… 🤖</h4><p>If your chatbot isn’t at this level yet don’t fret. As I already mentioned, this chatbot UX design strategy is definitely on the more advanced end of the spectrum.</p><p>Do the best you can at present, but keep in mind that the chatbot space is moving in this direction and you’ll need to get here at some point. If you don’t, it shouldn’t be much of a shock when your once-promising chatbot becomes as extinct as the dinosaurs.</p><p>Cheers to a successful 2019!</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*YfEE32OOt5KymoLv.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fupscri.be%2F58521e%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fupscri.be%2F58521e%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/c90883b0516ddbe5c59960c12a04bc64/href">https://medium.com/media/c90883b0516ddbe5c59960c12a04bc64/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b77b85e36f5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chat-bots/the-ultimate-chatbot-ux-design-strategy-for-2019-b77b85e36f5a">The Ultimate Chatbot UX Design Strategy for 2019</a> was originally published in <a href="https://medium.com/chat-bots">Chatbots Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why You Should NEVER Use ‘Yes’ or ‘No’ Chatbot Buttons]]></title>
            <link>https://medium.com/swlh/why-you-should-never-use-yes-or-no-chatbot-buttons-d1be443372be?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/d1be443372be</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Wed, 14 Nov 2018 07:23:53 GMT</pubDate>
            <atom:updated>2018-11-14T07:23:53.500Z</atom:updated>
            <content:encoded><![CDATA[<h4>Safeguard your chatbot from one of the most prominent user errors</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/735/0*6ABXXRnOPelAXdFs.jpg" /><figcaption>Thinking about using ‘Yes’ or ‘No’ chatbot buttons? Please STOP and read this article first…</figcaption></figure><h4>Users will misuse your chatbot far more often than you expect 🤖</h4><p>If you think most users will use your chatbot as expected this is clearly your first rodeo. Not only will user conversations surprise you but you will likely find yourself dumbfounded by many of them.</p><p>To expect a chatbot conversation to go as planned is the literal equivalent to meeting a stranger and expecting to know exactly how that conversation will unfold ahead of time. Plain and simple, it’s nearly impossible to predict chatbot user behavior.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/460/0*sdCJh7exQ9XeBB6w.jpg" /><figcaption>If your chatbot has made you feel this way, don’t worry. You’re not alone…</figcaption></figure><p>Moral of the story here is to expect the unexpected and take whatever measures you can to safeguard your precious chatbot from user error as best as you can. Otherwise, don’t be surprised when your chatbot fails miserably.</p><h4>If you think users read everything your chatbot says, you’re wrong 🤦</h4><p>This one of the first and harshest lessons I learned after building my first chatbot. Unless your chatbot is designed purely for entertainment purposes — in which case this may still happen — expect users to frequently skim through your chatbot’s responses instead of reading them verbatim.</p><p>Users are ultimately looking to get some sort of value from your chatbot, and if that value isn’t pure entertainment, then they will try to get through the chatbot conversation as quickly as possible to reach the prize aka that value they’re seeking. This cruel reality only increases the likelihood that users will make mistakes when navigating through your chatbot’s conversation flow.</p><p>The key takeaway here is that you need to keep your chatbot responses brief and straight to the point wherever possible. Any unnecessary dialogue that doesn’t help the user navigate to what they’re looking for is just adding to the probability of user error and misuse.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/495/1*wqIkx0-pCEkzM7Pgko0Vcw.png" /><figcaption>A perfect example of a long chatbot response that is at risk of getting skimmed over</figcaption></figure><h4>Using Single-word chatbot buttons such as ‘Yes’ or ‘No’ is like begging for user error 🙏</h4><p>Now that we’ve established the likelihood that users will skim through and misread your chatbot content, let’s couple that with the use of vague, single-word chatbot buttons such as ‘Yes’ or ‘No’. I’m going to provide a simple real-world example that actually occurred in a chatbot that I previously built to prove why these minuscule chatbot buttons are so dangerous.</p><p>In this example, we have a support-based chatbot whose initial message to the user asks them to confirm whether or not they’re an existing customer. This is a critical inquiry as existing customers should continue through the chatbot conversation and hopefully get the support they need from the chatbot. Users that are new customers need to get routed to a contact center queue where a sales rep will reach out to them.</p><p>Users that are not paying attention to the content in this initial message may click the ‘Yes’ chatbot button indicating that they’re an existing customer where in fact they may have just made a mistake. Now, this user is getting free support instead of a callback from a sales rep. This is a simple example, but you can see just how costly user mistakes like this can be to your chatbot’s success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/378/1*AvESxTY9jvixKjRNiIJtJQ.png" /><figcaption>You’d be shocked at how many users will incorrectly respond to these ‘Yes’ and ‘No’ chatbot buttons</figcaption></figure><h4>Opt for brevity except when labeling your chatbot buttons ✏️</h4><p>In that example, the ‘Yes’ and ‘No’ chatbot buttons should’ve been labeled ‘Yes, I’m an existing customer’ and ‘No, I’m new’ to help prevent user error. While users will often skim through a chatbot response, they’re generally far more likely to pay attention to the label of a chatbot button since they have to focus on the chatbot button while engaging in the act of clicking on it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/375/1*E3NZGAJLVRnx1iXnQxmEtg.png" /><figcaption>Chatbot buttons with descriptive labels such as these help to prevent user error</figcaption></figure><p>So, when building your next chatbot opt for brevity in your chatbot messages to minimize the likelihood of users skimming, but make sure to label chatbot buttons in a manner that makes it clear what action the user will be taking by clicking on it even if they didn’t read a word of the associated chatbot message.</p><p>As always, remember to ‘Keep calm and chatbot on’…</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*YfEE32OOt5KymoLv.png" /></figure><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YqDjlKFwScoQYQ62DWEdig.png" /></a></figure><h4>This story is published in <a href="https://medium.com/swlh">The Startup</a>, Medium’s largest entrepreneurship publication followed by +388,456 people.</h4><h4>Subscribe to receive <a href="http://growthsupply.com/the-startup-newsletter/">our top stories here</a>.</h4><figure><a href="https://medium.com/swlh"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ouK9XR4xuNWtCes-TIUNAw.png" /></a></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d1be443372be" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/why-you-should-never-use-yes-or-no-chatbot-buttons-d1be443372be">Why You Should NEVER Use ‘Yes’ or ‘No’ Chatbot Buttons</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Obstacles to Chatbot User Adoption & How to Overcome Them]]></title>
            <link>https://medium.com/chat-bots/5-obstacles-to-chatbot-user-adoption-how-to-overcome-them-78652a613b69?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/78652a613b69</guid>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Mon, 22 Oct 2018 20:03:06 GMT</pubDate>
            <atom:updated>2018-10-22T20:03:06.847Z</atom:updated>
            <content:encoded><![CDATA[<h4>Winning over potential chatbot users is no easy task, but it can be done with the right mindset and approach</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*UM8sBsc1knJ1lIjUdUCFxQ.png" /></figure><h4>You expected chatbot user adoption to be easy, didn’t you? 😂</h4><p>Let’s be honest. When building your chatbot, you were so thrilled with the user experience that you expected users to flock to it in droves once it went live. Now you’re three months in post-live and practically banging your head against the wall when analyzing the user data.</p><p>Not only are users not lining up to use your chatbot as you’d hoped, but the numbers are well below the benchmarks you’ve set. Don’t worry; you’re not alone. Several inherent obstacles are a hindrance to virtually all chatbot user adoption, but they can be overcome. Obligatory disclaimer: it won’t be easy though…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*NP16aA_ISWA5Pd0V.jpg" /><figcaption>Does this remind you of your chatbot user adoption struggle?</figcaption></figure><h4>1. Chatbots are unproven versus the status quo 🤔</h4><p>Remember the struggle mobile apps had converting web browser users several years ago? That same struggle seems pretty non-existent today, doesn’t it?</p><p>Chatbots are currently in the same situation that mobile apps were in several years ago. Users are often creatures of habit and will get comfortable with the workflows and technologies that they use on a day-to-day basis. Getting users to cross the line and adopt something new is no easy feat, and the same applies to chatbot user adoption.</p><p><strong>So what can you do to overcome this?</strong></p><p>First off, be patient and persistent with a focus on the long term. If you analyze your chatbot’s user adoption in the short term, you will find yourself overreacting and making impulse decisions that don’t fit with your best long-term interests.</p><p>In addition to being patient, you need to make sure your chatbot leaves an excellent initial impression and showcases some form of value to the user that the status quo isn’t providing. If users don’t see this value almost immediately or see a product riddled with bugs and shortcomings, you can bet that they will immediately crawl back to whatever product or tool they were using before they gave your chatbot a shot.</p><h4>2. User expectations often far exceed reality 🤖</h4><p>This struggle is all too real in the chatbot space right now. So many users expect chatbots and the AI that powers them to be something out of a Sci-Fi movie. Unfortunately, that’s just not the reality in today’s chatbot landscape.</p><p>While chatbots can do a lot of great things and provide excellent opportunities for automation, they are still not smarter than humans. The chatbot user adoption struggle is real folks…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/0*r2Rhv1FtgAIN_TOv.jpg" /><figcaption>Don’t be surprised if users expect your chatbot to be on this level…</figcaption></figure><p><strong>So what can you do to overcome this?</strong></p><p>Don’t oversell your chatbot as something it isn’t. If your chatbot can only answer basic questions about the weather, that’s fine, but don’t sell users on it being their a personal meteorologist in their pocket. If you do that, you can expect a lot of first-time users that will never become recurring users.</p><p><a href="https://chatbotsmagazine.com/why-your-chatbots-greeting-is-its-most-important-response-3278898dc7a3">Crafting a sound welcome message for your chatbot</a> can set realistic expectations for users regarding what it can and can not do. While this may be a less sexy way to sell your chatbot, it will improve the overall user experience and lead to more repeat usage.</p><h4>3. Organizational Failure to Properly Integrate Chatbots 🤦</h4><p>This struggle applies to organizations trying to implement chatbots into their existing technology portfolio and everyday workflows. Too often, there is a failure to truly understand the potential impact chatbots will have when thrown into an organization for internal use.</p><p>I get it. Chatbots are sexy and one of the most prominent technological fads at the moment, but that doesn’t mean they’re miracle workers and always the right decision. There are instances where chatbots may not coexist well with the workflows or existing technologies within an organization, and that’s fine. Forcing chatbots into the mix just for the sake of having chatbots, however, is not a good practice.</p><p><strong>So what can you do to overcome this?</strong></p><p>Whether you work for an external agency looking to integrate chatbots within a client organization or a key stakeholder vetting the possibility of incorporating chatbots internally, you need to do your due diligence and have a success plan in place. Key things to consider include:</p><ul><li>Do chatbots create synergy with the rest of the organization’s technologies?</li><li>Will chatbots make a noticeable difference in the productivity and success of the organization, and if so, what metrics and goals can be used to assess their effectiveness?</li><li>Does the organization have a culture that will embrace the use of chatbots?</li><li>What is the potential ROI for the adoption of chatbots and how likely is it that this ROI can be met?</li></ul><p>If any of those questions result in a resounding ‘No,’ then you may want to reconsider the chatbot implementation or at the very least create a plan that helps to flip that resounding ‘No’ into a potential ‘Yes.’</p><h4>4. User activity is completely unpredictable 🙃</h4><p>This struggle is arguably the most frustrating and challenging when it comes to chatbot user adoption yet also the most enjoyable aspect of working on chatbots at times. This struggle of never knowing exactly how users are going to interact with a chatbot is part of the thrill that makes chatbots so fun to build and chatbot user adoption so tricky.</p><p>Let’s face it, you can add beautiful menus of response buttons and as many utterances to those intents as you want, but ultimately users are going to create a conversation that you and your chatbot are entirely unprepared for. It’s inevitable but ultimately part of the fun. Embrace the uncertainty, move quickly, and learn from your mistakes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*bcluc2ALqfh3L0zi.jpg" /><figcaption>Chatbot users will never cease to surprise and amaze with the things they’ll say.</figcaption></figure><p><strong>So what can you do to overcome this?</strong></p><p>Analytics, analytics, and oh yeah, more analytics! Analytics are critical to identifying the biggest pitfalls that are hindering chatbot user adoption. Without analytics, you will find yourself blindly making decisions and overreacting to short-term trends.</p><p>You’re never going to build a chatbot that will appease every user it encounters so you need to leverage analytics to figure out how to design your chatbot in a way that pleases the masses while pissing off the fewest. Oh, and when your chatbot does fail to satisfy what a user wants, <a href="https://chatbotsmagazine.com/what-to-do-when-your-chatbot-is-wrong-extracting-value-from-failure-385d23fed1b1">make sure to have an effective fallback response</a> that at least attempts to get the user back on track in the conversation.</p><h4>5. Public fear and distrust over Chatbots and AI 😨</h4><p>Unfortunately, this obstacle is out of your control for the most part. For many, AI and chatbots represent a brewing evil that is out to take our jobs and eventually take over planet earth. While the rest of us all know that couldn’t be further from the truth, this public perception that has been building over the last few years can negatively impact chatbot user adoption.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*RM2GsqsT0QMKlt3W.jpg" /><figcaption>Sadly, many users have this same fear when it comes to AI and chatbots…</figcaption></figure><p><strong>So what can you do to overcome this?</strong></p><p>As I already mentioned, there is unfortunately only so much you can do to overcome this chatbot user adoption struggle. Branding your chatbot as a tool that provides positive value to humanity is a start and can be further aided by giving your chatbot a friendly avatar and personality.</p><p>Remember that over time this negative connotation will die down as the public sees for themselves that AI and chatbots are not the root of all evil and in reality benefiting humanity.</p><h4>You can do it. No seriously, you really can 💪</h4><p>Be patient, learn from your mistakes, and don’t give up. If you do this you will get over your chatbot user adoption struggles with time. After all, nothing worth accomplishing ever comes easy.</p><p>Keep calm and chatbot on…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*YfEE32OOt5KymoLv.png" /></figure><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fupscri.be%2F58521e%3Fas_embed%3Dtrue&amp;dntp=1&amp;url=https%3A%2F%2Fround-lake.dustinice.workers.dev%3A443%2Fhttps%2Fupscri.be%2F58521e%2F&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=upscri" width="800" height="400" frameborder="0" scrolling="no"><a href="https://medium.com/media/c90883b0516ddbe5c59960c12a04bc64/href">https://medium.com/media/c90883b0516ddbe5c59960c12a04bc64/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78652a613b69" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chat-bots/5-obstacles-to-chatbot-user-adoption-how-to-overcome-them-78652a613b69">5 Obstacles to Chatbot User Adoption &amp; How to Overcome Them</a> was originally published in <a href="https://medium.com/chat-bots">Chatbots Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using the 80/20 Rule to Build Better Chatbots]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/good-audience/using-the-80-20-rule-to-build-better-chatbots-749b7adaf1c2?source=rss-e3f0721527ec------2"><img src="https://cdn-images-1.medium.com/max/600/0*hJ5W4H4MqzLcSkJt" width="600"></a></p><p class="medium-feed-snippet">Creating successful outcomes by automating what matters.</p><p class="medium-feed-link"><a href="https://medium.com/good-audience/using-the-80-20-rule-to-build-better-chatbots-749b7adaf1c2?source=rss-e3f0721527ec------2">Continue reading on Good Audience »</a></p></div>]]></description>
            <link>https://medium.com/good-audience/using-the-80-20-rule-to-build-better-chatbots-749b7adaf1c2?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/749b7adaf1c2</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[chatbots]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Wed, 05 Sep 2018 19:11:17 GMT</pubDate>
            <atom:updated>2018-09-14T12:16:26.308Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Introducing the Relay Knowledge Ecosystem]]></title>
            <link>https://medium.com/support-automation-magazine/introducing-the-relay-knowledge-ecosystem-10939d5fc356?source=rss-e3f0721527ec------2</link>
            <guid isPermaLink="false">https://medium.com/p/10939d5fc356</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[bots]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[customer-service]]></category>
            <dc:creator><![CDATA[Casey Phillips]]></dc:creator>
            <pubDate>Mon, 20 Aug 2018 20:50:29 GMT</pubDate>
            <atom:updated>2018-08-23T22:00:16.280Z</atom:updated>
            <content:encoded><![CDATA[<h4>Knowledge sharing fueled by AI</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/0*I9pe7Hmq7m9O9u2A.jpg" /></figure><p>One of the most significant challenges for those trying to offer service and support is being able to relay the proper internal knowledge to customers who need it promptly. As organizations and their product and service offerings grow, the amount of support-related information continuously expands. As this scope of knowledge and information broadens the gap between a tenured, experienced support agent and a new hire grows tremendously.</p><p>AI-powered automation can help bridge this gap and make all of your organization’s support and service-related knowledge accessible to your customers at the click of a button. We created the Relay Knowledge Ecosystem to provide the knowledge organization and automation needed to take your support or service offering to the next level.</p><h3>What is the Relay Knowledge Ecosystem?</h3><p>The Relay Knowledge Ecosystem brings your organization’s knowledge to your customers through chatbots and knowledge base articles that are fueled by Artificial Intelligence (AI). Getting onboard and using the Relay Knowledge Ecosystem is a breeze too as in many cases we can import your organization’s existing knowledge base (if you have one) and make it immediately accessible via chatbots and a visual search bar embedded on a landing page with customizable branding.</p><p>Don’t worry about building bots. We’ve fully automated that process with the Relay software. Now your organization can merely focus on creating a vast knowledge base while knowing that it will be accessible via chatbots and a search bar presentation similar to the Google experience we all know and love. Talk about killing two birds with one stone…</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zivKZv4fA-LpHSTW.jpg" /></figure><h3>The Relay Knowledge Base &amp; Search Bar. Your organization’s personal Google engine</h3><p>When it comes to searching and accessing internal knowledge, it’s tough to beat the concept of a Google-esque search bar. Unlike a chatbot, a search engine is tailored to display a bevy of relevant search results thus increasing the likelihood that you find exactly what you’re looking for.</p><p>While chatbots are an ideal solution for displaying knowledge to external customers, your organization’s internal employees may prefer to find and access knowledge via a search bar since they will likely have the insight needed to weed through a selection of search results. Your customers probably won’t have that same insight, and therefore a conversational approach via chatbots is more likely to provide success.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/0*Ixy7TCb1kV-G3dq7.jpg" /></figure><h3>Deliver your knowledge to your customers via Chatbots</h3><p>While a traditional search bar approach works great for your internal team, it often requires context and insights for success that your customers don’t have. When delivering your organization’s knowledge to customers, chatbots are the way to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/911/0*1A9ZnYA2CE-59g0Z.jpg" /></figure><p>The Relay platform uses proprietary AI and Machine Learning (ML) powered search algorithms that can deliver the same piece of content to your internal team via the Google-like search bar we just highlighted and/or your external customers via the <a href="https://thinkrelay.com/chatbots/">Relay Bots</a>. Just create your piece of knowledge content once, and decide whether it’s searchable via the search bar, chatbots, or both. With the Relay Knowledge Ecosystems, we’re already making manual chatbot creation a thing of the past.</p><h3>So what’s next?</h3><p>If you aren’t currently using knowledge bases and chatbots towards the goal of being able to provide better service and support, then you’re running the risk of falling well behind the competition. Start doing your research and find out whether or not a chatbot and/or knowledge base aligns with the focus of you or your organization. For tips on determining the best chatbot platform for your needs check out one of our <a href="https://thinkrelay.com/blog/choosing-best-chatbot-platform/">previous posts on the subject</a>.</p><p>We would love to give you a demo to show you just how powerful our <a href="https://thinkrelay.com/chatbots/">native chatbots</a> are when combined with the Relay intelligent support platform. <a href="https://thinkrelay.com/request-demo/">Schedule a demo</a>, and we’ll help you transform your support and service operations and take your organization to new heights.</p><p><em>Originally published at </em><a href="https://thinkrelay.com/blog/introducing-relay-knowledge-ecosystem/"><em>thinkrelay.com</em></a><em> on August 20, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10939d5fc356" width="1" height="1" alt=""><hr><p><a href="https://medium.com/support-automation-magazine/introducing-the-relay-knowledge-ecosystem-10939d5fc356">Introducing the Relay Knowledge Ecosystem</a> was originally published in <a href="https://medium.com/support-automation-magazine">Support Automation Magazine</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>