<?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[Obie.ai - Medium]]></title>
        <description><![CDATA[The fastest way to find knowledge at work. - Medium]]></description>
        <link>https://medium.com/tasytt-inc?source=rss----29d471a161a9---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Obie.ai - Medium</title>
            <link>https://medium.com/tasytt-inc?source=rss----29d471a161a9---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 05:17:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/tasytt-inc" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Why we rebuilt our native knowledge base (yet another silo)]]></title>
            <link>https://medium.com/tasytt-inc/why-we-rebuilt-our-native-knowledge-base-yet-another-silo-dac564876395?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/dac564876395</guid>
            <category><![CDATA[product]]></category>
            <category><![CDATA[slackbot]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[slack-apps]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <dc:creator><![CDATA[Chris Buttenham]]></dc:creator>
            <pubDate>Mon, 21 Oct 2019 21:13:16 GMT</pubDate>
            <atom:updated>2019-10-22T00:45:06.464Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KSuf9mKns0s_jmfEFwsyjA.png" /><figcaption>A glimpse of the new Obie Page editor!</figcaption></figure><p>Our mission at Obie.ai is to make company knowledge universally accessible and more useful. Today, we hope to have taken another step in the direction to realize that mission. For those familiar with our product, you know that our core competency is integrating knowledge that already exists within your organization. In seconds, Obie allows you to <strong>connect one of our 16+ out of the box integrations</strong> like: <a href="https://gsuite.google.com/marketplace/app/obie/428522427191">Google Drive</a>, <a href="https://marketplace.atlassian.com/apps/1215787/obie-search-confluence-from-slack?hosting=cloud&amp;tab=overview">Confluence</a> or <a href="https://www.zendesk.com/guide/">Zendesk Guide</a> into one single source of truth for knowledge. Though, this isn’t where Obie started. For the very first Obie customers, we encouraged the use of our own native format of knowledge: <a href="http://ob.ie/AorEHr">Obie Books</a>. Over the course of Obie’s journey, the Books fell further and further down the line of priority as the feedback from new customers was overwhelmingly focused on search and integrations. With that in mind, it might come as a surprise to some that we have spent the last ~8 months re-designing and re-building Obie Books from the ground up.</p><p>We are and will remain unbiased to the source of knowledge you or your organization want to leverage to author and collaborate with one another. However, perhaps more overwhelming than the feedback we receive regarding search and integrations is that organizations feel stuck with, what they describe as, less than ideal knowledge base tools.</p><p>Finally, we are confident that the new Obie knowledge base can fill that gap (for the organizations that need it). Otherwise, our focus will continue to be enabling better access to knowledge <strong>wherever you choose to author it.</strong></p><h3>Highlights of the new Obie Page editor</h3><ul><li>Up to <strong>10x faster</strong> load times!!!</li><li><strong>Markdown</strong> support</li><li><strong>New image editing</strong> experience</li><li>Add beautiful royalty free images from <a href="https://medium.com/u/2053395ac335">Unsplash</a></li><li>Link external applications with <strong>embeddable iFrames</strong></li><li>Deep linking of Obie Pages &amp; Google Drive documents</li><li>.. and more! Check it out, or <a href="http://obie.ai/">try Obie for free</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*65g3sDG8DSkRz1BUM6yTvw.gif" /><figcaption>Rich snippets for Obie Pages &amp; Google Drive</figcaption></figure><h3>Search at Obie.ai</h3><p>Just in case you’re worried that we’re shifting focus, we decided to put together this roadmap of search iterations and improvements; it’s often difficult to see the incremental work we do on our search technology as the greatest gains come from behind the curtain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nBNCi-S4ge1qqaZ-rfpY0Q.png" /><figcaption>Obie Search Roadmap — Past &amp; Future Improvements</figcaption></figure><h4>But wait, there’s more!</h4><ul><li><strong>Zendesk Guide integration! </strong>Support teams rejoice! You can now connect your existing knowledge base from Zendesk and access it with ease.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*ag0MEDiQ5NYOBvXOMgYIvw.gif" /><figcaption>Obie for Zendesk Guide!</figcaption></figure><ul><li>For <strong>Obie Premium</strong> customers using our <a href="https://medium.com/u/a24c634669f">JIRA Service Desk</a> integration, the <strong>Create Ticket </strong>app action is now available in Slack for easier request creation.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/868/1*rpfGQ-4KrD2iWmZFsOvu0A.gif" /><figcaption>Create a JSD ticket with 2 clicks!</figcaption></figure><ul><li>The Obie slash command <strong>(/obie) is now available in private channels</strong> as well as direct messages. Quite frankly, it should have worked that way from the beginning. We are grateful for the feedback.</li><li>We re-jigged <strong>Obie Suggest</strong> to respect a higher confidence when showing suggested knowledge, added a <strong>dismiss button</strong> and cleaned up the UI a bit.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2ZXTcIebD5nleKM9SnJLjA.png" /><figcaption>A cleaner Obie Suggest experience</figcaption></figure><ul><li>Added these new <strong>Insights: </strong>Obie Suggest, Tickets Created, Ticket Deflection &amp; Adoption Rate.</li><li>As well as made the following <strong>Insights</strong> more intuitive: Channels &amp; Questions.</li><li>Obie will now follow-up with the original asker of a question when <strong>Requests </strong>are filled by admins.</li><li>We made some underwhelming, but necessary improvements to <strong>reporting. </strong>Go ahead, set one now!</li><li>Refactored load times for the <strong>Invite People </strong>and <strong>Team </strong>features, for our larger organizations.</li></ul><p>There’s more, but I think you’ve had enough. As always, we’re eager to hear what you think about anything we’re officially releasing today or anything else for that matter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dac564876395" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/why-we-rebuilt-our-native-knowledge-base-yet-another-silo-dac564876395">Why we rebuilt our native knowledge base (yet another silo)</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Technical Changes from the Obie Dashboard Redesign]]></title>
            <link>https://medium.com/tasytt-inc/technical-changes-from-the-obie-dashboard-redesign-47a89fd8b580?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/47a89fd8b580</guid>
            <category><![CDATA[code]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[obie]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Alex Sopinka]]></dc:creator>
            <pubDate>Wed, 19 Jun 2019 19:34:30 GMT</pubDate>
            <atom:updated>2019-06-19T19:34:30.647Z</atom:updated>
            <content:encoded><![CDATA[<p>It was a long time coming: improvements to <a href="https://obie.ai/">Obie</a>’s dashboard. I wrote the dashboard very early on in the company, and have since learned and grown so much in my development skills, as most coders do over a period of years. My team and I worked diligently in Q1 to redesign and speed up the dashboard. We’re extremely happy with the release and wanted to share some of the more technical aspects.</p><h4><strong>Redesigned UI and UX</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qbwWYg6YkMLHKx4xVS7GIg.png" /></figure><p>If you’re a long-time Obie user, and visit the dashboard, it will be very obvious that there have been changes. The UI is completely redesigned and much more beautiful now. There are also UX tweaks everywhere, based on feedback from users, about completing actions such as user management, permission management, and navigation through the dashboard in general.</p><h4><strong>Domain Migration</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/348/1*debod3tE2qXn5nRTnCYtpQ.png" /></figure><p>The dashboard used to be on the tasytt.com domain, but this caused a bit of confusion when we launched Obie 2 years ago. We’ve moved everything over to the obie.ai domain now and the consistency across the product is already providing a much cleaner experience. Dashboards can be viewed at https://&lt;subdomain&gt;.obie.ai</p><h4><strong>Async</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/753/1*trZzRsPq4iSDnAs_VnG9vg.png" /></figure><p>We rewrote many functions to work asynchronously. Instead of loading data on the server before the page is served, we now display the page as quickly as possible and then call our internal APIs to get any of the meaty data needed on the page.</p><h4><strong>Code Cleanup</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*rRX_bry9KhPVHbj8MfuZrA.png" /></figure><p>Because the dashboard was the first thing we built at Obie.ai, it’s gone through the growing pains alongside the rest of the company. Dead code, failed features, and massive blocks of commented code were lingering everywhere. To be clear, this existed due to sheer laziness, recklessly fast product iterations, and not really knowing where the product was headed. While the unused code didn’t really matter much to end-users, we got rid of all of it to tighten up the codebase. There <em>were</em> places where some of these unused features were still being initialized and this <em>did</em> have an impact on the speed of the dashboard, so we were happy to remove them.</p><h4><strong>Code Optimization</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*55YRH_h_RS0nS6PpJkyAiw.png" /></figure><p>All of the data retrieval server-side was audited to ensure database calls were optimal, targeted, and running simultaneously where possible. Many poorly written actions were fixed, and we hope to find more in the future, because that means we’re learning.</p><h4><strong>Caching</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/674/0*P9UbQhG3QTuWgCwc.png" /></figure><p>We started storing some of the more static data in Redis. Sometimes manipulation is needed server-side, so if the data doesn’t change much, we can cache the final data model after the first load for speedier subsequent loads. While our databases and servers are fast, Redis is faster, and we focused on cutting down 500ms to 250ms, 250ms to 100ms. Any little wins we could achieve, we took. Those 250ms operations start to add up quick!</p><h4><strong>HTTP/2</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/685/0*loy3clfGAOiunc1p.png" /></figure><p>In case you haven’t heard, HTTP2 is the shit. The main feature is called request multiplexing, and what this means is that multiple requests for data can be sent over a single connection to a web server, instead of multiple requests requiring multiple connections. The overhead is drastically reduced and this means faster load times all around. You can read more about HTTP/2 here: <a href="https://medium.com/@factoryhr/http-2-the-difference-between-http-1-1-benefits-and-how-to-use-it-38094fa0e95b">https://medium.com/@factoryhr/http-2-the-difference-between-http-1-1-benefits-and-how-to-use-it-38094fa0e95b</a></p><h4><strong>Standalone, Fast Servers</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*n6m4gwCpP35GhxcA.jpg" /></figure><p>We migrated the entire dashboard and APIs to dedicated servers. This means we can scale pretty much infinitely if we need to now. Obie also communicates with the dashboard servers often, so the dedicated and faster servers let Obie respond to you more quickly with knowledge or a snappy remark.</p><p>There’s likely a few technical enhancements we made that I’ve missed. Between launching <a href="https://obie.ai/itsm">our robust Jira Service Desk integration</a> and deleting all that nostalgic code, it was a whirlwind Q1 2019.</p><p>We haven’t slowed down in Q2 2019 either. Improved Obie search results and natural language understanding is in Beta for users who opt in, and the frequently-requested slash command is now live. Read more about all the latest and greatest here: <a href="https://blog.obie.ai/a-brand-new-way-to-search-for-knowledge-at-work-e4e0519f5cc0">https://blog.obie.ai/a-brand-new-way-to-search-for-knowledge-at-work-e4e0519f5cc0</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47a89fd8b580" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/technical-changes-from-the-obie-dashboard-redesign-47a89fd8b580">Technical Changes from the Obie Dashboard Redesign</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A brand new way to search for knowledge at work]]></title>
            <link>https://medium.com/tasytt-inc/a-brand-new-way-to-search-for-knowledge-at-work-e4e0519f5cc0?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/e4e0519f5cc0</guid>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[obie]]></category>
            <category><![CDATA[knowledge-sharing]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[slack]]></category>
            <dc:creator><![CDATA[Chris Buttenham]]></dc:creator>
            <pubDate>Mon, 17 Jun 2019 18:10:37 GMT</pubDate>
            <atom:updated>2019-06-17T14:47:37.959Z</atom:updated>
            <content:encoded><![CDATA[<p>Massive product updates for Obie and some design thinking behind them</p><p>Summer (or lack there of) here in Canada is near, and it’s only been 2 months since our <a href="https://blog.obie.ai/the-future-of-obie-65f880161dfc">last product update</a> (a major one, at that) but we have so much to share, including some massive changes and updates to the product, that we couldn’t wait another minute. So, let’s get right into it:</p><ul><li><strong>/obie</strong> — a completely brand new way to search for knowledge at work. You can now type /obie in any channel and ask questions privately with the ability to share relevant knowledge that Obie returns with a click of a button. The /obie slash command with respect your integration settings and Book permissions.</li></ul><p><strong>Note:</strong> if you’re an Obie customer and have not already authorized the new Slack scopes, you will <strong>not</strong> be able to see the slash command. You can <a href="http://bit.ly/AuthorizeObieAppAction">click here</a> to authorize.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1qQMsbP6qINmiLBLgH8udQ.png" /></figure><p><strong>tl;dr</strong></p><p>Now, you may be thinking: “shouldn’t Obie have already worked with slash commands?”. Perhaps. A lot of bots have leveraged the slash command within the Slack platform, but we don’t think it’s an obvious user experience for all users in every application. So we wanted to share some design thinking behind why we decided that we will introduce this important change now, after so long.</p><p>See at first, we thought users wanted to interact with Obie directly. We imagined a very private user experience for the product, and while that was true, increasingly we saw our most successful users bring Obie into channels—within the workflow of how and where questions are naturally asked. Our initial answer to that was <strong>Obie Suggest </strong>which is a feature that, like the name implies, suggests relevant FAQs, documents or knowledge articles to questions that naturally occur within channels Obie has been invited to (without having to mention him). While <strong>Suggest </strong>remains one of our most powerful features, we identified an increasing need to replace the, quite frankly, clunky user experience of mentioning @ Obie. The main challenge with this original experience is that it gums up the channel with unwanted information and is distracting to others in the channel. We believe we now have the best and most flexible way to search for knowledge across your organization, no matter where you are in Slack. Give it a try!</p><ul><li><strong>Add FAQs from conversations in Slack</strong> using the new Obie ‘message action’</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*VwlSGehNcmK6lHEmSTD7Zw.png" /><figcaption>Building your knowledge base just got a whole heck of a lot easier!</figcaption></figure><ul><li><strong>Obie Suggest </strong>was already a feature, yes, but nameless—voila, now it has a name! We’ve also made some pretty important improvements since its beta debut over a year ago. You can now upvote, downvote, see up to 12 results (3 per page), ‘Ask a Channel’, manage FAQs and of course, share with channel!</li><li>Content verification is now baked into the Obie FAQs feature (on by default). You can adjust the verification interval (amount of time before Obie deems knowledge out of date) under Configure &gt; Advanced &gt; Content Verification. You can also turn on Content Verification BETA for Google Drive, Confluence and the Obie knowledge base.</li><li>FAQs got a brand new facelift in the web. We think this represents a much more intuitive and real-estate efficient feature. No functionality was hurt in the cosmetic experimentation of Obie FAQs.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qZPvg5tqFjSjmYr1G1Mb9Q.png" /><figcaption>Now you can fit many more FAQs in a single view!</figcaption></figure><ul><li>We’ve limited results to 3 per page when asking Obie questions (via DM, slash command or Suggest) to a total of 12. Hopefully, this is a little easier on the eyes.</li><li>To combat the “you don’t know what you don’t know” issue, we’ve added the currently active integrations to the search loading message to give users an idea of where they can expect to get knowledge from.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/766/1*p2bid8Apa--9Q5tRX95jdA.gif" /><figcaption>At the very least, something to look at while you wait?</figcaption></figure><ul><li>Content Creators rejoice! This global user permission can now access and add FAQs in the Obie web interface. Just head over to <strong>teamname.obie.ai/faq</strong> to give it a try.</li><li>We’ve completely redesigned the user onboarding and ‘help’ messages head-to-toe (not exciting to most) which includes the ability to formally <strong>invite your teammates </strong>and fellow knowledge experts to Obie (formally, that is)<strong>. </strong>You can do this in the web by clicking ‘Invite People’ just below your team name.</li><li><strong>Big search improvements </strong>are coming to Obie. We’ve completely rebuilt the underlying search technology from the ground up over the last 6-months. This includes our natural language processing as well as our search algorithm. We are releasing these improvements in phases, so this certainly will be the first of many updates you’ll hear about it. Phase 1 is in BETA and on for some teams. Let us know if you’re brave enough to try it!</li><li>On a similar note, Obie now returns the keywords he detected when he cannot find anything at all. Great for troubleshooting or rewording your question to find what you’re looking for.</li><li>You can now see the number of upvotes or downvotes that a given result has in accordance to the question asked (specifically, the ‘topic’/keywords extracted from that question). Our goal, always, is to try and give you the most context possible to find the knowledge you need at work. Hopefully, this will help solidify whether or not the knowledge you’re trying to access is still relevant.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9S9XPSfDaNDE7guS3zVDvQ.png" /><figcaption>Enjoy the dopamine hit when you see the upvote number increase 😍</figcaption></figure><p><strong>Noteworthy bug fixes:</strong></p><ul><li><strong>Having to login/authorize too many times. </strong>Oh boy, well, we’re sorry. We sincerely thought this was rectified months ago. Turns out, it wasn’t. After finding a pesky (and quite hidden) browser expiry setting, this is finally put to rest. Sorry for the extra step in getting what you need.</li><li>Google Drive (Team Drives) users were experiencing some sync issues after some API changes to the way Obie recognizes newly added documents. This should be rectified indefinitely.</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e4e0519f5cc0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/a-brand-new-way-to-search-for-knowledge-at-work-e4e0519f5cc0">A brand new way to search for knowledge at work</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Future of Obie]]></title>
            <link>https://medium.com/tasytt-inc/the-future-of-obie-65f880161dfc?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/65f880161dfc</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[obie]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[product-updates]]></category>
            <dc:creator><![CDATA[Chris Buttenham]]></dc:creator>
            <pubDate>Mon, 15 Apr 2019 11:31:00 GMT</pubDate>
            <atom:updated>2019-04-15T11:31:00.856Z</atom:updated>
            <content:encoded><![CDATA[<p>Welcome to the all new Obie experience!</p><p>Over the last 2 years our team has poured their heart and soul into making knowledge more accessible for organizations of all shapes and sizes. When we started this, Obie was one of a very small handful of apps on Slack. We have since grown to be one of the most installed apps across the platform and beyond:</p><ul><li>Over <strong>300k questions asked</strong></li><li>More than <strong>7,000 installs</strong></li><li>Almost<strong> 2,000 Google Drive’s</strong> integrated</li><li><strong>Countless hours saved</strong> looking for knowledge at work</li></ul><p>In doing so, we have had to learn to get focused on what the direction of Obie must be in order to support our customers at the level we know you deserve.</p><p>Today, we are officially releasing the new Obie experience and saying <strong>goodbye to our </strong><a href="http://obie.ai/pricing"><strong>free tier</strong></a>. Making this change will allow us to focus on building a more robust product for Obie customers that helps make knowledge and documentation more accessible at work. It’s important to ensure we are building both a successful product and a successful business. After much consideration, we believe this is the best route to take to strike that balance.</p><p>More importantly, I wanted to break the silence on (what used to be) somewhat regular product updates. Our wonderful friend, <a href="https://medium.com/u/20aba1488490">Carolyn Chong</a> used to write these but today, you’re stuck with me.</p><p>Here are the <strong>major updates</strong> since the .. <a href="https://blog.obie.ai/obie-1-0-changelog-for-slack-aaedbe20f48b">last update</a> 😅 tl;dr</p><ul><li>A complete re-imagination, redesign and in a lot of places, rebuilt web experience for Obie.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gNUcRFkSw_GlCldtS7Kf2w.png" /><figcaption>The new knowledge base view on the Obie Platform</figcaption></figure><ul><li>Books &gt; <a href="http://tas.yt/t/qOBAs3"><strong>Chapters</strong></a><strong> &gt; </strong>Pages. Yes, you read that right. Quite possibly the <strong>most requested </strong>knowledge base<strong> </strong>feature is now available for your organization needs.</li><li>Integration Settings is now <strong>Configure. </strong>Configure is no longer a setting, it’s a power house of a feature that allows you to manage 3rd party integrations (i.e. Confluence) and point specific folders and spaces to specific channels in Slack.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*vD_t0yTLNbovYgCyUdvZgA.gif" /><figcaption>Specify the spaces and folders Obie can search across different channels in Slack</figcaption></figure><ul><li>Obie Responses are now <a href="https://hq.obie.ai/books/1747289/chapters/2"><strong>FAQs</strong></a>. To say we are bad at naming conventions here would be an understatement. We felt FAQs was a much better representation of what the feature means for Obie users. Oh, and we redesigned it, too.</li><li><strong>Content Verification (beta) </strong>is a new feature we built to make sure knowledge stays up to date and relevant. Obie will intelligently notify content owners when their knowledge is getting stale and also visually display whether or not information is trustworthy to users when they ask Obie questions.</li><li>We built a robust analytics dashboard called <strong>Insights </strong>so that you can keep up with what documentation and knowledge is used most often, or not. You can track how many questions your team is asking and see how many <strong>Requests </strong>for new knowledge there are. Oh, and you can also send these insights via Slack with our reporting feature.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RpX3FPROlBZTgeJHvVXBVQ.png" /><figcaption>Obie Insights Dashboard</figcaption></figure><ul><li>We got rid of the concept of <strong>publishing </strong>Books and made all Books visible by default. Which makes sense, because you have to assign Books for them to be accessible anyways—duh! You can now <strong>archive </strong>a Book, though.</li><li>We added <strong>guest access </strong>so you can control how single-channel and multi-channel guests operate with Obie.</li><li>Remember the whole thing about us naming features? Yeah, we renamed <strong>Request Response</strong> to <strong>Ask a Channel</strong>. Of course, that’s not all—we completely changed the way Obie crowdsources knowledge from your team in Slack.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/984/1*cMMZVeRUgmRJdvksdX_NPw.gif" /><figcaption>If Obie can’t find an answer, he’ll help you hunt one down!</figcaption></figure><ul><li>We are proud to integrate with <a href="http://readme.io/"><strong>ReadMe</strong></a><strong> </strong>so Obie can now search your product documentation in Slack if you use this wonderful tool.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*B3wejtqZ7vJCyNz8G1Pjag.png" /></figure><ul><li>We also added a major <a href="http://obie.ai/itsm"><strong>Jira Service Desk</strong></a><strong> </strong>integration that brings ticket deflection and resolution all within Slack.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AEIot1OhzCLjj36pMg33CA.png" /><figcaption>Jira Service Desk in Slack by Obie.ai</figcaption></figure><ul><li>ALSO, official support for our <a href="http://trello.com/"><strong>Trello</strong></a> integration that allows you to search across your boards. Plus, Taco needed a friend.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/967/1*fQQqVI728ZgEQhcyGZ6xtw.png" /><figcaption>Obie &amp; Taco from Trello</figcaption></figure><ul><li>We completely redesigned the user management functionality within Obie which was previously found under <strong>Team.</strong></li><li>We also got rid of a couple things that weren’t aligned with the vast majority of Obie customers: Quizzes and Jira issues search.</li></ul><p><strong>We’ve fixed a lot of stuff since the last update but here are some noteworthy mentions:</strong></p><ul><li>The FAQs editor was funky to type in. This was annoying. We’re sorry—it’s fixed now.</li><li>Obie was asking you to authorize too many times when trying to access results from Slack. Very annoying, but luckily now rectified. We appreciate your patience.</li><li>Various search improvements. Specifically, better handling of punctuation, ranking and result matching as well.</li></ul><p><strong>Bells and whistles on there way out next:</strong></p><ul><li>Rebuilt <strong>Page editor</strong> for the Obie knowledge base</li><li><strong>Chrome</strong> extension</li><li><a href="https://www.salesforce.com/ca/products/service-cloud/overview/"><strong>Salesforce</strong></a> integration</li><li><strong>Massive </strong>search improvements</li><li>and so much more..</li></ul><p>We’re dying to hear your feedback, so please don’t hesitate to <a href="http://bit.ly/ObieHelp">chat with us</a>, check out the <a href="http://bit.ly/ObieHelpGuide">new help guide</a> or follow along on our <a href="https://trello.com/invite/b/FGu1ZXG0/20945deeeeeafdf207b56d679a5c30e4/obieai-roadmap">product roadmap</a> for more details and updates.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65f880161dfc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/the-future-of-obie-65f880161dfc">The Future of Obie</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Obie 1.0 Changelog for Slack]]></title>
            <link>https://medium.com/tasytt-inc/obie-1-0-changelog-for-slack-aaedbe20f48b?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/aaedbe20f48b</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[changelog]]></category>
            <category><![CDATA[slackbot]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <dc:creator><![CDATA[Carolyn Chong]]></dc:creator>
            <pubDate>Fri, 08 Jun 2018 18:49:15 GMT</pubDate>
            <atom:updated>2018-06-08T18:49:15.250Z</atom:updated>
            <content:encoded><![CDATA[<h4>New things released and bad things fixed</h4><h4>Here’s what’s new:</h4><ul><li>We’re outta beta, gata!</li><li>Our onboarding experience is better. It’s not perfect, but it is, at the very least, better. And by better we mean simpler.</li><li>Ever wish Obie could search GitHub or Box? Wish: Received.</li><li>Good news for our friends who use Jira or Trello: Early access to these integrations starts…NOW! <a href="http://bit.ly/ObieSupport">Chat with us to learn more</a>.</li><li>We added a brand new way to view engagement and trends of your team’s use of Obie. What is it, you ask? A customized report delivered straight to you in Slack. We’re testing it with select teams. <a href="http://bit.ly/ObieSupport">Talk to us to try out the new reporting</a>.</li><li>AND a whole new way to visualize engagement and trends on the dashboard. Also testing this new addition with select teams. <a href="http://bit.ly/ObieSupport">Be one of the first to take it for a test drive by reaching out</a>.</li><li>Marvellous changes to <a href="http://tas.yt/t/TzUGTw">Responses</a> on the dashboard: A way to verify added responses, a way to see requests, a way to add unlimited responses, a way to sort all of the above.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I9h1NnRn-mXZyPzsipH7eQ.png" /></figure><ul><li>Just in case you missed what we sneakily added above: Yes, we have removed the limit on the number of responses you can manage. Previously, users were limited to managing ten responses on the Free plan. Now you can add, edit, delete as many responses as your heart desires. Go for it.</li><li>We said goodbye to some bloat features. Essentially, some features that you never used are no longer there. <a href="https://blog.obie.ai/somethings-that-you-never-used-are-no-longer-there-d5df03ba1399">RIP</a> to the marketplace, user profiles, team member information, and forms.</li><li>Small, but pleasant: we now display four results, with the opportunity to see up to a maximum of twelve by clicking on a next button. Previously, you could only see five, and you told us that wasn’t enough. We also added file type icons so you know what you’re getting before you even click on the link. Oh, and we added a ‘View Folder’ button to all Google Drive results, and a ‘View Book’ button to all Obie Page results, just in case you want a sense of where that result is living.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UaqQFn-TI0U_8Jl_YNtrXg.png" /></figure><ul><li>You can kiss goodbye to editing responses using the message box (or you could if you knew that’s how it was done) because editing is now done using dialogs. Much, much more intuitive.</li><li>A new way to get an answer when there isn’t one by asking Obie to nudge a colleague. Simply tap ‘Submit Request’ to enjoy.</li><li>You can now search Obie using plain simple keywords, instead of prefacing every question with who, what, where, etc. etc. If you want to.</li><li>OH! Hi. I was just wondering… um… OK, fine: You can now get suggested answers to questions asked in channels, without having to @mention Obie. Awkward no replies begone.</li><li>We updated our security and privacy policies to ensure we’re GDPR compliant. Because privacy is important.</li><li>The redesigned website is, we think, gosh-darned delightful.</li><li>A deep re-visit of our NLP, tweaking things and tidying up and generally making it better in myriad abstruse ways.</li></ul><h4>Here’s what we fixed:</h4><ul><li>A performance problem where Obie would get stuck in a crash loop. There are a lot of things we want you to be able to do with Obie. All of them, it turns out, involve you being able to access Obie. Apologies.</li><li>When attempting to access Obie Pages, some users experienced slow load times (yes, again). Which was no bueno. Sorry about that, some users.</li><li>Basically, on long responses displayed on the dashboard, in just the right scenario, the text would start to appear behind the resize toggler, making it difficult to see the text and the toggler. Now, it’ll never do that. We put it back in its rightful place.</li><li>Attempting to copy and paste text onto a Page from an outside source now actually copies and pastes.</li><li>It pains us to say that Obie wasn’t always remembering your upvote history, wouldn’t respond to questions starting with who’s, what’s etc, and you couldn’t actually search the answer of a question you stored with Obie…just the question. This was maddening, we are very sorry for it, and very happy to have fixed it.</li><li>Our error pages. They were just full of errors. Now they’re gone… the errors, not the error pages, because those are not errors.</li></ul><p><em>That’s all she wrote, folks. Obie 1.0 is live in the </em><a href="http://bit.ly/slackobie"><em>Slack App Directory</em></a><em>. </em><a href="http://bit.ly/tawktosupport"><em>Send us a note</em></a><em> or </em><a href="http://bit.ly/obietwitter"><em>tweet</em></a><em> to let us know what you think. We love bugs, so send those our way, too.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aaedbe20f48b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/obie-1-0-changelog-for-slack-aaedbe20f48b">Obie 1.0 Changelog for Slack</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Obie 0.1 [Beta] Changelog for Stride]]></title>
            <link>https://medium.com/tasytt-inc/obie-0-1-beta-changelog-for-stride-eb7b93c79516?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/eb7b93c79516</guid>
            <category><![CDATA[knowledge-management]]></category>
            <category><![CDATA[changelog]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[atlassian]]></category>
            <dc:creator><![CDATA[Carolyn Chong]]></dc:creator>
            <pubDate>Fri, 08 Jun 2018 18:48:21 GMT</pubDate>
            <atom:updated>2018-06-08T18:48:21.378Z</atom:updated>
            <content:encoded><![CDATA[<h4>Our first changelog for Obie in Stride</h4><p>We recently wrote about <a href="https://blog.obie.ai/building-obie-ai-for-stride-3f63da002e53">our experience building Obie for Stride</a>. Suffice it to say we’re proud of v1 and grateful for the feedback from our early adopters.</p><p>It’s important to us that you know that we’re working hard to make Obie better. Below you’ll be able to read and see some of the things we’ve released or fixed of late, both big and small, because every little thing matters.</p><h4>Here’s what’s new:</h4><ul><li>Good news for our friends who use Jira or Trello: Early access to these integrations starts…NOW! <a href="http://bit.ly/ObieSupport">Chat with us to learn more</a>.</li><li>We added a brand new way to view engagement and trends of your team’s use of Obie. What is it, you ask? A customized report delivered straight to you in Slack. We’re testing it with select teams. <a href="http://bit.ly/ObieSupport">Talk to us to try out the new reporting</a>.</li><li>AND a whole new way to visualize engagement and trends on the dashboard. Also testing this new addition with select teams. <a href="http://bit.ly/ObieSupport">Be one of the first to take it for a test drive by reaching out</a>.</li><li>Marvellous changes to <a href="http://tas.yt/t/ole73I">Responses</a> on the dashboard: A new way to verify added responses, a new way to see requests, a new way to add unlimited responses, a new way to sort all of the above.</li><li>Just in case you missed what we sneakily added above: Yes, we have removed the limit on the number of responses you can manage. Previously, admins were limited to managing ten responses on the Free plan. Now you can add, edit, delete as many responses as your heart desires. Go for it.</li><li>We updated our security and privacy policies to ensure we’re GDPR compliant. Because privacy is important.</li><li>The redesigned website is, we think, gosh-darned delightful.</li><li>A deep re-visit of our NLP, tweaking things and tidying up and generally making it better in myriad abstruse ways.</li><li>Support for our new search bar in the sidebar. Did we mention we have a search bar now? Well, we have a search bar. Bring Obie to every room and conversation.</li><li>Sharing a result is now a thing, too. Just head to any result in the sidebar and click the share icon on the card. Bam! Obie will share the result to the room you have open. Sharing is the new copy/pasting, folks.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*3hDKD56w-znAn9dfgTqhnQ.gif" /><figcaption>The new search bar allows you to search Obie from any room. See a result you want to share with your team? Just click share. Simple as that.</figcaption></figure><h4>Here’s what we fixed:</h4><ul><li>A performance problem where Obie would get stuck in a crash loop. There are a lot of things we want you to be able to do with Obie. All of them, it turns out, involve you being able to access Obie. Apologies.</li><li>When attempting to access Obie Pages, some users experienced slow load times (yes, again). Which was no bueno. Sorry about that, some users.</li><li>Basically, on long responses displayed on the dashboard, in just the right scenario, the text would start to appear behind the resize toggler, making it difficult to see the text and the toggler. Now, it’ll never do that. We put it back in its rightful place.</li><li>Attempting to copy and paste text onto a Page from an outside source now actually copies and pastes.</li><li>It pains us to say that Obie wasn’t always remembering your upvote history, wouldn’t respond to questions starting with who’s, what’s etc, and you couldn’t actually search the answer of a question you stored with Obie…just the question. This was maddening, we are very sorry for it, and very happy to have fixed it.</li><li>If you got a single result from Obie, we wouldn’t let you upvote or downvote that result, which meant there was no way to boot out a bad result, or give praise to a good result. Now, you can boot and praise away, regardless of how many results are returned.</li><li>We spliced some wires we shouldn’t have, causing an error when accessing the dashboard via the ‘dashboard’ command. Now you’ll get the dashboard.</li><li>Our error pages. They were just full of errors. Now they’re gone… the errors, not the error pages, because those are not errors.</li></ul><p><em>That’s all she wrote, folks. Obie 1.0 [Beta] is live in the </em><a href="https://marketplace.atlassian.com/apps/1218544/obie-for-stride?hosting=cloud&amp;tab=overview"><em>Atlassian Marketplace</em></a><em>. </em><a href="http://bit.ly/tawktosupport"><em>Send us a note</em></a><em> or </em><a href="http://bit.ly/obietwitter"><em>tweet</em></a><em> to let us know what you think. We love bugs, so send those our way, too.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eb7b93c79516" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/obie-0-1-beta-changelog-for-stride-eb7b93c79516">Obie 0.1 [Beta] Changelog for Stride</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three Reasons You Should Try Stride]]></title>
            <link>https://medium.com/tasytt-inc/three-reasons-you-should-try-stride-ec861ed4006d?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/ec861ed4006d</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[stride]]></category>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[enterprise-messaging]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[Chris Buttenham]]></dc:creator>
            <pubDate>Thu, 29 Mar 2018 01:13:42 GMT</pubDate>
            <atom:updated>2018-03-29T01:13:46.673Z</atom:updated>
            <content:encoded><![CDATA[<p>Over the last 3–4 years enterprise messaging has completely disrupted the workplace and truly paved a new road for the possibilities of the future of work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bEiIJGiHVplCxA59XozVPw.png" /><figcaption>The Obie.ai team using Stride</figcaption></figure><p>Given that we’re “in the space” the team and I at Obie.ai have tasted all of the flavours (sp: I’m Canadian) of enterprise messaging platforms. To be honest, they all have their pros and cons. We’ve done a deeper dive into the new <a href="https://techcrunch.com/2018/03/27/stride-atlassians-slack-competitor-hits-general-availability/">Atlassian Stride</a> over the past few months while bringing Obie to Atlassian customers. Our goal of partnering with Atlassian is to enable companies to access their company knowledge and documentation right within Stride. We wrote<a href="https://blog.obie.ai/building-obie-ai-for-stride-3f63da002e53"> how we built this here</a>. So, I wanted to share some things I personally noticed when using Stride.</p><h3>1. You Get More Done</h3><p>Since starting to use Stride the one thing that stands out to me is <strong>focus mode. </strong>Focus mode is a feature, but so much more than that. It actually helps me get more done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/572/1*qnEC4B_Hi8qwSaqcW0Jivg.gif" /><figcaption>Focus mode on Stride</figcaption></figure><p>Reducing the noise from someone’s workflow is definitely something we’re familiar with at Obie.ai and something that is becoming increasingly topical in the modern workplace. An influx of emails, DM’s, pings — that damn notification spark in your dock! While teams inhabit messaging tools more and more and attention shifts deeper, disruptions and distractions have the potential to significantly chip away at your productivity — the exact problem these tools promise to solve for us. To me, Atlassian has done an excellent job at designing Stride with this in mind. By enabling focus mode, with just one click you can mute <strong>all </strong>incoming notifications AND eloquently communicate that with the rest of your team. Not only that, but I feel that the Stride team has been very thoughtful of when, even out of focus mode, they are sending you that notorious notification <em>spark </em>and push notifications. I have found a great balance when using Stride of “being in the know” of the happenings with the team, but not getting sucked into the productivity loss abyss.</p><h3>2. The Sidebar (and the apps)</h3><p>If you’re not a Stride user, you likely have no idea what the “sidebar” is, but it’s wonderful! Of course, from a <em>biased</em> designer standpoint the sidebar (seen below) offers endless possibilities to create rich experiences right in Stride. But from a user’s perspective, I’m really enjoying some of the new apps that leverage the sidebar in the <a href="https://marketplace.atlassian.com/addons/app/stride">Stride Marketplace</a> like: <a href="https://marketplace.atlassian.com/plugins/polly-6dadefc4-351c-4ff6-8a43-906b1d681506/cloud/overview"><strong>Polly</strong></a><strong> </strong>the team polling bot, <a href="https://marketplace.atlassian.com/plugins/standbot-3d80d0a8-5099-4b0d-a650-aa5d3e92ee50/cloud/overview"><strong>Standbot</strong></a> for team standups and, I can never get enough of <a href="https://marketplace.atlassian.com/plugins/trello-f90bf32a-0bbf-4900-b6e9-b63ce043bb1a/cloud/overview"><strong>Trello</strong></a> in my life, so why not bring more of it in Stride!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LyLI2cjlrpf6xwjgOwcgfw.png" /><figcaption>How we leverage the sidebar for Obie (on the right)</figcaption></figure><p>The sidebar really helps apps go that “extra mile” past just conversational experiences by more utility to solutions integrating with Stride. To me, from a design perspective, the sidebar is a way less invasive way to use my favourite app or feature no matter where I am in Stride.</p><h3>3. Meetings That Work!</h3><p>Speaking of the sidebar, you can easily start Stride meetings <strong>anywhere </strong>with one click in the sidebar. Video conferencing isn’t a very novel concept in 2018, but that doesn’t mean we are flooded with excellent choices. We have a Telsa floating in space, but we haven’t cracked the code on team conferencing? Maybe Stride has. Honestly, <strong>it just</strong> <strong>works. </strong>Of course, you have to have the standard prerequisites (like a stable internet connection), but really, it works!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w4C-sX7uR85FHamZKiY6Lg.png" /><figcaption>Having fun with Stride meetings</figcaption></figure><p>You can pop in and out of meetings with ease via Stride rooms and DMs. You can even <strong>invite people from outside your organization to join a meeting! </strong>I’ll be honest, I stumbled across that beautiful feature by accident last week and it made my day. Now we can do client calls right from the comfort of Stride and have comfort in knowing we’re going to have a stable call!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Gfc8Krc0I2VfftcOKsMGPw.png" /><figcaption>Stride meetings</figcaption></figure><p>And that’s all for now folks! I’m really bullish on enterprise messaging as a whole, so it’s always exciting to see updates from Slack, Cisco Spark, Microsoft Teams and the recent launch of Google Hangouts Chat, but wanted to take some time to share what’s really special about Stride since I’ve started to use it.</p><p>I would love to hear what your experience has been like with Stride, so please reach out or sound off in the comments if you have something to share.</p><p>And if you do end up taking <a href="http://stride.atlassian.com/">Stride</a> for a test spin make sure to try out <a href="https://marketplace.atlassian.com/plugins/obie-a9020b8d-9051-4280-aab2-6db8b4f68ed2/cloud/overview">Obie</a> for your team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec861ed4006d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/three-reasons-you-should-try-stride-ec861ed4006d">Three Reasons You Should Try Stride</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Some things that you never used are no longer there]]></title>
            <link>https://medium.com/tasytt-inc/somethings-that-you-never-used-are-no-longer-there-d5df03ba1399?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/d5df03ba1399</guid>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Carolyn Chong]]></dc:creator>
            <pubDate>Thu, 08 Mar 2018 23:05:50 GMT</pubDate>
            <atom:updated>2018-03-16T15:14:55.693Z</atom:updated>
            <content:encoded><![CDATA[<h4>Saying goodbye to bloat features</h4><p>Obie is spring cleaning his dam. With that comes the removal of a handful of features on Obie’s dashboard for all teams, including teams now and into the future. The features will be removed on March 9. We’re excited to retire off older unloved ideas so that fresh new ideas can take their place.</p><p>An end of life will occur for the following features:</p><ul><li>Marketplace</li><li>User Profiles</li><li>Team Member Information</li><li>Custom Forms</li></ul><p>We’re honoured to be able to help companies organize their knowledge and make it universally accessible and useful. Our dashboard was designed as an easy way for teams to onboard and train new hires. Over time, Obie has evolved from our company mascot to a productive beaver, helping teams save time by accessing their collective knowledge and documentation.</p><p>We’ve found that the teams that see the greatest success are the ones who use Obie to search for and share information. For that reason, moving forward, all of our efforts made on the dashboard will be focused on reducing context switching when accessing the things you need to get stuff done, and administrative features to ensure knowledge is accessible, useful and up to date.</p><p>We know someone out there has built some of these features into their workflow. To help minimize the interruption, please reach out to us, and we’ll be happy to find a solution that works for you.</p><p>Team Obie</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d5df03ba1399" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/somethings-that-you-never-used-are-no-longer-there-d5df03ba1399">Some things that you never used are no longer there</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building Obie.ai for Stride]]></title>
            <link>https://medium.com/tasytt-inc/building-obie-ai-for-stride-3f63da002e53?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/3f63da002e53</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[enterprise-chatbot]]></category>
            <category><![CDATA[atlassian]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[John Kyeremeh]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 21:47:21 GMT</pubDate>
            <atom:updated>2018-02-27T21:47:21.091Z</atom:updated>
            <content:encoded><![CDATA[<p>How we connect knowledge to your fingertips in Stride</p><h3>How we connect knowledge to your fingertips in Stride</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ireTPmcesD2z_DWeaXsT2A.jpeg" /></figure><p>Whether you work in a small team or a larger enterprise juggling and finding the right internal knowledge when you need it is no easy task. And for teams that rely heavily on messaging (which most organizations do), it’s especially easy to allow conversational knowledge to not be turned into institutional knowledge. These days it’s all too common to have business units put into isolated groups that rarely talk, share information, or collaborate. When specific knowledge does need to be found it’s hard to search for the information, know if the information is up-to-date, or worse there can be too much information to sort through. Information just lives in too many places. We created a bot in Stride to tackle this.</p><p>If you are thinking of bringing your bot from another platform to Stride, here are some lessons we learned launching our app and how we solved key problems. We’ll cover why we chose to use particular commands, give an architectural overview of the application, and walk through considerations we took when building <a href="http://obie.ai/">Obie</a> for Stride.</p><h3>First, some context</h3><p>Messaging does a great job of keeping communication in one place. It makes for a great archive of information. We all know how to search; it’s pretty simple. You type in what you are looking to find. The problem? Getting information from the deepest archives is a challenge.</p><p>For example, looking for a file you accessed a few weeks ago (noise) while only remembering the topic, a few queries, and a bit of context on the content (signal) but not the file name can be a frustrating experience. You have a good idea of what to look for, but there are a lot of places the file can exist and lots of files with similar topics, queries, and context. How can we impact the signal, and reduce the noise?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qAXdOJS7rpLsoVwSxgkCqg.png" /></figure><p>At <a href="http://www.obie.com/">Obie.ai</a>, we tackle this signal and noise issue using messaging, behaviour-based machine learning, and natural language processing to help teams share and access knowledge organization-wide: the bigger the company, the harder the challenge exists of accessing and sharing knowledge. With every search, teams can be more focused and informed with fewer interruptions. Our goal is to ensure employees can get access to relevant knowledge at their fingertips. Whether you have an intranet, Google Drive, GitHub, Confluence, or other Atlassian tools like Trello, knowledge is dispersed and siloed across the organization, making some information inaccessible. Finding information should be an easy process. A defined single source of truth to search for knowledge streamlines the search process for both the employees and organizations looking to make information easier to find so that you can get more done.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KYthC7UGpgQzGTOz4nM-Sw.png" /><figcaption>Obie in Stride fetching a resource</figcaption></figure><p>We were lucky to have heard from many teams, developers and product managers who use a wide range of productivity, developer, and project management tools about common pitfalls: finding information across sources within an organization can create a virtual firehose of information. People didn’t want more knowledge sources. We needed to figure out how to continually reduce the noise so that people can find what is relevant, quickly.</p><p>Our journey building bots on messaging platforms began in 2016. As a team who has been tackling knowledge management for some time now, we feel that messaging has afforded us unique opportunities that we’ve never been able to tackle.</p><p>While building Obie from a prototype to a fully functioning Stride app, we learned some tips and tricks that might be useful for those bot developers hoping to transition their bot to Stride or those looking to build something new. Here are a few takeaways from our efforts to create a valuable experience:</p><h3><strong>1. If you’re building a bot for the first time, try not to bite off too much</strong></h3><p>After being in the bot ecosystem for some time now, we found that the most useful bots typically provide easy ways to get information or collect information using the conversational interface and other interfaces available to them.</p><p>We knew that we had to build a quick prototype with Obie’s knowledge retrieval functionality front and center. The prototype of our Stride app was going to be very simple, but still valuable.</p><p>In addition to the send/receive messaging endpoints, it involved leveraging the following Stride APIs:</p><blockquote><strong><em>User Details:</em> </strong><em>Returns useful information about a given user like their real name, email, and photo.</em></blockquote><h4><strong><em>Usage Example</em></strong></h4><pre>getUser: (cloudId, userId, cb) =&gt; {<br>     auth.getToken((token) =&gt; {<br>         request({<br>         url:       `https://api.atlassian.com/scim/site/${cloudId}/Users/${userId}`,<br>         method: &#39;GET&#39;<br>         headers: {<br>            &#39;Authorization&#39;: &#39;Bearer &#39; + token<br>         }<br>      }, (err, httpRsp, body) =&gt; {<br>         if (cb) {<br>           cb(JSON.parse(body));<br>         }<br>       })<br>    });<br>}</pre><blockquote><strong><em>Conversation rosters: </em></strong><em>Returns a list of user Ids for users in the given conversation.</em></blockquote><h4><strong>Usage Example</strong></h4><pre>getConversationRoster:(cloudId, conversationId, cb) =&gt;{<br>          auth.getToken((token) =&gt; {<br>                  request({<br>                          url:<br>`https://api.atlassian.com/site/${cloudId}/conversation/${conversationId}/roster`,<br>                          method: ‘GET’,<br>                          headers: {<br>                              ‘Authorization’: ‘Bearer ‘ + token<br>                         }<br>                  }, (err, httpRsp, body) =&gt; {<br>                           if (cb) {<br>                                   cb(JSON.parse(body));<br>                            }<br>                 });<br>           });</pre><pre>}</pre><p>We developed the Alpha in about a week at StrideCon. StrideCon is more or less a hackathon week at Mountain Winery in Saratoga, CA, attended by Stride developers and designers. This experience was a unique and timely opportunity that gave us the resources to move quickly. We had entertained talks internally about working within new APIs and we were interested in understanding what it was like to work within the Stride API. This opportunity helped us understand what it would take to bring Obie from other messaging apps into Stride.We tested it and demoed Obie at StrideCom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6YucsDoeLR4IbksmJc_cSQ.png" /><figcaption>View from StrideCon in Mountain Winery Saratoga, CA</figcaption></figure><p>With the help of the Atlassian designers and developers we created a solid proof of concept that helped skyrocket our understanding of the Stride ecosystem. After this experience, we decided to focus on how we were going to translate more of our core product experience into Stride past the Alpha.</p><h3>2. Communicate early to your users what your bot does</h3><p>There should be some information that explains the value of your bot (what it can do) communicated early. You’re going to get users installing just to play around, so it’s a good idea to demonstrate or talk about the value very early on. This is especially important if you want users to invest the time in going through a lengthy onboarding process.</p><p>We focused heavily on educating users through an onboarding process where we could be as specific as possible so new users understand what the bot can or can’t do. After a design review with the Atlassian team, we made several iterations to the onboarding to ensure we communicated our value proposition much earlier than we initially intended.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B8LD2Ph-fzYO49Bj-JQ5cw.png" /></figure><h3>3. Make the first impression count</h3><p>We rely heavily on messaging to introduce users to what Obie can do and we get a sense of users sentiment and first impression — when they are happy and when they are frustrated — using <a href="https://www.dashbot.io/">Dashbot</a>, a bot analytics platform that enables developers to measure user engagement, and <a href="https://amplitude.com/">Amplitude</a>, which allows us to track the web experience of the user experience in addition to the bot experience. We focus extensively on user experience — we measure every click, question, and user reply to make sure the experience with Obie is better than nudging, asking a peer, or going into the knowledge sources directly.</p><p>A neat endpoint we use unique to Stride is the built-in configuration status for apps. We make it mandatory for users to complete onboarding/configuration before using Obie. While Obie is awaiting configuration, there is a status indicator beside his app icon in the side toolbar so that the installer is aware that configuration is required before proceeding to use the app fully.</p><p>To do this, we use:</p><blockquote><strong><em>Conversation Configuration State: </em></strong><em>Updates a given conversation’s configuration state, where configured is either “true” or “false”.</em></blockquote><h4><strong>Usage Example</strong></h4><pre>updateConversationConfig: (cloudId, conversationId, status, cb) =&gt; {<br>          auth.getToken((token) =&gt; {<br>          request({url: ‘https://api.atlassian.com/app/module/chat/conversation/chat:configuration/obie-config/state&#39;,<br>          method: ‘POST’,<br>          headers: {<br>               ‘Authorization’: ‘Bearer ‘ + token,<br>               ‘Content-Type’: ‘application/json’<br>           },<br>           json: {<br>                 configured: status,<br>                 context: {<br>                          cloudId: cloudId,<br>                          conversationId: conversationId<br>                  }<br>             }<br>           }, (err, httpRsp, body) =&gt; {if (cb) {<br>                  cb();}<br>            })<br>            });<br>}</pre><p>This configuration status is important for us since in order to have a good experience, users must first configure Obie within their environment. We’ve found that onboarding with Obie is crucial for success; by guiding the user through connecting an integration and performing their first search, they get the feel of how Obie works. Once the user has completed onboarding we unlock Obie for regular use.</p><h3>4. <strong>Sidebars and Cards: Take advantage of new design challenges for unique opportunities</strong></h3><p>It’s important to think of the type of information you are sending to Stride. Stride has a numerous amount of opportunities to allow developers to display information within its environment. We came up with a unique way to interact with Obie because of what Stride offered.</p><h4><strong>Stride Sidebar &amp; Cards</strong></h4><p><a href="https://developer.atlassian.com/cloud/stride/learning/glances-sidebars/">Stride Sidebars</a> provide a free for all in terms of design and development. Apps can display custom HTML hosted by your app in the right sidebar, like a list of meetings, relevant documents, or open tasks, to displaying contextual information relevant to the conversation.</p><p>We found it useful to display documents related to the search for our particular use case. One thing we took into consideration while embracing the freedom HTML provides was to ensure there is a consistent user experience with Obie and Stride. It’s difficult to create a consistent user experience without guidelines so we used Stride <a href="https://atlassian.design/">design guidelines</a> to create the consistent user experience the user audience would understand.</p><p>We found it beneficial to leverage <a href="https://developer.atlassian.com/cloud/stride/learning/sending-cards/">Stride App Cards</a>. App cards offer information at-a-glance and leverage a wide range of design options. When a user asks Obie a question, instead of showing a list of results within the conversation window, we leveraged the metadata and put this information into an App Card . This user experience ended up being quite favorable even though it wasn’t an experience we were used to. The Sidebar allowed us to avoid making the conversation too crowded by displaying only the top result in the conversation window, and then the rest of the results in the Sidebar.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yg-CTPiR-4812EWUunmitQ.png" /></figure><p><strong>Related Guides</strong></p><ul><li><a href="https://developer.atlassian.com/cloud/stride/learning/glances-sidebars/"><strong>Glances and sidebars</strong></a></li><li><a href="https://developer.atlassian.com/cloud/stride/learning/adding-sidebars"><strong>Adding sidebars</strong></a></li><li><a href="https://developer.atlassian.com/cloud/stride/learning/sidebar-style-guide"><strong>Sidebar style guide</strong></a></li><li><a href="https://developer.atlassian.com/cloud/stride/learning/sending-cards/"><strong>Sending cards</strong></a></li><li><a href="https://developer.atlassian.com/cloud/stride/apis/document/nodes/applicationCard/"><strong>Node — Application cards</strong></a></li><li><a href="https://developer.atlassian.com/cloud/stride/learning/sidebar-style-guide"><strong>Sidebar style guide</strong></a></li></ul><h3>Takeaways</h3><p>Obie integrated into Stride turns Stride into an intelligent source of truth, where you can keep your knowledge up-to-date and access knowledge wherever it lives. In Stride, you can surface relevant information and see how up-to-date information is. Through our focus on listening to our users, relentlessly pursuing a favorable user experience, and making data-driven decisions, we’ve learned that each encounter with a bot builds trust and your goal as you develop your bot is to build a trusted coworker.</p><p>We’ve only scratched the surface of the <a href="https://developer.atlassian.com/cloud/stride/rest/">Stride API</a>, but hopefully you’re now sufficiently excited to build something awesome! Even if your mission and product aren’t tied to the things we aim to solve, hopefully our learnings from this process will help inform your decisions about specific aspects of your bot and save you time as you build it in Stride. We’d really love to see how you use it, and if you do create a great bot in Stride (or move your bot over to Stride), don’t forget to let us know on <a href="https://twitter.com/AskObie">Twitter</a>. If you have any specific questions about the journey feel free to reach out and we’ll be sure to help!</p><p><em>Written by John Kyeremeh, Head of Growth, &amp; edited by the Obie.ai team.</em></p><h3>Think other people would benefit from this article? Click the clap to help them find it ❤</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3f63da002e53" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/building-obie-ai-for-stride-3f63da002e53">Building Obie.ai for Stride</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Obie 0.8 [BETA] Changelog]]></title>
            <link>https://medium.com/tasytt-inc/obie-4-0-beta-changelog-ea0dc7b385a2?source=rss----29d471a161a9---4</link>
            <guid isPermaLink="false">https://medium.com/p/ea0dc7b385a2</guid>
            <category><![CDATA[slackbot]]></category>
            <category><![CDATA[changelog]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <dc:creator><![CDATA[Carolyn Chong]]></dc:creator>
            <pubDate>Tue, 24 Oct 2017 18:41:01 GMT</pubDate>
            <atom:updated>2018-06-05T18:33:34.597Z</atom:updated>
            <content:encoded><![CDATA[<h4>Here’s what’s new:</h4><ul><li>Obie is better and smarter at returning more relevant Page results. TL;DR: Better.</li><li>If you had a large Google Drive, Obie was very slow at returning results. We cut the time down to 10% of what it originally was. No one should ever be penalized for storing too much knowledge.</li><li>Performance improvements and a coating of grease mean results from all the other integrations slip through the sky and into Slack far faster.</li><li>We spruced up the design of Flows with new buttons, formatting and the ability to snooze a step. They’re lovelier now than we ever dreamed possible.</li><li>The Page editor has been updated so it’s even nicer than before. It sorta kinda closely resembles the Medium.com editor, which we like a lot a lot. It’s got everything you need and more: embed media, insert cloud docs, highlight knowledge cards, align text. Absolutely delightful.</li><li>Each Flow assignment notification now comes with a button that says “Start Flow”. This way you can be assigned multiple Flows and not get confused, and you can start a Flow whenever you please. As it should be.</li></ul><h4>Here’s what we fixed:</h4><ul><li>Sometimes, Obie was just not there for you. Maybe you’d ask him a question and he wouldn’t respond, or maybe you’d click a button to submit an answer and he just wouldn’t take the answer. Commonly, Obie was seen as offline. It wasn’t Obie being neglectful. It was software being a bit of a piffle. All better now.</li><li>You can now exercise your right to create and edit a Flow and know for certain that no steps will disappear or magically re-arrange themselves on their own.</li><li>The Unanswered Question metric in Insights now measures pretty much what you’d expect. That is, a question that had no results returned. Previously, an unanswered question was a question that had no saved response, but that’s certainly not always the case (like maybe (quite likely) an integration returned a result), so we fixed it.</li><li>New users attempting to use Obie would sometimes get stuck in an onboarding loop, which is not the warm welcome we would wish for those people. Sorry, new users.</li><li>Scheduling a Flow should, cross fingers, deliver the steps at the scheduled time.</li><li>When upvoting or downvoting a result, Obie did not always reliably register your vote, somehow mistaking “voting” for “ignoring”.</li><li>Searching for default content once worked, and now works once more.</li><li>For teams who use Slack User Groups, well those groups sometimes weren’t syncing properly with the dashboard. Which meant default assigning and un-assigning of content based on User Group failed silently. No more.</li><li>One last little big thing: If you ever said “hi” or “hello” to Obie, he wouldn’t have understood…how rude! He’s friendlier now and will say “hi” back!</li></ul><p><em>That’s all she wrote, folks. Obie 4.0[BETA] is live in the </em><a href="http://bit.ly/slackobie"><em>Slack App Directory</em></a><em>. </em><a href="http://bit.ly/tawktosupport"><em>Send us a note</em></a><em> or </em><a href="http://bit.ly/obietwitter"><em>tweet</em></a><em> to let us know what you think. We love bugs, so send those our way, too.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea0dc7b385a2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/tasytt-inc/obie-4-0-beta-changelog-ea0dc7b385a2">Obie 0.8 [BETA] Changelog</a> was originally published in <a href="https://medium.com/tasytt-inc">Obie.ai</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>