<?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 Andrei Kamarouski on Medium]]></title>
        <description><![CDATA[Stories by Andrei Kamarouski on Medium]]></description>
        <link>https://medium.com/@kamarouski?source=rss-91b1b83ccecb------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*DIwtY-jQDNYrUezOZgRYEQ.png</url>
            <title>Stories by Andrei Kamarouski on Medium</title>
            <link>https://medium.com/@kamarouski?source=rss-91b1b83ccecb------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 02:45:46 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kamarouski/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[ How Pythia helps multilingual CS teams in Zendesk]]></title>
            <link>https://medium.com/pythia-ai/how-pythia-helps-multilingual-cs-teams-in-zendesk-6083b65762e0?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/6083b65762e0</guid>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[multilingual]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Tue, 02 Mar 2021 07:18:19 GMT</pubDate>
            <atom:updated>2021-03-02T07:22:09.185Z</atom:updated>
            <content:encoded><![CDATA[<p>How do you and your agents feel working with multiple languages in Zendesk tickets and chats? We know there are some very common challenges here like language detection or change.</p><p>Meeting these needs we&#39;ve added a bunch of new cool features to Pythia apps and made the life of multilingual CS teams much easier!</p><ul><li>Pythia detects the <strong>actual language of the request</strong> instead of relying on some often incorrect technical information;</li><li>Your agents can <strong>change the language</strong> of macros/shortcuts in one click to apply the answers in relevant language;</li><li>Your agents can <strong>preview English versions</strong> of your macros/shortcuts in one click if needed and reply in a non-native language easily avoiding using Google Translate.</li></ul><p>See the live explanation from our CEO. Find your challenges and our cool solutions!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Ftp5YbqYkSoo%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dtp5YbqYkSoo&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Ftp5YbqYkSoo%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6be841684f8a8aa85ad5545fe8a7fa68/href">https://medium.com/media/6be841684f8a8aa85ad5545fe8a7fa68/href</a></iframe><p>Try Pythia apps for <a href="https://www.zendesk.com/apps/support/advanced-macros-by-pythia/">Zendesk Support</a> or <a href="https://www.zendesk.com/apps/chat/advanced-shortcuts-by-pythia/">Chat</a> for free.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6083b65762e0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pythia-ai/how-pythia-helps-multilingual-cs-teams-in-zendesk-6083b65762e0">🇺🇸🇩🇪🇪🇸 How Pythia helps multilingual CS teams in Zendesk</a> was originally published in <a href="https://medium.com/pythia-ai">Pythia AI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Predefined answers in your Help Center webform (Zendesk Tip)]]></title>
            <link>https://medium.com/pythia-ai/predefined-answers-in-your-help-center-webform-zendesk-tip-5c55843594f2?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/5c55843594f2</guid>
            <category><![CDATA[self-service]]></category>
            <category><![CDATA[deflection]]></category>
            <category><![CDATA[zendesk-tip]]></category>
            <category><![CDATA[zendesk]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Sat, 20 Feb 2021 07:09:51 GMT</pubDate>
            <atom:updated>2021-02-20T07:09:51.643Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/0*S0D76JYefX6nIzVi.png" /></figure><p>Today we would like to share a very nice tip that expands the standard self-service options of your Help Center running on Zendesk (BTW you can find more <a href="https://support.zendesk.com/hc/en-us/community/posts/203458536-Guide-community-tips-for-Help-Center">Help Center related tips in Zendesk Community</a>). The solution is based on simple JavaScript code and HTML template that might be added and extended even by non-developers.</p><h3>Expanding default self-service options in Zendesk Help Center</h3><p>These options include <a href="https://support.zendesk.com/hc/en-us/articles/360039548713-Using-different-search-methods-in-the-Help-Center#topic_vqf_4br_vjb">Knowledge base articles suggestions</a> when visitors type text in the Subject line and Answer Bot suggestions after the visitor submits a ticket. While the last option is a final attempt to deflect tickets (already submitted!), the first one works at the very beginning of the ticket submission process. It is clear that any additional meaningful and well-organized options for ticket deflection at the very beginning of this process could provide a good experience with your customer service.</p><p>Many brands do use and require filling out the custom ticket field with request categories when submitting a ticket. This is a great way to organize the related workflows in your Zendesk (see here how you can benefit from <a href="https://blog.pythia.cc/posts/how-to-organize-an-excellent-tickets-categorization-in-zendesk-fa460a7afd">excellent ticket categorization</a>). You can place this field at the very beginning of the webform to structure the whole submission process around this and ensure the best results in terms of the most relevant category selection.</p><h3>How Lyft does it</h3><p>So why not provide predefined suggestions below this field when visitors choose a specific value there? You can see how Lyft does it in their custom and interactive <a href="https://help.lyft.com/hc/en-us/requests/new?ticket_form_id=724707&amp;language=en-us&amp;isSubmittingTicket=true&amp;selectedOptions=%5B0%2C0%2C0%5D">webform here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5H3raH5ROXMUu3EV.png" /></figure><p>They use conditional ticket fields logic to guide visitors through multi-level categorization scenarios to end up with tailored predefined answers for each one of them. Additionally, they pre-fill the Subject field with the value of the last category, thus saving the efforts of the visitor and controlling the related workflows in Zendesk. Well done guys!</p><h3>How you do this in your Help Center</h3><p>Lyft’s example requires advanced web form customization to get conditional button like fields and selection experience. This customization is out of the scope of our today’s tip: our main goal is to provide a solution to show predefined answers for the case of one custom drop-down ticket field with categories.</p><p><strong>Step 1. Create custom categories field</strong></p><p>Again follow our best practices for one ticket form case outlined in the <a href="https://support.zendesk.com/hc/en-us/community/posts/360047415073-How-to-organize-an-excellent-tickets-categorization-in-Zendesk">post about excellent ticket categorization</a>. Then export all values and their tags via the “Download CSV” feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vEhpxzNht1ucFpEe.png" /></figure><p><strong>Step 2. Prepare predefined answers</strong></p><p>Import your CSV into Excel or Google Sheet so you can see the ticket field values and related tags (tags are used to show answers when values are selected in the field). Then add prepared predefined answers to those of them that you would like to show in the web form. You can use this <a href="https://docs.google.com/spreadsheets/d/1UBJrxnAqpzMXtPCChvHUIFxDeAV-dd5x8boWeApO0uI/edit?usp=sharing">Google Sheet template</a> or download the attached Excel file.</p><p><strong>Step 3. Add code to Help Center</strong></p><p>Go to Help Center theme pages (see <a href="https://support.zendesk.com/hc/en-us/articles/203664326-Customizing-your-help-center-theme">how to do this</a>) and open the New request page there. Place JavaScript and HTML code as following at the end of the page. Replace <strong>YOUR_TICKET_FIELD_ID</strong> with the ID of the custom ticket field and <strong>FIELD_VALUE_TAG_1</strong> with your tag. You can add any HTML text formattings (like headings, bold, links, images, etc).</p><pre>&lt;div style=&quot;display: none; margin-top: 10px&quot; data-element=&quot;field-helper&quot; data-field-id=&quot;YOUR_TICKET_FIELD_ID&quot;&gt;<br>  &lt;div data-field-tag=&quot;FIELD_VALUE_TAG_1&quot;&gt;<br>    &lt;h2&gt;Subtitle&lt;/h2&gt; and &lt;a href=&quot;https://google.com&quot;&gt;google link&lt;/a&gt;<br>  &lt;/div&gt;<br>&lt;/div&gt;</pre><pre>&lt;script&gt;<br>  try {<br>    const fieldHelperElement = document.querySelector(&#39;[data-element=&quot;field-helper&quot;]&#39;);<br>    const fieldId = fieldHelperElement.dataset.fieldId;<br>    const fieldInput = document.querySelector(`#request_custom_fields_${fieldId}`);<br>    const fieldInputContainer = fieldInput.parentElement;<br>    fieldInputContainer.after(fieldHelperElement);<br>    const fieldHelperOptions = [...fieldHelperElement.querySelectorAll(&#39;[data-field-tag]&#39;)];<br>    fieldHelperOptions.forEach(option =&gt; {<br>      option.style = &#39;display: none&#39;;<br>    });<br>    fieldHelperElement.style.display = &#39;block&#39;;</pre><pre>    fieldInput.addEventListener(&#39;change&#39;, event =&gt; {<br>      const selectedFieldTag = event.currentTarget.value;</pre><pre>      fieldHelperOptions.forEach(option =&gt; {<br>        option.style.display = option.dataset.fieldTag === selectedFieldTag ? &#39;block&#39; : &#39;none&#39;;<br>      });<br>    });<br>  } catch (err) {<br>    console.warn(&#39;Support form custom script error&#39;, err);<br>  }<br>&lt;/script&gt;</pre><p>Duplicate as many new code sections as you wish in the HTML code to add new answers.</p><pre>&lt;div data-field-tag=&quot;FIELD_VALUE_TAG_1&quot;&gt;<br>    Your text<br>  &lt;/div&gt;</pre><p>This is how it might look like as a result.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Fr1lWB19CgZ9G0_q.png" /></figure><p>That’s it! Now you have predefined answers and provide an additional streamlined self-service option to your Help Center visitors and customers.</p><p>I hope you have enjoyed this post. Share your additional ideas or best practices you have seen across Help Centers to improve this tip.</p><p>Happy support and stay safe!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5c55843594f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pythia-ai/predefined-answers-in-your-help-center-webform-zendesk-tip-5c55843594f2">Predefined answers in your Help Center webform (Zendesk Tip)</a> was originally published in <a href="https://medium.com/pythia-ai">Pythia AI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to organize an excellent tickets categorization in Zendesk]]></title>
            <link>https://medium.com/pythia-ai/how-to-organize-an-excellent-tickets-categorization-in-zendesk-36c3985ec579?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/36c3985ec579</guid>
            <category><![CDATA[customer-journey]]></category>
            <category><![CDATA[categorization]]></category>
            <category><![CDATA[zendesk-tip]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 15:06:59 GMT</pubDate>
            <atom:updated>2020-07-09T15:08:17.370Z</atom:updated>
            <content:encoded><![CDATA[<p><em>This story was initially published in </em><a href="https://medium.com/startup-central"><em>Startup Central</em></a><em> Medium Blog by Zendesk Startups.</em></p><p>Hi! 👋</p><p>More than one year ago I have posted my main contribution to Zendesk Community — the post about <a href="https://support.zendesk.com/hc/en-us/community/posts/360028933614-Using-Customer-Journey-idea-to-set-up-or-scale-your-Zendesk">Using Customer Journey idea to set up or scale your Zendesk</a>. Since that time I had implemented and optimized Zendesk many times. And in most cases, this approach has served as a great tool to make Zendesk efficient and manageable.</p><h3>How do you benefit from tickets categorization</h3><p>Today I would like to tell you more about the practical side of CJ idea implementation. And the starting point should be one of the main areas where CJ idea is applied in Zendesk — <strong>tickets categorization</strong>.</p><p>Why is it so important? Mostly because you can build out the whole Zendesk workflows on top of this one. Once you know what is your ticket about you can make many actions on it!</p><p>Namely, on top of the tickets categorization system you can:</p><ul><li><strong>Triage tickets</strong> into different ticket views</li><li><strong>Route tickets</strong> to different groups and/or agents</li><li><strong>Assign priority</strong> levels to tickets (Urgent, High, Normal or Low)</li><li><strong>Assign SLA</strong> policies to tickets</li><li><strong>Change status</strong> of the ticket</li></ul><p>This all makes a significant part of the everyday agents’ work. At the end of the post, I will tell you how you can automate this job of the tickets categorization (assigning categories to tickets) and win a lot of time for improving your customer service.</p><h3>How to create a good categorization system</h3><p>As one would expect you can create a good categorization system using Customer Journey idea. The general advantage of the СJ idea is that it mimics the real-world customer experience and by default is transparent for both customers and employees (it means it is easy to learn!).</p><p>Applied to tickets categorization this means that your system should be:</p><ul><li><strong>Customer-centric in its vision.</strong> All categories and namings should be from the customer’s, not the company’s perspective (i.e. the company sends a refund, but the customer receives the refund). It allows you to deploy this categorization in your Help Center for the tickets submission as it is.</li><li><strong>Comprehensive in its coverage. </strong>Your categories should cover (more or less) all possible and important categories. The most secure and reliable way to get this result is just to follow step-by-step the real journeys (actions) on different СJ stages.</li><li><strong>Compact in its namings.</strong> I prefer to use compact namings (2–3 words) for categories and follow the pattern of “Verb + Noun” (i.e. Request refund, Approving refund, Receive refund). It looks good on all devices (especially mobile ones).</li><li><strong>Neutral in its terms</strong>. The categories should not be negative or positive but neutral. This allows you to apply them in any case — would it be a simple question or real problem. You can use the <strong>Ticket Type</strong> field to define the mode of the requester sentiment or create a custom ticket field for this reason.</li></ul><p>Those principles might have some exceptions: like you can use simple nouns for a very general category without specifying any action via the verb there (Company &gt; Newsletter / Partners / Stores etc). But it is always good to follow those principles consistently to avoid a chaotic categorization system in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ng19qV3lGa7M1YbO.png" /></figure><p>Let me explain those principles using an example of the <strong>delivery</strong> related tickets categorization from the <strong>Ecommerce</strong> domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QinluavMxoVFnQ1d.png" /></figure><p>As you can see some journey steps are optional, but they should be part of the complete Delivery journey. One ticket might be a simple <strong>question</strong> about the possible exceptions (due to COVID-19) and another one a <strong>complaint</strong> about delayed delivery (due to the same COVID-19). You mark both as Delivery &gt; Starting delivery, and use <strong>Ticket Type = Question</strong> for the first case and <strong>Ticket Type = Problem</strong> for the second one.</p><h3>How to implement categorization system in Zendesk</h3><p>The answer here depends on what Zendesk plan and features (add-ons) you have, namely if you have Multiple ticket forms available (part of the <a href="https://support.zendesk.com/hc/en-us/articles/360021065653-What-does-the-Productivity-Pack-add-on-include-">Productivity Pack add-on</a>).</p><ul><li><strong>You have Multiple forms</strong> &gt; Use ticket forms and custom ticket fields to create separate forms per category (Journey stage).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7OTeUKGtspqZ4dFS.gif" /></figure><ul><li><strong>You DON’T have Multiple forms</strong> &gt; Use only custom ticket fields to create one field with categories using <strong>drop-down</strong> or <strong>multi-select</strong> field type to allow one or multiple categories per ticket.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*q1gd8LZ7qR-yovRb.gif" /></figure><p>Technically using any of those two options, you have the same results in terms of categorization. Multiple forms provide more control over the ticket submission process and more flexible reporting.</p><h3>How to automate the categorization process in Zendesk</h3><p>There are several ways to achieve the categories being automatically filled in when tickets are created in Zendesk.</p><ul><li><strong>Via web form(s) / Web widget.</strong><br>You can add the categorization related field(s) to the Ticket form(s) and Web widget (additionally making them required upon ticket submission). Customers will do the job of categorization for you. This might work pretty well once your categorization system is customer-centric and transparent, and your customers engaged and ‘responsible’. This approach is limited since many companies use Email as the main support channel and customers are not always ‘correct’ with topics selection.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JlwVKl5hR0nFeWO5.png" /></figure><ul><li><strong>Via Zendesk triggers</strong>.<br>With Zendesk triggers you can create different rules to check ticket’s <a href="https://support.zendesk.com/hc/en-us/articles/226009928-How-do-I-create-a-trigger-based-on-a-ticket-subject-">Subject text</a> and/or Comment text for having some keywords or strings. This method is limited because of language complexity: customers might write about the same categories in a very different way and mentioning many keywords at the same time. But for typical request cases, it works pretty well too. More details about triggers <a href="https://support.zendesk.com/hc/en-us/articles/203662106-Streamlining-workflow-with-ticket-updates-and-triggers">here</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*CL0bO--c2m-HETcx.png" /></figure><ul><li><strong>Via AI services</strong>.<br>Last but not least method is to use modern AI-based tools and/or services. Unlike in the previous method, they are not limited to the simple keywords based understanding of the text but use the whole tickets description to define the main or multiple categories. In Zendesk Marketplace you can find different apps for this case like <a href="https://www.zendesk.com/apps/support/monkeylearn-ticket-tagging">MonkeyLearn</a>. We at Pythia developed Tickets Classifier which provides automatic tickets categorization for the Ecommerce domain with 12 general categories and 56 advanced subcategories. You can test it live with your own requests <a href="https://pythia.cc/products/classify">here</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*izP2BdAVUrMMmiur.png" /></figure><p>I hope you have enjoyed this post. Let me know with your upvotes and feedback comments.</p><p>Stay safe and happy support!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36c3985ec579" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pythia-ai/how-to-organize-an-excellent-tickets-categorization-in-zendesk-36c3985ec579">How to organize an excellent tickets categorization in Zendesk</a> was originally published in <a href="https://medium.com/pythia-ai">Pythia AI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to organize an excellent tickets categorization in Zendesk]]></title>
            <link>https://medium.com/startup-central/how-to-organize-an-excellent-tickets-categorization-in-zendesk-11e64d99efc3?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/11e64d99efc3</guid>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[cx]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[ticketing-system]]></category>
            <category><![CDATA[customer-service]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Tue, 30 Jun 2020 17:53:06 GMT</pubDate>
            <atom:updated>2020-06-30T17:53:06.239Z</atom:updated>
            <content:encoded><![CDATA[<p>Hi! 👋</p><p>More than one year ago I have posted my main contribution to Zendesk Community — the post about <a href="https://support.zendesk.com/hc/en-us/community/posts/360028933614-Using-Customer-Journey-idea-to-set-up-or-scale-your-Zendesk">Using Customer Journey idea to set up or scale your Zendesk</a>. Since that time I had implemented and optimized Zendesk many times. And in most cases, this approach has served as a great tool to make Zendesk efficient and manageable.</p><h3>How do you benefit from tickets categorization</h3><p>Today I would like to tell you more about the practical side of CJ idea implementation. And the starting point should be one of the main areas where CJ idea is applied in Zendesk — <strong>tickets categorization</strong>.</p><p>Why is it so important? Mostly because you can build out the whole Zendesk workflows on top of this one. Once you know what is your ticket about you can make many actions on it!</p><p>Namely, on top of the tickets categorization system you can:</p><ul><li><strong>Triage tickets</strong> into different ticket views</li><li><strong>Route tickets</strong> to different groups and/or agents</li><li><strong>Assign priority</strong> levels to tickets (Urgent, High, Normal or Low)</li><li><strong>Assign SLA</strong> policies to tickets</li><li><strong>Change status</strong> of the ticket</li></ul><p>This all makes a significant part of the everyday agents’ work. At the end of the post, I will tell you how you can automate this job of the tickets categorization (assigning categories to tickets) and win a lot of time for improving your customer service.</p><h3>How to create a good categorization system</h3><p>As one would expect you can create a good categorization system using Customer Journey idea. The general advantage of the СJ idea is that it mimics the real-world customer experience and by default is transparent for both customers and employees (it means it is easy to learn!).</p><p>Applied to tickets categorization this means that your system should be:</p><ul><li><strong>Customer-centric in its vision.</strong> All categories and namings should be from the customer’s, not the company’s perspective (i.e. the company sends a refund, but the customer receives the refund). It allows you to deploy this categorization in your Help Center for the tickets submission as it is.</li><li><strong>Comprehensive in its coverage. </strong>Your categories should cover (more or less) all possible and important categories. The most secure and reliable way to get this result is just to follow step-by-step the real journeys (actions) on different СJ stages.</li><li><strong>Compact in its namings.</strong> I prefer to use compact namings (2–3 words) for categories and follow the pattern of “Verb + Noun” (i.e. Request refund, Approving refund, Receive refund). It looks good on all devices (especially mobile ones).</li><li><strong>Neutral in its terms</strong>. The categories should not be negative or positive but neutral. This allows you to apply them in any case — would it be a simple question or real problem. You can use the <strong>Ticket Type</strong> field to define the mode of the requester sentiment or create a custom ticket field for this reason.</li></ul><p>Those principles might have some exceptions: like you can use simple nouns for a very general category without specifying any action via the verb there (Company &gt; Newsletter / Partners / Stores etc). But it is always good to follow those principles consistently to avoid a chaotic categorization system in the future.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JaRXPWHciNg-2blM.png" /></figure><p>Let me explain those principles using an example of the <strong>delivery</strong> related tickets categorization from the <strong>Ecommerce</strong> domain.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VYf3avq-pEIK5MyC55GzTA.png" /></figure><p>As you can see some journey steps are optional, but they should be part of the complete Delivery journey. One ticket might be a simple <strong>question</strong> about the possible exceptions (due to COVID-19) and another one a <strong>complaint</strong> about delayed delivery (due to the same COVID-19). You mark both as Delivery &gt; Starting delivery, and use <strong>Ticket Type = Question</strong> for the first case and <strong>Ticket Type = Problem</strong> for the second one.</p><h3>How to implement categorization system in Zendesk</h3><p>The answer here depends on what Zendesk plan and features (add-ons) you have, namely if you have Multiple ticket forms available (part of the <a href="https://support.zendesk.com/hc/en-us/articles/360021065653-What-does-the-Productivity-Pack-add-on-include-">Productivity Pack add-on</a>).</p><ul><li><strong>You have Multiple forms</strong> &gt; Use ticket forms and custom ticket fields to create separate forms per category (Journey stage).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5wRgTqTtW49i6ndM.gif" /></figure><ul><li><strong>You DON’T have Multiple forms</strong> &gt; Use only custom ticket fields to create one field with categories using <strong>drop-down</strong> or <strong>multi-select</strong> field type to allow one or multiple categories per ticket.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ztcWDsR9TlwYFCht.gif" /></figure><p>Technically using any of those two options, you have the same results in terms of categorization. Multiple forms provide more control over the ticket submission process and more flexible reporting.</p><h3>How to automate the categorization process in Zendesk</h3><p>There are several ways to achieve the categories being automatically filled in when tickets are created in Zendesk.</p><ul><li><strong>Via web form(s) / Web widget.</strong><br>You can add the categorization related field(s) to the Ticket form(s) and Web widget (additionally making them required upon ticket submission). Customers will do the job of categorization for you. This might work pretty well once your categorization system is customer-centric and transparent, and your customers engaged and ‘responsible’. This approach is limited since many companies use Email as the main support channel and customers are not always ‘correct’ with topics selection.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HRGGIBo5ZHEdwowm.png" /></figure><ul><li><strong>Via Zendesk triggers</strong>. <br>With Zendesk triggers you can create different rules to check ticket’s <a href="https://support.zendesk.com/hc/en-us/articles/226009928-How-do-I-create-a-trigger-based-on-a-ticket-subject-">Subject text</a> and/or Comment text for having some keywords or strings. This method is limited because of language complexity: customers might write about the same categories in a very different way and mentioning many keywords at the same time. But for typical request cases, it works pretty well too. More details about triggers <a href="https://support.zendesk.com/hc/en-us/articles/203662106-Streamlining-workflow-with-ticket-updates-and-triggers">here</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_zUOxp_s-wIsUic4.png" /></figure><ul><li><strong>Via AI services</strong>.<br>Last but not least method is to use modern AI-based tools and/or services. Unlike in the previous method, they are not limited to the simple keywords based understanding of the text but use the whole tickets description to define the main or multiple categories. In Zendesk Marketplace you can find different apps for this case like <a href="https://www.zendesk.com/apps/support/monkeylearn-ticket-tagging">MonkeyLearn</a>. We at Pythia developed Tickets Classifier which provides automatic tickets categorization for the Ecommerce domain with 12 general categories and 56 advanced subcategories. You can test it live with your own requests <a href="https://pythia.cc/products/classify">here</a>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wPWKubQwNkqT1eb-.png" /></figure><p>I hope you have enjoyed this post. Let me know with your upvotes and feedback comments.</p><p>Stay safe and happy support!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=11e64d99efc3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-central/how-to-organize-an-excellent-tickets-categorization-in-zendesk-11e64d99efc3">How to organize an excellent tickets categorization in Zendesk</a> was originally published in <a href="https://medium.com/startup-central">Startup Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ How to set up an “ideal” KPI system for your customer support]]></title>
            <link>https://medium.com/startup-central/how-to-set-up-an-ideal-kpi-system-for-your-customer-support-93b1fb9bafde?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/93b1fb9bafde</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[customer-support]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[kpi]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Mon, 01 Jun 2020 17:43:39 GMT</pubDate>
            <atom:updated>2020-06-01T17:43:39.536Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*CW9uOKteLq3P2uiC3hjzcg.png" /></figure><p>Today I would like to share my vision of the ideal KPI system for your customer support. I was inspired to write this post by one question in the amazing <a href="https://supportdriven.com/">Support Driven community</a> (I suggest everyone join it if you have not yet). I have been doing CS and Zendesk consulting for the last 8 years and can share experience proven with a lot of projects and companies.</p><p>Yeah, you should now think that it might sound too pretentious to pretend for something ideal in our modern world. But let me explain why I think the proposed KPI system can be titled as an ideal one. Once I set the criteria of being ideal I can name the thing ideal, can’t I? :)</p><h3>What makes the ideal KPI system</h3><p>Any customer support manager is challenged to manage the customer support team and systems efficiently and with less internal frictions. The KPI system is a managerial tool to govern and monitor the process in an organized way.</p><p>So what makes the ideal KPI system? I would name the next 3 criteria:</p><ul><li>It is <strong>balanced</strong>. The ideal KPI system should have not too many but enough indicators which are related and dependent on each other — like any good system of checks and balances.</li><li>It is <strong>transparent</strong>. It should be crystal clear for whom it serves — for support agents as well as for support managers.</li><li>It is <strong>scalable</strong>. Finally, the ideal KPI system should work even when your team is growing, splitting, and gets more complex in terms of workflows.</li></ul><p>The ideal KPI system allows you to track agent performance and compare between agents when they are segmented into different groups with each group working on different types of tickets with varying processes, the time required and complexity. The balance is also really important to avoid individual cherry-picking or collective scores gaming.</p><h3>KPI metrics types</h3><p>Like any activity in the world, the customer support routine can be described with 3 attributes: <strong>how</strong> <strong>much</strong> you do, <strong>how</strong> <strong>fast</strong> you are, and <strong>how good</strong> you are at. As a result, it leads us to the ideal KPI system which should include 3 kinds (groups) of metrics:</p><ol><li><strong>Capacity</strong> metrics</li><li><strong>Velocity</strong> metrics</li><li><strong>Quality</strong> metrics</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*6uaAOiPpF6XVU46Fq7acjA.png" /></figure><p>Those metrics (outlined in the next chapter) are <strong>balanced</strong>: usually, you can not serve too many requests or to be too slow (= doing just a few requests with brilliant quality) without having a negative impact on the overall quality. They are <strong>transparent</strong> since you are measuring well-known real-world attributes transposed into the customer support realities and related to the clear actions and outcomes. And <strong>scalable</strong> to any department/group level specifics since they are not too specific at the same time (to stay balanced and transparent!).</p><h3>KPI metrics list</h3><p>Now let’s name those metrics! I usually suggest using them to have the ideal KPI system. They are relevant for tickets but with some adoption, you can have the same equivalents for chats, calls, etc.</p><p><strong>Capacity metrics</strong></p><ol><li>Solved tickets or Public replies (individually solved or assists)</li><li>Productivity (Tickets or Replies / Total Time spent)</li><li>Macros usage rate / KB linkage rate</li></ol><p><strong>Velocity metrics</strong></p><ol><li>First Reply Time</li><li>Next Reply Time</li><li>Full Resolution Time</li></ol><p><strong>Quality metrics</strong></p><ol><li>CSAT (Customer Satisfaction score)</li><li>NPS (Net Promoter Score®, or NPS®)</li><li>(Optional) CES (Customer Efforts Score)</li></ol><p>One notion for the metric <strong>Macros usage rate / KB linkage rate</strong>. I think this one is very important to have because it is directly related to how your agents are utilizing your internal knowledge. I usually observe the best rates in all the capacity, velocity, and quality in those companies who actively use macros / KB articles. This is natural because macros are one of the main productivity tools in any support system (and you can define this easily with our <a href="https://pythia.cc/products/report">Macros Reporting</a> for Zendesk).</p><h3>Calculating and weighing the scores</h3><p>Until some point, you are OK with having and comparing absolute numbers for KPI metrics. But once you have many agents and multiple teams you will probably need to understand the individual agent’s performance.</p><p>This is possible by going <strong>3 steps</strong> like:</p><ol><li><strong>Calculating</strong> individual scores against the group’s average,</li><li><strong>Assigning</strong> some standard ‘points’ based on it, and</li><li><strong>Aggregating</strong> them with some weights to a global KPI score.</li></ol><p>I will write a separate post with examples for these calculations in the near future. I hope you have enjoyed this post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93b1fb9bafde" width="1" height="1" alt=""><hr><p><a href="https://medium.com/startup-central/how-to-set-up-an-ideal-kpi-system-for-your-customer-support-93b1fb9bafde">📈 How to set up an “ideal” KPI system for your customer support</a> was originally published in <a href="https://medium.com/startup-central">Startup Central</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to set up an ideal KPI system for your customer support]]></title>
            <link>https://medium.com/pythia-ai/how-to-set-up-an-ideal-kpi-system-for-your-customer-support-ae19cb02400?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/ae19cb02400</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[kpi]]></category>
            <category><![CDATA[zendesk-tip]]></category>
            <category><![CDATA[zendesk]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Fri, 08 May 2020 06:31:04 GMT</pubDate>
            <atom:updated>2020-05-08T06:31:04.213Z</atom:updated>
            <content:encoded><![CDATA[<h3>📈 How to set up an ideal KPI system for your customer support</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*CW9uOKteLq3P2uiC3hjzcg.png" /></figure><p>Today I would like to share my vision of the ideal KPI system for your customer support. I was inspired to write this post by one question in the amazing <a href="https://supportdriven.com/">Support Driven community</a> (I suggest everyone join it if you have not yet). I have been doing CS and Zendesk consulting for the last 8 years and can share experience proven with a lot of projects and companies.</p><p>Yeah, you should now think that it might sound too pretentious to pretend for something ideal in our modern world. But let me explain why I think the proposed KPI system can be titled as an ideal one. Once I set the criteria of being ideal I can name the thing ideal, can’t I? :)</p><h3>What makes the ideal KPI system</h3><p>Any customer support manager is challenged to manage the customer support team and systems efficiently and with less internal frictions. The KPI system is a managerial tool to govern and monitor the process in an organized way.</p><p>So what makes the ideal KPI system? I would name the next 3 criteria:</p><ul><li>It is <strong>balanced</strong>. The ideal KPI system should have not too many but enough indicators which are related and dependent on each other — like any good system of checks and balances.</li><li>It is <strong>transparent</strong>. It should be crystal clear for whom it serves — for support agents as well as for support managers.</li><li>It is <strong>scalable</strong>. Finally, the ideal KPI system should work even when your team is growing, splitting, and gets more complex in terms of workflows.</li></ul><p>The ideal KPI system allows you to track agent performance and compare between agents when they are segmented into different groups with each group working on different types of tickets with varying processes, the time required and complexity. The balance is also really important to avoid individual cherry-picking or collective scores gaming.</p><h3>KPI metrics types</h3><p>Like any activity in the world, the customer support routine can be described with 3 attributes: <strong>how</strong> <strong>much</strong> you do, <strong>how</strong> <strong>fast</strong> you are, and <strong>how good</strong> you are at. As a result, it leads us to the ideal KPI system which should include 3 kinds (groups) of metrics:</p><ol><li><strong>Capacity</strong> metrics</li><li><strong>Velocity</strong> metrics</li><li><strong>Quality</strong> metrics</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*6uaAOiPpF6XVU46Fq7acjA.png" /></figure><p>Those metrics (outlined in the next chapter) are <strong>balanced</strong>: usually, you can not serve too many requests or to be too slow (= doing just a few requests with brilliant quality) without having a negative impact on the overall quality. They are <strong>transparent</strong> since you are measuring well-known real-world attributes transposed into the customer support realities and related to the clear actions and outcomes. And <strong>scalable</strong> to any department/group level specifics since they are not too specific at the same time (to stay balanced and transparent!).</p><h3>KPI metrics list</h3><p>Now let’s name those metrics! I usually suggest using them to have the ideal KPI system. They are relevant for tickets but with some adoption, you can have the same equivalents for chats, calls, etc.</p><p><strong>Capacity metrics</strong></p><ol><li>Solved tickets or Public replies (individually solved or assists)</li><li>Productivity (Tickets or Replies / Total Time spent)</li><li>Macros usage rate / KB linkage rate</li></ol><p><strong>Velocity metrics</strong></p><ol><li>First Reply Time</li><li>Next Reply Time</li><li>Full Resolution Time</li></ol><p><strong>Quality metrics</strong></p><ol><li>CSAT (Customer Satisfaction score)</li><li>NPS (Net Promoter Score®, or NPS®)</li><li>(Optional) CES (Customer Efforts Score)</li></ol><p>One notion for the metric <strong>Macros usage rate / KB linkage rate</strong>. I think this one is very important to have because it is directly related to how your agents are utilizing your internal knowledge. I usually observe the best rates in all the capacity, velocity, and quality in those companies who actively use macros / KB articles. This is natural because macros are one of the main productivity tools in any support system (and you can define this easily with our <a href="https://pythia.cc/products/report">Macros Reporting</a> for Zendesk).</p><h3>Calculating and weighing the scores</h3><p>Until some point, you are OK with having and comparing absolute numbers for KPI metrics. But once you have many agents and multiple teams you will probably need to understand the individual agent&#39;s performance.</p><p>This is possible by going <strong>3 steps</strong> like:</p><ol><li><strong>Calculating</strong> individual scores against the group’s average,</li><li><strong>Assigning</strong> some standard ‘points’ based on it, and</li><li><strong>Aggregating</strong> them with some weights to a global KPI score.</li></ol><p>I will write a separate post with examples for these calculations in the near future. I hope you have enjoyed this post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ae19cb02400" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pythia-ai/how-to-set-up-an-ideal-kpi-system-for-your-customer-support-ae19cb02400">How to set up an ideal KPI system for your customer support</a> was originally published in <a href="https://medium.com/pythia-ai">Pythia 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 ultimate checklist to optimize your Zendesk]]></title>
            <link>https://medium.com/pythia-ai/the-ultimate-checklist-to-optimize-your-zendesk-9c821db24377?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/9c821db24377</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[zendesk-tip]]></category>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Mon, 30 Mar 2020 16:30:46 GMT</pubDate>
            <atom:updated>2021-10-22T15:44:58.615Z</atom:updated>
            <content:encoded><![CDATA[<h4>Or any other support system</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*A7rV6H_75mvlXhiNKm2G_A.jpeg" /></figure><p><strong>🔥🔥🔥 Good news</strong>!<br>Now you can easily optimize your Zendesk with an interactive web tool called <a href="https://pythia.cc/products/health">Zendesk Health Check</a>!</p><p>It includes all checks from this list as well as many other advanced checks for any Zendesk account.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/798/0*P2Xkkd0_uZNk3F9s.jpeg" /></figure><p><strong>Preface</strong></p><p>Today, mid-March 2020, when COVID-19 is on the rise and many companies are affected, we need to support each other even more than usual. We all are facing very special management and productivity challenges doing customer service these days. And I think that knowledge is the best weapon against those challenges.</p><p>That’s why I decided to share another piece of my professional knowledge with the community. Last time I posted about my approach to <a href="https://support.zendesk.com/hc/en-us/community/posts/360028933614-Using-Customer-Journey-idea-to-set-up-or-scale-your-Zendesk">set up or optimize Zendesk using Customer Journey idea</a>. I know this post might sound a bit too theoretical — so I would like to share more practical stuff today.</p><p>I have been doing professional Zendesk consulting for the last 9 years. One of my best-selling services is Zendesk Health Diagnostics. I have diagnosed many Zendesk accounts — from small one-agent accounts to big enterprise-scale ones — and collected a lot of cases. But all the time I was facing the same repetitive issues/optimizations.</p><p><strong>The Checklist</strong></p><p>The checklist is a great tool to organize any activities. I have organized all optimizations into groups based on the area of Zendesk and/or functional type of optimization. But technically you can follow them in any order you like.</p><p>For almost all points I have placed the links to Zendesk Help Center articles where you can find the details of the implementation. Sometimes you will find the screenshots with real examples of discussed setups which allows you to reproduce them easily in your Zendesk.</p><p><strong>BRANDING</strong></p><ol><li><strong>Add avatars in agent profiles</strong><br>Looking more human is better than a no-name Support Agent. You can use your real photos or create custom avatars using tools like <a href="https://chrome.google.com/webstore/detail/avatar-maker/ofknlbikfofijlcjkfcihomkedmchfbn?hl=en">this</a>. <a href="https://chrome.google.com/webstore/detail/avatar-maker/ofknlbikfofijlcjkfcihomkedmchfbn?hl=en">https://chrome.google.com/webstore/detail/avatar-maker/ofknlbikfofijlcjkfcihomkedmchfbn?hl=en</a></li><li><strong>Add signatures in agent profiles</strong><br>Signatures are useful for providing branded contact details, links, etc. They add a bit more personalization to your customer service. You can add <a href="https://support.zendesk.com/hc/en-us/articles/203691076-Adding-an-agent-signature-to-ticket-email-notifications#topic_uxd_slm_hj">individual and branded signatures</a> and design them very differently <a href="https://support.zendesk.com/hc/en-us/articles/203691016-Formatting-text-with-Markdown">using Markdown</a>. I always suggest keeping them short until you don’t need to have long ones for some specific reason.</li><li><strong>Add your brand name to Email template</strong><br>Default Email template in Zendesk has a footer placeholder like “This email is a service from YourZendeskName”. You can <a href="https://support.zendesk.com/hc/en-us/articles/115000945487-How-to-remove-Delivered-by-Zendesk-from-emails">remove</a> it or replace it with your own text like “This email is a service from BRAND X”.</li><li><strong>Change Help Center address to branded one</strong><br>Starting from the Zendesk Support Team plan you can <a href="https://support.zendesk.com/hc/en-us/articles/203664356-Changing-the-address-of-your-support-website-on-Zendesk-host-mapping-">set up a branded Help Center address</a> instead of BRAND.zendesk.com/hc. You can use more official support.BRAND.com or more friendly help.BRAND.com as a custom address. And you get a free SSL for this address!</li><li><strong>Add SPF and DNS records to verify your branded emails</strong><br>This may sound too technical but actually is very easy: just add several records in your domain management system (like GoDaddy). One SPF record (details <a href="https://support.zendesk.com/hc/en-us/articles/203683886-Allowing-Zendesk-to-send-email-on-behalf-of-your-email-domain#topic_w5x_3tp_l2b">here</a>), 4 CNAME records (details <a href="https://support.zendesk.com/hc/en-us/articles/203683886-Allowing-Zendesk-to-send-email-on-behalf-of-your-email-domain#topic_sx4_wqp_l2b">here</a>) and one TXT record (details <a href="https://support.zendesk.com/hc/en-us/articles/203683886-Allowing-Zendesk-to-send-email-on-behalf-of-your-email-domain#topic_ryh_djh_sfb">here</a>). You can do it yourself or ask your IT professional. It takes up to 5 minutes.</li></ol><p><strong>WORKFLOWS &amp; CHANNELS</strong></p><ol><li><strong>Use grouping and sorting in Views<br></strong>Views are a great tool to organize tickets in your Zendesk, especially when you group the tickets by some attribute and sort them inside this attribute. I usually suggest using Priority for grouping tickets and Next SLA Breach attribute to sort them. Look at this <a href="https://gyazo.com/4f55971d1c68810152326b9298d36e7c">Unassigned tickets view</a> and <a href="https://gyazo.com/d28924dc3124bbbda873bbcc5607fdfe">its settings</a> examples. This way you have a well-prioritized tickets queue reflecting different importance of tickets (= customers) for your business.</li><li><strong>Categorize tickets by topics</strong><br>Tickets categorization has a lot of benefits for automating different areas in Zendesk based on topics via triggers: (a) route tickets to groups/agents, (b) assign Priority, © assign SLAs, (d) get reporting for customer experience analytics. Organize your topics in forms or <a href="https://support.zendesk.com/hc/en-us/articles/203661876">multi-level dropdown fields</a> depending on your Zendesk plan. Download <a href="https://docs.google.com/spreadsheets/d/1bn3e4xcQKPfxGTEVmeqsGJXo_YJhOTWLanRCvB_Ny-o/edit?usp=sharing">this Excel file</a> with my ‘ultimate’ list of categories for E-commerce brands (and instructions about how to create a field).</li><li><strong>Use more Priority levels in tickets<br></strong>Zendesk allows you to have 2 or 4 levels of ticket priority (you can change them on ticket field settings in <em>Admin &gt; Tickets Fields &gt; Priority</em>). Having more levels allows you to reflect all gradients of tickets importance considering multiple conditions (like category, channel, tags, etc). Otherwise, you have too many just High priority tickets where some are really more urgent than others.</li><li><strong>Enable On hold status in tickets</strong><br>By default, this status is not enabled in Zendesk. But this status is very useful for many cases when a response is needed from a third party (not the requester or the assignee). You can set up special views to track those tickets and exclude them from other views (using condition Status IS NOT On Hold). Go to <em>Admin &gt; Tickets Fields &gt; Status </em>to enable the status.</li><li><strong>Set up SLAs to track KPIs and manage the queue</strong><br>Sometimes SLAs are not used even if this feature is available because they are considered as an enterprise-like story. In fact, you can use SLAs to have more internal control over tickets queues in terms of prioritization and reporting (remember Views setup in p. 1 above). I usually suggest adding at least 2 metrics — First Reply Time and Next Reply time in Calendar or Business hours. Look at <a href="https://gyazo.com/0cab43f63a4bf826bda1b73ef8e11e5d">this screenshot</a> for a real setup example.</li><li><strong>Add Web widget to Help Center / Website</strong><br>Web Widget is a great way to receive tickets because unlike emails you have much more control over the submission process and results. You can <a href="https://support.zendesk.com/hc/en-us/articles/115004884827">define mandatory custom ticket fields</a> to collect the required details for further workflows (see p. 2 above). Check other useful <a href="https://support.zendesk.com/hc/en-us/articles/115004744348-Web-Widget-resources">resources</a> for setting up and customizing Web Widget.</li><li><strong>Make Request theme field visible and editable for customers<br></strong>This point is one of the actions related to pp. 2 and 5 above. Since you have a clear and simple categorization system you can make it mandatory by ticket submission and get the correct categories in most cases upon ticket creation. It allows you to get all the benefits of tickets categorization from p. 2. Naturally, you benefit even more if your customers use this channel over others (like email or social media) where they don’t have to select a request category.</li><li><strong>Use macros in tickets and/or shortcuts in chats (more and more again)<br></strong>In my opinion, Macros is the main productivity tool in Zendesk. Macros allow agents to insert predefined responses into the comment box and apply multiple ticket fields values automatically. Sometimes companies avoid using macros to provide more personalized, non-templated customer support and service. For me this attitude is not completely correct: macros just help you to save time for manual typing and fields filling. What would be the final reply depends on your agents (who follow your guides and SOPs). Macros are just a tool; people decide to be humans or ‘robots’. Check what the normal macros usage rate is below (in the ‘KPIs &amp; Reporting’ section).</li><li><strong>Activate CSAT Surveys if possible</strong><br>If your Zendesk plan allows you (Professional and higher) to have CSAT Surveys, use them. They allow you to collect valuable customer feedback (ratings and comments) and track your agents’ performance in terms of the support quality. And don’t forget to activate collecting the bad scores reasons too. Look at <a href="https://gyazo.com/a9b2ccc11bd275baf89ed6c5f475e0ae">this screenshot</a> with typical settings. Below (in the ‘KPIs &amp; Reporting’ section) you will find the details about building a report for CSAT Comments in Explore.</li><li><strong>Activate ССs and Followers feature</strong><br>ССs and Followers is a pretty new feature (introduced in 2019) and is not actively used yet in old accounts I encounter. Actually, it is very beneficial to separate public and hidden recipients because Followers feature works like BCC in normal emails. In most cases, you use automatic migration which takes just a few minutes (see how <a href="https://support.zendesk.com/hc/en-us/articles/360002113728-Migrating-to-CCs-and-followers">here</a>).</li><li><strong>Activate Schedules to track KPIs within business hours<br></strong>Starting from Professional plan you can <a href="https://support.zendesk.com/hc/en-us/articles/203662206-Setting-your-schedule-with-business-hours-and-holidays-Professional-and-Enterprise-">set up schedules</a> in your Zendesk. Multiple schedules allow you to track groups’/agents’ performance reflecting the time zones where they are working (their group/individual schedules). This way you have a more detailed performance picture (within calendar and business hours).</li><li><strong>Activate ‘Auto-assign tickets upon solve’ setting<br></strong>This small setting allows you to automate ticket assignment in one click (you can build a more customized trigger for the same process). Go to <em>Admin &gt; Tickets &gt; Assignment</em> section and check the box (don’t forget to save the changes).</li><li><strong>Activate ‘Include attachments in emails’ setting</strong><br>This setting is located on the same page and allows you to include actual attachments in outbound emails instead of links that might be just missed by customers. Go to <em>Admin &gt; Tickets &gt; Attachments</em> section and check the box (don’t forget to save the changes).</li><li><strong>Activate Automatic Redaction in tickets</strong><br>As Zendesk states “Selecting this option enables automatic redaction of credit card numbers from all customer-submitted text in tickets to protect sensitive data.”. Go to <em>Admin &gt; Security</em> and check the box (don’t forget to save the changes).</li><li><strong>Activate ‘Include unpublished posts’ in Facebook page settings</strong><br>If you run Facebook ads campaigns you can get them as tickets in Zendesk too (with some limitations described <a href="https://support.zendesk.com/hc/en-us/articles/115000572788-Why-aren-t-comments-from-Facebook-being-added-to-tickets-">here</a>). Check the setup process <a href="https://support.zendesk.com/hc/en-us/articles/203661556#topic_ejk_hp3_zl">here</a>.</li><li><strong>Install apps for online shops, delivery systems, and other integrations</strong><br>Zendesk Marketplace has a lot of great free and paid apps. Ecommerce companies might install apps to integrate with online shops (<a href="https://www.zendesk.com/apps/support/shopify-for-support/?source=app_directory">Shopify</a>, <a href="https://www.zendesk.com/apps/directory/?q=WooCommerce%20&amp;idx=appsIndex&amp;p=0&amp;utm_medium=zendesk_support&amp;utm_source=marketplace_directory_link">WooCommerce</a>, <a href="https://www.channelreply.com/pricing">Amazon</a>), delivery systems (<a href="https://www.zendesk.com/apps/support/shipstation/?source=app_directory">Shipstation</a>, <a href="https://www.zendesk.com/apps/support/shipup-for-zendesk-support/?source=app_directory">Shipup</a>) and other apps.</li></ol><p><strong>TRIGGERS &amp; AUTOMATIONS</strong></p><ol><li><strong>Autosolve Pending tickets to avoid backlogging</strong><br>Very often pending tickets never get a reply from the customer. It makes sense to solve them automatically to avoid tickets backlog growth. You can also include ‘Email user’ action into this trigger to kindly notify the customer about pending ticket awaiting the customer’s reply. You might build a sophisticated process for this case <a href="https://support.zendesk.com/hc/en-us/community/posts/204143947-Zendesk-on-Zendesk-Bump-Bump-Solve">following Zendesk’s Bump Bump Solve tip</a>.</li><li><strong>Autoclose Solved tickets</strong><br>Since this rule is not mandatory you can use it to keep your tickets queue clean from solved cases that probably will never be reopened again. You can send an educational notification about a closed ticket and ask to provide a new request via the preferred channel. In some cases, this is the main reason to use this rule.</li><li><strong>Notify agents/managers about bad CSAT ratings</strong><br>Being immediately notified about bad ratings is good not only for customer-obsessed brands. Might customers give you fair bad ratings or from misunderstandings, you have a possibility to follow up and try to solve the initial issue and ask the customer to change the rating to a Good one. Use this <a href="https://gyazo.com/9bc5a4ed77a3c92b01d9e2e4fae1f2db">basic example</a> to create a trigger for your needs.</li><li><strong>Deactivate duplicate notifications</strong><br>By default, Zendesk provides you many triggers that are doing the same thing — notifying you about new or updated tickets. Consider deactivating some of them to reduce clutter in your email box. If you have one or two agents you can deactivate triggers to notify groups and/or all agents. You can reactivate them anytime later once you need those triggers again. Go to <em>Admin &gt; Triggers</em> and check what you have.</li></ol><p><strong>KNOWLEDGE BASE (HELP CENTER)</strong></p><ol><li><strong>Add (more) articles to the ‘Promoted articles’ section</strong><br>With Promoted articles feature you can put some of the articles from your Help Center on the Home page. It should naturally help your customers find them and self-service. Check regularly your Knowledge base views stats using <a href="https://support.zendesk.com/hc/en-us/articles/203664486-Analyzing-knowledge-base-activity-Guide-Professional-and-Enterprise-">default Reporting</a> (or using Google Analytics with filtering only effective visits) and update this list of Promoted articles accordingly (check <a href="https://support.zendesk.com/hc/en-us/articles/115002484368-Promoting-an-article-to-the-top-of-the-section">how to promote an article</a>).</li><li><strong>Make Search box bigger to stimulate self-service</strong><br>This task requires some IT skills but is very easy in general. Default search box parameters are pretty fine; nevertheless, I always suggest making it even bigger. Recently I discovered an amazing example of the Help Center by <a href="https://support.gospotcheck.com/hc/en-us">GoSpotcheck</a> with the search box taking the whole first screen.</li><li><strong>Add quick links under the Search box to stimulate self-service</strong><br>The same Help Center example I provided above has this option added. In addition to the Promoted articles, this makes the likelihood of self-service even higher. You should place up to Top 5 quick links there (better 3). Less is more here.</li><li><strong>Put Customer team on the Main page</strong><br>It depends on your privacy policy and guidelines. You can put the collective photo (like <a href="https://support.gospotcheck.com/hc/en-us">GoSpotcheck</a>) or individual profiles (like KissMyKeto <a href="https://help.kissmyketo.com/hc/en-us">here</a>). It makes your customer support much friendlier and helps with your assisted service.</li><li><strong>Provide multiple Contact options and expectations</strong><br>Depending on your customer support strategy (more reactive or proactive) you can put contact options on the Home page. You can manage expectations adding Operating hours and expected reply time for each support channel (like KissMyKeto <a href="https://help.kissmyketo.com/hc/en-us">here</a>).</li></ol><p><strong>KPIs &amp; REPORTING</strong></p><ol><li><strong>Check your main Support KPIs against benchmark data</strong><br>Zendesk collects and analyzes anonymized data about customer support performance of thousands of companies around the globe. And this benchmarking data is available for free. Visit <a href="https://www.zendesk.com/benchmark/">this page</a> when you ask the question “How do we perform compared to the industry average?’.</li><li><strong>Install and use Time Tracking app (Professional plan and above)</strong><br>Speed is one of the most important dimensions of customer service performance (along with volumes and quality). Time Tracking app allows you to track time spent per each ticket update when the agent directly works with the ticket. <a href="https://support.zendesk.com/hc/en-us/articles/203662506-Setting-up-the-Time-Tracking-app-Professional-and-Enterprise-">Setup</a> is very easy and there are detailed articles <a href="https://support.zendesk.com/hc/en-us/articles/360022186134">about building the reporting</a>. Here is a <a href="https://gyazo.com/fc5067df997239074c0ad464a357f98e">real example</a> of the report to track Update Time by Agents.</li><li><strong>Check your Views to Tickets rate in Help Center</strong><br>Self-service is an important part of any customer support strategy and system. With proper setup, this might save your company a lot of resources for providing excellent personalized assisted support. Having HC Views and Tickets stats (tickets created via Help Center) you can calculate the Views:Tickets rate. It gives you a clear picture of how much self-service you have. A good rate is about 10:1, but it varies for companies depending on the audience’s habits and service strategy.</li><li><strong>Check you Searches to Tickets rates in Help Center</strong><br>It is the same story as in the point above but here we look at Searches:Tickets rate. Since customers can rephrase search requests multiple times and you can have a well-filled Knowledge base this rate may reach 50:1 proportion (recently I have seen that one), but usually it is lower. In simple words it means that only 1 ticket is submitted when 50 searches are made.</li><li><strong>Track articles linking activity by agents<br></strong>Placing links to Help Center articles is a good option to promote your Knowledge base and stimulate self-service. Zendesk allows you to track this activity in the default <a href="https://support.zendesk.com/hc/en-us/articles/115004881807-Analyzing-your-Knowledge-Capture-activity-Guide-Professional-and-Enterprise-">Explore dashboard</a> (available on Guide Professional and above) and provides a great <a href="https://support.zendesk.com/hc/en-us/articles/115003373367-Searching-and-linking-articles-using-the-Knowledge-Capture-app">Knowledge Capture app</a> to link articles. Look at leading rates and coach other agents to reach them.</li><li><strong>Build CSAT Comments report in Explore to track feedback topics<br></strong>With new Explore reporting the old Satisfaction report is removed but you will not find the report with CSAT comments there. This point may be obsolete in the near future, but you can use this <a href="https://gyazo.com/e98b739ebe59c29509c73ca09745abdf">report example</a> to get this in your Explore.</li><li><strong>Track macros/shortcuts usage by agents</strong><br>This report is essential since macros are an important productivity tool in Zendesk. Zendesk suggests you build the report using tags. It supposes you need to tag all your tickets and build a tags-based report (in <a href="https://support.zendesk.com/hc/en-us/articles/360022186094-Explore-recipe-Reporting-on-macros-using-tags">Explore</a>). A good rate is about 80%, which means you use 8 macros in 10 tickets on average. And again it varies from company to company. We (at Pythia) provide you Macros Reporting inside our <a href="https://www.zendesk.com/apps/support/pythia-for-support/">Pythia app</a>.</li></ol><p>I hope you enjoyed the checklist and optimized your Zendesk.</p><p>And safe and happy support to everyone!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9c821db24377" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pythia-ai/the-ultimate-checklist-to-optimize-your-zendesk-9c821db24377">The ultimate checklist to optimize your Zendesk</a> was originally published in <a href="https://medium.com/pythia-ai">Pythia AI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Customer Journey idea to set up or scale your customer support system]]></title>
            <link>https://medium.com/pythia-ai/using-customer-journey-idea-to-set-up-or-scale-your-customer-support-system-3b2048789b5f?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b2048789b5f</guid>
            <category><![CDATA[journey-maps]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[zendesk]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Fri, 27 Mar 2020 08:17:12 GMT</pubDate>
            <atom:updated>2020-03-27T08:17:12.938Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Preface</strong></p><p>This post was initially published in <a href="https://support.zendesk.com/hc/en-us/community/posts/360028933614-Using-Customer-Journey-idea-to-set-up-or-scale-your-Zendesk">Zendesk Community</a> but the ideas apply for any customer support system (of any time). Because true methodologies don&#39;t get outdated.</p><p><strong>Post</strong></p><p>Six months ago I promised to write a post answering the <a href="https://support.zendesk.com/hc/en-us/community/posts/360004383387/comments/360002177607">question</a> under the last post of the great series of Knowledge Management Roundtables (the full list is <a href="https://support.zendesk.com/hc/en-us/community/posts/360002981308">here</a>). Today I am happy to publish this post and share the essence of my many-year Zendesk consulting experience with the Community. I would like if more people use this approach to make their Zendesk and customer support experience even better :)</p><p>There are the following sections in my post:</p><ol><li>‘Approach’ or ‘No approach’</li><li>The secret weapon</li><li>Customer Lifecycle and Customer Journey(s)</li><li>Customer Journey inside Zendesk</li></ol><h3>‘Approach’ or ‘No approach’</h3><p>The approach I am presenting below can be used by everyone, but it is more valuable in the following cases:</p><ul><li><strong>Initial setup</strong> of Zendesk — when you have to organize your fresh-started support instance right and systematically from the very beginning;</li><li><strong>Scaling</strong> existing Zendesk setup — when you have to reorganize/optimize your mature and ‘complicated’ support environment.</li></ul><p>In both cases, Zendesk admin (manager) is being enforced to do many things in different parts of Zendesk (incl. Support, Chat, Guide, Explore/Insights, etc). Doing them in a structured way allows avoiding occasional, unsystematic changes leading to chaos in the future (especially when you are fast-growing or a big company already). This also happens when Zendesk admins change or many admins are managing Zendesk with their own different approaches. ‘No approach’ means that one day you will cry and ask ‘What’s going on in our Zendesk!?’ — and nobody will answer clearly why you have what you have now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wemT4TosCxLsnuKc.jpeg" /></figure><h3>The secret weapon</h3><p>The ‘secret weapon’ of my approach to Zendesk setup and management is the Customer Journey idea. This is not my personal know-how — the idea was already known before I was even born. Historically the Customer Journey idea was invented somewhere in the early 1990s in marketing. This idea was an organic result of the modern business transformation guided by the imperatives of the customer service and customer experience quality.</p><p>Today this idea is widely used by most professionals from IT (web and mobile development), sales and advertising, CX management and analytics. In this case, the Customer Journey idea is used as a common client-centric language for both internal (!) and external (!) communications. I think this is the only way to be truly customer-centric — when you seriously think and talk like your customers do.</p><p>The idea of Customer Journey is systematically reflected in the methodology known as <strong>Customer Journey Mapping</strong> (CJM). ‘Mapping’ means a broad set of research methods and management tools for analyzing existing and designing ideal customer experience (some examples of maps are <a href="http://www.servicedesigntools.org/tools/8">here</a>). Having a well-structured Customer Journey Map allows you to create the structured and really <strong>customer-centric</strong> workflows in your Zendesk (and beyond too). The advantage of using СJ idea is that it mimics the real-world experience and by default is transparent for both customers and employees (it means it is easy to learn!).</p><p><em>Customer journey mapping is the process of tracking and describing all the experiences that customers have as they encounter a service or set of services, taking into account not only what happens to them, but also their responses to their experiences.</em></p><h3>Customer Lifecycle and Customer Journey(s)</h3><p>On the <strong>highest level,</strong> this methodology relies on the idea of the <strong>customer lifecycle</strong> — a well-known sequence of stages from the brand awareness to the advocacy / leaving. Below you can see the general example of the customer lifecycle which applies to many businesses (it is about the physical products consumption case). You may have different stages for different products, but the idea is to follow the same approach of presenting the typical customer’s relationship history all the time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t1YYNXGjq7II_rEt.png" /></figure><p><strong>Picture 1. Customer lifecycle example</strong></p><p><strong>On the next deeper levels,</strong> we have more detailed step-by-step <strong>customer journeys</strong> (micro-cycles) reflecting the real-world scenarios of how customers interact with the business on different lifecycle stages via different touchpoints (offline and online ‘interfaces’). In the end, this may be a very complex multi-level system (map), but in my practice, I rarely use more than 3 levels of categorization to avoid intransparency of the final setup (first of all of tickets categorization system).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*DHW2DzyR46kh5OgH.png" /></figure><p><strong>Picture 2. Customer journeys (simplified ecommerce example for 2-level of detalization)</strong></p><h3>Customer Journey inside Zendesk</h3><p>When I’m setting up or scaling Zendesk I always try to implement the idea of Customer Journey in Zendesk. It serves as a leading methodology for organizing service workflows and knowledge assets (HC articles, macros/shortcuts) — along with the whole customer support <strong>journey</strong> (yes, there is its own journey on the support stage!) and inside all parts of you support <strong>environment</strong> (= in different Zendesk products).</p><p><em>I am often asked — why to include non-support stages inside Zendesk (support system!). The answer is simple — you may be asked about everything by your customers. Yes, about 80% of tickets are support requests, but ideally, tickets categorization should cover the whole customer experience environment (to be holistic). Or you can have a big bucket ‘Other’ with many unsorted tickets.</em></p><p>This is what I call the unified (or <strong>holistic</strong>) approach for Zendesk setup and management. Again, this approach helps you to design the holistic customer service system along the whole customer support journey. As a result, your Zendesk becomes not just ‘support’ system, but pretends to be one of the leading customer experience systems in the company (along with call center or physical touchpoints).</p><p>The holistic approach covering the steps of the customer support journey looks like this (table view).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xJRWqsCPejjKkFAW.png" /></figure><p>And the same thing in a visual mode.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*L3MAFbEAAHxmDFnA.png" /></figure><p><strong>Picture 3. The holistic approach for Zendesk setup</strong></p><p>The same set of principles and specific mapped Journeys is being implemented in different Zendesk products building the closed loop of customer service and customer experience management process — that’s so easy and efficient!</p><h3>Conclusion</h3><p>In this post, I’ve tried to show you why Customer Journey is a great ‘tool’ for organizing your support workflows and technologies (Zendesk or any other system) in a really customer-centric and productive way. Let me know if you’re interested in reading the next posts about implementing CJ idea in different parts of Zendesk (with your votes and comments). I am happy to share practical examples and tips.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b2048789b5f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/pythia-ai/using-customer-journey-idea-to-set-up-or-scale-your-customer-support-system-3b2048789b5f">Using Customer Journey idea to set up or scale your customer support system</a> was originally published in <a href="https://medium.com/pythia-ai">Pythia AI</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Looking for a really smart AI assistant? You’ll be surprised.]]></title>
            <link>https://medium.com/chatbots-journal/looking-for-a-really-smart-ai-assistant-suddenly-youll-be-disappointed-ea1031bdf4e5?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea1031bdf4e5</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[chatbots]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Mon, 24 Apr 2017 14:53:51 GMT</pubDate>
            <atom:updated>2017-05-03T10:31:11.983Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*It-ZMLRpUqbyK3eP37WS6g.jpeg" /><figcaption>Photo by <a href="https://stocksnap.io/author/39183">Alex Knight</a>.</figcaption></figure><p>This morning I’ve read two very similar and interesting stories. Their authors told about one of the today’s most overhyped topic — <strong>personal AI assistants</strong>. The both stories are critical and skeptical. They doubt the ability of these “smart” bots to augment human intelligence in an effective manner.</p><p>It might sound a bit strange but I agree with authors. As a founder of AI-inspired startup <a href="https://www.summa.space/">Summa</a> — I’m sure about the big potential of AI in assisting humans. Still, it would be too optimistic if we oversee all limitations and risks of using AI assistants.</p><h3>Real people behind your “smart” AI assistant</h3><p>The first story “<a href="https://www.bloomberg.com/news/articles/2016-04-18/the-humans-hiding-behind-the-chatbots">The Humans Hiding Behind the Chatbots</a>”, delivered in an amazing daily email by <a href="https://medium.com/u/f3a886c9aaff">Sam DeBrule</a>, was published several days ago. As a practitioner, I certainly know that every AI “brain” need manual human setup and training. Thus the fact that “<em>humans had to be on duty at all times</em>” doing a big part of AI’s job behind one of these “smart” bots was very surprising.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kqb44Pdomzubt28D_QEW5Q.gif" /><figcaption>Illustrator: James Singleton/Bloomberg</figcaption></figure><p>The story is full of other interesting facts and thoughts. It raises a very important question about our <strong>privacy</strong> protection by using any AI assistant today. It might look very attractive and cheap, but in fact companies “<em>use similar and vague marketing language and don’t often divulge operational details</em>”. Even if trainers should deal with anonymized data, who knows if they don’t want (and can) de-anonymize them in any way?</p><blockquote>Or, as another former X.ai trainer put it, he wasn’t worried about his job being replaced by a bot. It was so boring he was actually looking forward to not having to do it anymore.</blockquote><p>Today’s AI assistants have a long way of progressive evolution to become really smart. Ideally, they must be quickly trained and become autonomous— so we don’t need constantly supervise them as small children.</p><h3>Unexpected consequences of using AI meeting schedulers</h3><p>The <a href="https://medium.com/startup-grind/unexpected-consequences-of-using-ai-meeting-schedulers-43bd16cb14d7">second story</a> by <a href="https://medium.com/u/eb4c8ee18457">Alex Fishman</a> is written more from the practical point of view. His bottom line isn’t inspiring for AI assistants creators.</p><blockquote>AI assistants are too dumb to trust right now and they’re too dangerous to ignore.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fQfxUi96JQJMCgBGwLNlog.jpeg" /><figcaption><a href="https://stocksnap.io/author/36317">Janko Ferlic</a></figcaption></figure><p>To be honest I am not so extremely skeptical about AI-bot scheduling the meetings. It can be very valuable for some kind of professionals (like HR pros etc) who deal with lots of meetings day by day. It doesn’t look so strange to receive bot’s message when you are seeking a job. You have to follow the existing hiring rules — and to discuss the meeting time with a bot.</p><p>But this use case may not look very farsighted for other cases, especially for networking and everyday communication. Humans like <em>to converse</em> with humans. Today, no bot is likely to withstand a meaningful conversation with human more than several seconds. You do not want to chat with them after few dumb misunderstandings.</p><blockquote>Don’t get me wrong, I understand the need to improve productivity. However, when forcing a tool on your business partners and customers, think about how it may affect <strong>them</strong> and consider the message you’re sending by doing so.</blockquote><p>P.S. My founder’s takeaway from these stories is pretty simple. Putting AI bots in the front of any human-to-human relationships is a very risky idea. No AI bot today is capable to take into account all nuanced contexts and meanings involved in real world communication. They may assist or augment us in the desired manner, but they cannot replace. <em>Humans are not replaceable.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea1031bdf4e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/chatbots-journal/looking-for-a-really-smart-ai-assistant-suddenly-youll-be-disappointed-ea1031bdf4e5">Looking for a really smart AI assistant? You’ll be surprised.</a> was originally published in <a href="https://medium.com/chatbots-journal">Chatbots Journal</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Three stories behind Summa]]></title>
            <link>https://medium.com/@kamarouski/three-stories-behind-summa-5a150801416d?source=rss-91b1b83ccecb------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a150801416d</guid>
            <category><![CDATA[reading]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[knowledge]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Andrei Kamarouski]]></dc:creator>
            <pubDate>Tue, 04 Apr 2017 12:09:50 GMT</pubDate>
            <atom:updated>2017-04-14T20:29:41.970Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*653UPEyQTOMNKZ98LimLtA.png" /></figure><p>I have to tell you three stories that explain why I am developing Summa, why it will be launched on April 22, 2017, and what the mission is that drives Summa.</p><p><strong>Story I. Me and Science</strong></p><p>In 2015, I received a PhD. My thesis was about the methodology of cultural sociology, in other words, how can culture be studied. I had to defend my thesis right on April 22, 2015 — the last birthday of my beloved PhD advisor.</p><p>All these years I have been tormented by one and the same <strong>question</strong> — what value do my articles bring for other researchers? On different online resources, where I published my work, I was able to follow their browsing and downloading activities. <em>But what did I know about their reading experiences? Nothing!</em> Even though the rare citations of my articles gave me pleasure, I knew for sure that they were only a small fraction of the feedback that I probably received from these readers.</p><p><strong>Story II. Me and Teacher</strong></p><p>In 2015, my dear teacher, who was my university and PhD advisor and whom I always called “master”, passed away. Since then I decided to work with and promote his heritage for the rest of my life.</p><p>My teacher was encyclopediacally educated. He wrote a lot, but even more important, he read. He was a voracious reader, and in his archives I found dozens of printed articles with his handcrafted marks and annotations. I knew him, and I therefore understand <em>what </em>he marked<em> </em>and <em>why</em> he marked it there. And one day I got an <strong>idea</strong>: why not to try to “decipher” his reading “technology” and digitize it. The thought of me reading new articles, <em>with his eyes</em>, sounded like an incredible idea.</p><p><strong>Story III. Me and Business</strong></p><p>Since 2010 I have been working as a business consultant. I have fulfilled various projects in different domains and businesses. All of these projects were amazing challenges that allowed me to apply my knowledge and to prove its value. And also to earn money.</p><p>A frequent change of projects always challenged me with switching quickly between different business domains and learning new knowledge. These tasks require good searching and reading skills as well as good networking skills. I was always dreaming about some sort of <strong>digital assistant</strong> who could help me with finding, reading and checking content, the same as I would do it.</p><p><strong>Everything has its beginning</strong></p><p>One day I realized that all three stories were about <strong>the</strong> <strong>same question</strong>: how do we work with information? Simply put, it is about reading. Reading remains the most important way we get information from the world.</p><p>In the digital era, we are facing a boom in the production of content. <em>However, our basic content “consumption technology” (aka reading) has somewhat changed.</em> That’s because we are facing many other issues, like political polarization due to massive fake content misinformation, or job losses due to our routine labor rapid automation.</p><p>As very different people, we all have very similar challenges — we have to keep ourselves always prepared for modern life by constantly expanding our knowledge and skills.</p><blockquote>So now is the right time to find new ways of how we generate and promote knowledge. And that’s why Summa’s Mission is to empower human creativity by providing advanced knowledge acquisition technologies.</blockquote><p>And that’s why I decided to take the risk of developing Summa. I am very motivated by dreams from my stories and many other stories that I find everyday around the web. I will make my dreams a reality.</p><p>You can help develop Summa by joining the closed beta. Sign up <a href="http://www.summa.space/"><strong>here</strong></a> or just write a few words on <strong><em>beta@summa.space</em></strong>.</p><p>Join Summa. Start to <strong>read different</strong>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a150801416d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>