<?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 Guy Nirpaz on Medium]]></title>
        <description><![CDATA[Stories by Guy Nirpaz on Medium]]></description>
        <link>https://medium.com/@guynirpaz?source=rss-13cfa7557c98------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*hoMTXV4h4jjZnHVrPweu7g.png</url>
            <title>Stories by Guy Nirpaz on Medium</title>
            <link>https://medium.com/@guynirpaz?source=rss-13cfa7557c98------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 05:33:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@guynirpaz/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[customer success — mainstream now]]></title>
            <link>https://medium.com/farm-dont-hunt/customer-success-mainstream-now-8f890356f610?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f890356f610</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[business-strategy]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Sat, 09 Jun 2018 13:56:19 GMT</pubDate>
            <atom:updated>2018-06-09T13:56:19.851Z</atom:updated>
            <content:encoded><![CDATA[<p>Customer success is mainstream now. The largest companies in the world are taking on ambitious initiatives to center their operations around their customers.</p><p>Some compnies call it Customer For Life, other Customer Obsession — I call it E2C — Enterprise To Customer, as it doesn’t matter if it’s in B2B or B2C, what matters is the direction from enterprise to customer. The focus is customer success.</p><p>Exciting times!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f890356f610" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farm-dont-hunt/customer-success-mainstream-now-8f890356f610">customer success — mainstream now</a> was originally published in <a href="https://medium.com/farm-dont-hunt">Farm Don’t Hunt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is Customer Health Score?]]></title>
            <link>https://medium.com/farm-dont-hunt/what-is-customer-health-score-68b9067d031c?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/68b9067d031c</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Sun, 15 Oct 2017 14:21:52 GMT</pubDate>
            <atom:updated>2017-10-15T14:23:15.409Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Customer Health Score</strong> summarizes multiple dimensions of customer data measures and classifies them into a single representation of either green, yellow or red. It is a consolidation all the information the company has about the customer, from all probes, people and systems, past and current.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rID20vECEimYZf4vXF1FoQ.png" /></figure><p>Companies use customer health to speed up and scale communication, prioritization, decision making and forecasting of their customer success operations.</p><p>The model is very simple to understand:</p><p>When customer is green, the customer is getting value from the products and services, the engagement is effective and the company should continue to manage the customer in a similar way.</p><p>On the other hand once customer is marked as red, there is something wrong that requires immediate attention with either the value the customer is not getting or the engagement with the account. Action is required to address it. Customer health is also known as the one of the key components of an<a href="https://www.totango.com/blog/2016/07/understanding-early-warning-systems-for-customer-success/"> early warning system</a>.</p><p>Now that we’ve established the purpose of customer health, there are two other considerations that we need to take into account when we designed our own customer success model. I call the first one “expressiveness of customer health”. Put differently, when something is wrong and the customer is marked as yellow or red — why is that? Is there a single reason, multiple reasons and what those reasons are?</p><p>The second consideration that ties into the expressiveness of customer health answers what are the metrics/measures that should be included in the customer health and what is the best way to formalize those into green, yellow or red?</p><p><strong>Expressiveness of Customer Health</strong></p><p>Sometimes when companies introduce customer health model for their business they they might deliberate on the objective and the formals for health forever the classical analysis paralysis syndrome. To make it clear here’s what we’re trying to solve for:</p><ol><li>What makes a customer green?</li><li>What makes a customer red?</li><li>Yellow — if the customer is not green and not red they are yellow, and in this case we want to answer, why are they not green, what are the gaps?</li></ol><p>Health score must be actionable and by knowing the reasons that attributes to the color classification the company has a clear path for action.</p><p><strong>What are the measures that formulate Customer Health?</strong></p><p>What I have found most effective is to group the measures into categories.</p><p>The most common health categories I suggest to start with are:</p><ol><li><strong>Product Usage and Adoption</strong> — what the volume and depth of use</li><li><strong>License Utilization</strong> — how much of the sold licenses are actually being utilized</li><li><strong>Business Results</strong> — is the customer getting the value they signed up for?</li><li><strong>Engagement</strong> — support, billing, marketing, customer success engagements — how are those going?</li><li><strong>Advocacy</strong> — is this customer referenceable, advocate?</li></ol><p>I’ll follow up with specific measures per each category in a follow up blog soon.</p><p>When we tie it all together the health formula should be something like this:</p><ol><li>Green Customer — if <strong>All of the</strong> thresholds of usage, utilization, business results, engagement and advocacy are met.</li><li>Red Customer — if the customer is flagged in <strong>At Least</strong> on of those categories. There could be a sharp decline is usage or the customer is a detractor or not paying their bills and so forth. I’m sure you get the point</li><li>Yellow Customer — those who are not green nor red. They only meet <strong>Some of </strong>the green criteria but not all of them. So there is clear room for improvement but on the other hand nothing is burning (yet).</li></ol><p>With this model of health formula we don’t only have the abiltiy to color each customer we can also communicate very clearly the reasons behind the health classification.</p><p><strong>Rule Based Customer Health vs. Linear Customer Health</strong></p><p>Using this logical conditions is also known as Rule Based Customer Health. Most people start with customer health using a spreadsheet. They use the excel formulas to summarize the metrics across a row and come up with a number. This is known as linear based health.</p><p>Linear health has few known limitation compared to rule based customer health:</p><ul><li><strong>Masking </strong>— It is very easy to understand customers that score 100 (all good) or 0 (all bad), but it becomes very difficult to look at a customer that scores 30 to 70 to really understand the reasons behind that.</li><li><strong>Difficult to Change </strong>— formula change in linear health is very difficult to do and in many cases creates confusion</li></ul><p>The intuitive value of customer health is clear. Better, fast and more accurate decision making process and being proactive about customer operations.</p><p>If you find this topic relevant for you, I highly recommend that you sign up (link below) for this coming webinar that takes customer health tuning into the next level.</p><p><a href="https://cc.readytalk.com/registration/#/?meeting=6bpzvxis0zkg&amp;campaign=bli12m54574d">https://cc.readytalk.com/registration/#/?meeting=6bpzvxis0zkg&amp;campaign=bli12m54574d</a></p><p>Please let me know in the comments what you think about the topic.</p><p>Guy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68b9067d031c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farm-dont-hunt/what-is-customer-health-score-68b9067d031c">What is Customer Health Score?</a> was originally published in <a href="https://medium.com/farm-dont-hunt">Farm Don’t Hunt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Implementing the customer success bot Zoe in Slack]]></title>
            <link>https://medium.com/slack-developer-blog/implementing-the-customer-success-bot-zoe-in-slack-8287a91f8198?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/8287a91f8198</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[bots]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Fri, 21 Apr 2017 16:54:41 GMT</pubDate>
            <atom:updated>2017-11-09T18:19:59.116Z</atom:updated>
            <content:encoded><![CDATA[<h4>What we learned about simplicity, iterative development, and community</h4><p><a href="https://www.totango.com/?utm_source=slack&amp;utm_medium=partner&amp;utm_campaign=2017-blog#zoe">Zoe</a> is a new bot we developed at Totango that allows users to ask questions about customers and customer segments directly in Slack.</p><p>A typical use case might be a CEO asking “@zoe, tell me about Acme.” Zoe will respond in Slack with KPIs for the customer Acme Inc, displayed alongside recent interactions a customer success team had with that client .</p><p>Or, a product manager might ask Zoe to “list all premium customers using feature <em>xyz</em>.” Zoe will respond by displaying a segment of users from premium accounts who have adopted that feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S9druoGIT8Kz99gpXnTWLw.png" /><figcaption>Zoe Bot in Slack</figcaption></figure><p>Zoe is built as an overlay over our core <a href="https://www.totango.com/customer-success-center/?utm_source=slack&amp;utm_medium=partner&amp;utm_campaign=2017-blog">customer success technology platform</a>, which does the heavy lifting of building out a rich set of insights from separate systems, such as an organization’s Salesforce CRM or a Segment.io data feed. <a href="https://www.totango.com/slack/?utm_source=slack&amp;utm_medium=partner&amp;utm_campaign=2017-blog">In Slack</a>, Zoe’s conversational interface makes it easier to access this key information in a straightforward way that all users – regardless of their understanding of Totango – can access.</p><p>In this post, I’ll share some lessons we learned as we developed the first Zoe implementation. In hindsight they seem quite obvious, but I wish someone would have pointed them out to me when we embarked on this mission 🙂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m4WOOgP65e1TPnWkUJYWjQ.png" /><figcaption>Zoe — Show me…</figcaption></figure><h3><strong>Give users only what they need</strong></h3><p>When we began developing Zoe, one of our biggest considerations was data density.</p><p>Zoe is built on top of Totango <a href="https://www.totango.com/blog/2017/03/totango-dna-cx-the-customer-centric-data-technology-powering-zoe/?utm_source=slack&amp;utm_medium=partner&amp;utm_campaign=2017-blog">DNA-CX</a>, our proprietary data architecture which contains multiple metrics and dimensions of customer data.</p><p>When you’re building a traditional web-based UI, you can use many techniques to allow users to gradually discover and explore data. For example, in order to gauge the process of an account, a customer success manager might need to review the week-over-week growth of a certain metric. The Totango UI supports that need by allowing a manager to click on a metric to drill down into a trend.</p><p>But when you’re building a bot, your visualization and interaction options are more limited.</p><p>Slack <a href="https://api.slack.com/docs/message-attachments">messages attachments </a>are quite flexible — they can include buttons, attachments, emojis and other goodness — but their paradigm is closer to a command line than to a web UI: you type in some text, and get a short text response back. This took us some time to get used to, and our first designs spat out pages of metrics to even the most simple request for data.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BsK7UeRi1SR8uO-jPF2rFA.jpeg" /><figcaption>Zoe — early design concepts</figcaption></figure><p>However, our usability tests and analytics told a different story: we were overwhelming users with data. We discovered that as we reduced the density of information, users were able to better understand and act on Zoe’s responses.</p><p>The rule became: “<strong>Between simplicity and depth of information, always opt for simplicity.”</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uTqwP8mX3wpsbno9oneg5A.jpeg" /><figcaption>Zoe — transition from desktop to chat experience</figcaption></figure><p>We kept removing stuff until we could not remove anything else. In many cases we had to let go of a certain dimension of data or work harder on the back end to translate several data points into a simpler insight.</p><p>Our current bot interface translates our web UI with multiple charts, tabs, and drilldowns into a card view with five options to show more. Not only is this a better design paradigm in the chat interface, it’s also better for Zoe’s users, who are typically on the go and require the “Cliff’s notes” version.</p><p>Users get the option to link out to a more detailed interface, but otherwise the high level of information keeps the conversation going.</p><h3><strong>Choose your SDKs wisely</strong></h3><p>Early on, we knew we wanted an abstraction layer over Zoe’s communication with Slack. We decided to try <a href="https://github.com/howdyai/botkit">Botkit</a>.</p><p>Botkit is an open-source bot development kit that makes it easy to build bots over many platforms, like Slack, Facebook, or Kik.</p><p>You can use Botkit’s neat plugin architecture to connect anything — from custom logging to NLP engines — into your bot’s conversations. We were able to easily plug in support for our own operational logging and metrics without much effort or fuss, which is always great when adopting a new framework.</p><p>It was very easy to get started with Botkit, and the project has a strong open-source community and great documentation. I highly recommend it.</p><h3><strong>Separate your bot interface and business logic into separate microservices</strong></h3><p>Our first iteration of Zoe included a microservice that took care of fulfilling a Zoe-related request end to end: everything from listening for incoming Slack messages, to parsing them, resolving them, and applying the logic to translate them into a request for our platform.</p><p>However, that structure made it difficult for us to iterate quickly. Each time we wanted to change our code to tweak our response message format, for example, we had to consider the impact of the change on the rest of the business logic before testing and eventually deploying the change.</p><p>We eventually decomposed the service into two microservices, each responsible for different parts of the user experience:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y-PmGeNt5h5VNfZtU1fL8g.jpeg" /><figcaption>DNA-CX as a backbone for all Zoe product line</figcaption></figure><ul><li><strong>Zoe Bot</strong> — The interface to Slack and other platforms. This microservice processes incoming user commands, interprets them, and passes the request to the business logic layer.</li><li><strong>Zoe Brain</strong> — The business layer that processes requests and pulls the needed information from Totango’s core data platform.</li></ul><p>You can think of this as an implementation pattern for bots in general: separate your bot interface from your app’s core business logic.</p><p>Beyond separating concerns and increasing development agility, you’ll be able to keep each service <em>stateless</em>, making it easier to scale your app as your user base grows.</p><h3><strong>Quick iterations help balance simplicity and information density</strong></h3><p>With a bot, the difference in adoption between an okay experience and a great one are staggering. Users have very little patience to work with a bot that provides irrelevant responses.</p><p>For that reason, you need the mindset and the tools to deploy many versions of your bot, and then iterate quickly based on your learnings.</p><p>We made it a point to release the first version of Zoe one week after we started working on it. But we used this as a base to gradually expose new versions to new users and gather feedback.</p><p>We were able to iterate over a dozen versions of Zoe’s basic response in a single development sprint, enabling us to reach a format that was the “just right” balance of content and information density.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*83UixcDP5Abj-P_OReeOrg.jpeg" /><figcaption>Zoe — from early to final design iterations</figcaption></figure><h3><strong>Think beyond the bot</strong></h3><p>A truly conversational interface isn’t just about building a bot interface. A conversation doesn’t always start with “@zoe,” and it does not always end with Zoe spitting out information back to the user.</p><p>For instance, we discovered that customer success managers often need to loop in other people, like an engineer, while working from the native Totango application. Sure, they could switch their application over to Slack to do that, but sharing information to Slack with a “Share to Slack” feature was more convenient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FnMp17c4Re-_ea45uprh9Q.jpeg" /><figcaption>Zoe — share (democratize)</figcaption></figure><p>Building a conversational interface means making it easy to get things done while interacting in the most frictionless way possible. Sometimes that involves speaking with a bot in a channel… but it can mean more than that.</p><h3><strong>Work with the community</strong></h3><p>Finally, work with the community.</p><p>Slack’s developer support team is awesome and has helped us every step of the way. From validating our architecture, recommending design patterns, sharing their roadmap and even publishing this blog :-)</p><p>In addition, the team at Botkit has been great resource.</p><p>We’ve spent the last few months building <a href="https://www.totango.com/?utm_source=slack&amp;utm_medium=partner&amp;utm_campaign=2017-blog#zoe">Zoe</a> and have recently released it to the market. Even more exciting to us, we’re seeing new user types, such as engineers or executives, use Zoe to have more meaningful, data-informed conversations about customers….which means we’re closer to our vision of making customer success everyone’s business!</p><p><em>This post was mostly written by Oren Raboy, Totango co-founder &amp; VP of Engineering</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8287a91f8198" width="1" height="1" alt=""><hr><p><a href="https://medium.com/slack-developer-blog/implementing-the-customer-success-bot-zoe-in-slack-8287a91f8198">Implementing the customer success bot Zoe in Slack</a> was originally published in <a href="https://medium.com/slack-developer-blog">Slack Platform Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The implications of the changing workforce demographics]]></title>
            <link>https://medium.com/@guynirpaz/the-implications-of-the-changing-workforce-demographics-52626792225f?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/52626792225f</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[workplace]]></category>
            <category><![CDATA[work]]></category>
            <category><![CDATA[recruiting]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Tue, 18 Apr 2017 05:50:58 GMT</pubDate>
            <atom:updated>2017-04-18T05:50:58.176Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FSVlCCNLLUOE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DSVlCCNLLUOE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FSVlCCNLLUOE%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/e60062a72c3a37bc14e464e956a901d9/href">https://medium.com/media/e60062a72c3a37bc14e464e956a901d9/href</a></iframe><p>I’m never tired of seeing this pitch by my old buddy Dan Finnigan, Jobvite CEO and a true thought leader in the space of HR and recruiting.</p><p>You can watch the rest of the customer success summit video on YouTube — start at www.customersuccesssummit.com</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52626792225f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customer Obsession — Company Guide]]></title>
            <link>https://medium.com/farm-dont-hunt/customer-obsession-company-guide-e6bd6ea3ae90?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6bd6ea3ae90</guid>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[amazon]]></category>
            <category><![CDATA[cutomer-experience]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Fri, 14 Apr 2017 16:09:36 GMT</pubDate>
            <atom:updated>2017-04-14T16:50:47.804Z</atom:updated>
            <content:encoded><![CDATA[<h4>True customer obsession is a key principle that keeps companies relevant, competitive, and growing. Without it, companies stagnate, become irrelevant, decline, and die.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2Fmjfakc5vzzJ1Uv9gmJsw.jpeg" /><figcaption>Zoe for True Customer Obsession</figcaption></figure><p>I was inspired by Jeff Bezos, Amazon CEO, when reading his 2016 Letter to Amazon Shareholders. In this year’s letter, he outlines four key principles that he believes are critical to keeping his company, or any company for that matter, relevant, competitive, and on a growth trajectory. You can read the full letter <a href="https://www.scribd.com/document/344982413/Amazon-2016-Letter-to-Shareholders">here</a>.</p><p>I find a striking resemblance between the ideas depicted by Bezos, which could lead Amazon to over a <a href="http://www.cnbc.com/2017/03/29/amazon-will-be-worth-1-trillion-one-day-barclays-predicts.html">trillion dollars</a> as a potential market cap, and the <a href="http://www.totango.com/?utm_source=website&amp;utm_medium=blog&amp;utm_campaign=2017-blog">Zoe</a> product and concept that Totango introduced not too long ago. Here are the parellels:</p><h3>True Customer Obsession</h3><p>Customer obsession is a company wide decision that is necessary for a company culture that influences and projects onto everything the company does.</p><p>Here’s the relevant quoted section of the letter:</p><blockquote><strong><em>True Customer Obsession</em></strong></blockquote><blockquote><em>There are many ways to center a business. You can be competitor focused, you can be product focused, you can be technology focused, you can be business model focused, and there are more. But in my view, obsessive customer focus is by far the most protective of Day 1 vitality. Why? There are many advantages to a customer-centric approach, but here’s the big one: customers are always beautifully, wonderfully dissatisfied, even when they report being happy and business is great. Even when they don’t yet know it, customers want something better, and your desire to delight customers will drive you to invention on their behalf. No customer ever asked Amazon to create the Prime membership program, but it sure turns out they wanted it, and I could give you many such examples. Staying in Day 1 requires you to experiment patiently, accept failures, plant seeds, protect saplings, and double down when you see customer delight. A customer-obsessed culture best creates the conditions where all of that can happen.</em></blockquote><p>The idea of true customer obsession that involves everyone within the company and is embedded into the culture and the everyday activities of the organization is exactly the idea that led to the creation of <a href="http://www.totango.com/?utm_source=website&amp;utm_medium=blog&amp;utm_campaign=2017-blog">Zoe</a>. I was struggling with the challenge of how to make a bigger impact with customer success, an impact that ripples across the entire organization. I asked myself, “What is customer success 2.0?” The answer that came to me, which clearly resonates with Bezos: company wide customer obsession.</p><p>In my own words: True customer obsession is a way to center and align your business around your customers.</p><h3>Resist Proxies</h3><p>In his letter, Bezos cautions against external proxies in the form of strict processes or addiction to market research. Instead he advises companies to assess each situation and make the right decisions for that particular situation, while also developing deep intuition and a direct connection to the situation. A very timely and highly-publicized negative example of this pitfall is illustrated in the recent <a href="http://www.cnn.com/2017/04/12/travel/united-passenger-pulled-off-flight/">United debacle</a>. But we don’t need to go to the extreme to know that there are many cases in which companies are applying the right rules for the wrong situations.</p><p>One of the key concepts of Zoe is the enablement of volunteer participation of employees in actions to impact customers. Instead of hierarchies and tasks and processes, Zoe encourages everyone in a company to use their expertise and swarm organically to solve customer issues with Impact Steps. Impact Steps give visibility into the commitments and progress of each customer champion to the entire company, enabling everyone to rally around the customer cause. Zoe and Impact Steps are designed so each situation can be assessed and acted upon individually, superseding process and avoiding stagnation.</p><h3>Embrace External Trends</h3><p>Bezos also talks about the importance of identifying (easy), then embracing and adopting (hard) meaningful external trends. The two biggest tech trends right now are 1) AI for data and 2) conversational user interfaces (like Alexa) that allow humans to interact with data in a conversational way.</p><p>Zoe was designed with Alexa in mind: let’s make a simple conversational interface where you can ask and receive human responses. <a href="https://www.totango.com/blog/2017/03/totango-dna-cx-the-customer-centric-data-technology-powering-zoe/?utm_source=website&amp;utm_medium=blog&amp;utm_campaign=2017-blog">DNA-CX</a>, the AI of the customer data behind Zoe, is an incredibly powerful, flexible architecture that customizes itself for each business to provide real-time customer context. DNA-CX is the only customer-centric data model, and it’s made possible by the leaps in AI advancement in recent years.</p><h3>High Velocity Decision Making</h3><p>The final and primary principle Bezos divulges is the concept of “Disagree and Commit.” Resist the temptation to wait for perfect decisions. Instead optimize for fast interactions over perfect attempts.</p><p>An important element of decision-making is the availability of information. In many organizations, customer data is locked in systems, silos, and storage places that are not immediately available. This can slow down decision-making, making it far from optimal.</p><p>Zoe is designed to continuously collect all streams of customer information in real-time and democratize it, making the data accessible via any channel that’s used by those needing to make decisions. This is the reason Zoe ‘lives’ within communication channels like Slack and email so there is no need to login to yet another IT system, which prevents all potential barriers to customer data. This level of transparency is designed to allow anyone within the company to make the right customer decisions, over time, all the time.</p><p>At a recent VC dinner I attended, all participants were asked, “On which company would you bet all your money?” Most of the entrepreneurs, CEOs, and venture partners in the room named Amazon. I found Bezos’s message inspiring and its alignment with Zoe undeniable. If you’re also inspired by Amazon and its future, <a href="https://www.totango.com/request-zoe/?utm_source=website&amp;utm_medium=blog&amp;utm_campaign=2017-blog">Zoe</a> can be the catalyst for a similar change in your company.</p><p><em>Originally posted on </em><a href="https://www.totango.com/blog/2017/04/true-customer-obsession-is-key-jeff-i-agree/"><em>https://www.totango.com/blog/2017/04/true-customer-obsession-is-key-jeff-i-agree/</em></a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*xVfgdQqtTVR0Nlvdag_lUw.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6bd6ea3ae90" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farm-dont-hunt/customer-obsession-company-guide-e6bd6ea3ae90">Customer Obsession — Company Guide</a> was originally published in <a href="https://medium.com/farm-dont-hunt">Farm Don’t Hunt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why We Chose Slack as Zoe’s First Integration]]></title>
            <link>https://medium.com/farm-dont-hunt/why-we-chose-slack-as-zoes-first-integration-f87d86be1763?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/f87d86be1763</guid>
            <category><![CDATA[slack]]></category>
            <category><![CDATA[slackbot]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Thu, 16 Mar 2017 16:17:52 GMT</pubDate>
            <atom:updated>2017-03-16T16:20:18.008Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bvSDJ8RPXBFUxTOKa8sj2A.jpeg" /><figcaption>Zoe and Slack</figcaption></figure><p>We’re thrilled to introduce <a href="https://www.totango.com/?utm_source=website&amp;utm_medium=blog&amp;utm_campaign=2017-blog/#zoe">Zoe</a>, an intelligent, conversational chatbot available now in Slack, the collaborative work environment, and via email.</p><p>Slack is making team collaboration effective and fun, which is the reason that we at Totango chose Slack as the first platform for Zoe. Well, that and the fact that over 60% of our customers use Slack, so it made sense to show value to our current customers as quickly as possible (and encourage future customers to make Slack an integral part of their tech stack along with Totango).</p><p>In case you haven’t heard, <a href="https://www.totango.com/?utm_source=website&amp;utm_medium=blog&amp;utm_campaign=2017-blog/#zoe">Zoe</a> is a friendly interface to align your company around your customer. Zoe gives everyone in the company access to the rich data available in Totango and allows teams to self-organize to proactively impact customers. Zoe enables companies to make the customer the cornerstone of everything they do.</p><p>Totango is constantly innovating customer success technology solutions. We define customer success as a modern way to align your company’s products, services, and employees around your customers to drive business growth. The logic seems obvious: if companies proactively ensure that their customers get value from their products and services, renewal rates and repeat buys will skyrocket, and expansion business will inevitably increase over time. SaaS businesses are familiar with this concept, but we think it’s universally true for almost any business.</p><p>Zoe in Slack appears as a chat-bot (cleverly named Zoe) and is designed to make it easy for the entire company to participate in customer success.</p><p>There are two main use cases for Zoe in Slack:</p><p>1. Zoe democratizes customer data, making it easily accessible to everyone in the company. Any employee can simply ask “@zoe tell me about…” and Zoe will immediately provide the rich customer data previously only available in the Totango Customer Success Center. We’ve named the data Totango DNA-CX™ and its structure is completely unique. DNA-CX is the proprietary, dynamic, no-schema data index that gives an accurate, real-time picture of each business’s unique relationship with their customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*rXbImTZUBAk3FCfn.png" /></figure><p>2. Zoe enables cross-functional teams to self-organize and work together for customer causes. By making it easy for employees to ask for help on initiatives to benefit the customer, experts from all departments can frictionlessly come together to quickly make an impact. When introduced to an impact step, employees just say “@zoe sign me up for &lt;customer champion action of choice&gt;” and Zoe makes them a part of the customer-oriented activity. Successfully completed impact steps can be shared on company-wide Slack channels such as the #general channel, giving visibility into the impacts that employees are working on and allowing company-wide acknowledgement of everyone’s participation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/920/0*dxcrDrzLUQ6AkDrK.png" /></figure><p>Totango customers can try Zoe immediately — take advantage of a free 7 day trial and see the power of this revolutionary product. Visit the <a href="https://www.totango.com/slack/?utm_source=website&amp;utm_medium=blog&amp;utm_campaign=2017-blog">Slack installation page</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f87d86be1763" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farm-dont-hunt/why-we-chose-slack-as-zoes-first-integration-f87d86be1763">Why We Chose Slack as Zoe’s First Integration</a> was originally published in <a href="https://medium.com/farm-dont-hunt">Farm Don’t Hunt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[See you at #CSSummit17 in few weeks]]></title>
            <link>https://medium.com/farm-dont-hunt/see-you-at-cssummit17-in-few-weeks-52d1a6d4f2c8?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/52d1a6d4f2c8</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Sat, 28 Jan 2017 17:19:51 GMT</pubDate>
            <atom:updated>2017-01-28T17:21:29.072Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rEir0f7j5BTB8DR3ghBW4g.jpeg" /><figcaption>customer success friends that are coming to #CSSummit17 this year</figcaption></figure><p>I’m excited about <a href="http://www.customersuccesssummit.com/">customer success summit</a> coming up in just few weeks on Feb 27–28 in San Francisco. First time attendees tend to under estimate the size of the event. I usually hear reaction that goes like: “I didn’t imagine that there are so many people interested in customer success…” followed by “so much great content, so many people already share practical experience, I’ve learned a lot…”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*A6ZkcD5XtVo3lZjF8JnxJQ.jpeg" /><figcaption>customer success friends that are coming to #CSSummit17 this year</figcaption></figure><p>Customer Success Summit’s mission was always to promote and advance the customer success thinking, methods and practices by bringing together like-minded people from all over the world. Two days in which they share learnings and experiences. We’ve always made sure that there is a clear separation between the commercials of summit and it’s content, <a href="http://www.customersuccesssummit.com/#agenda">speaker line-up</a> and attendees.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*V-droDAjYVRa2xzM0xeFUA.jpeg" /><figcaption>customer success friends that are coming to #CSSummit17 this year</figcaption></figure><p>I’d like everyone in customer success, customer experience, sales and marketing and other customer-centric thinking and practice to attend this year.</p><p>For the loyal readers of “Farm Don’t Hunt” community I’d like to offer</p><p><strong>FDH-PROMO </strong>promo code</p><p>which provides you 25% discount for the first 50 tickets.</p><p>I’m looking forward to seeing you there, and meet you in person. If you’d like for me to sign your copy of “Farm Don’t Hunt” — please bring it with you and I’d love to chat and learn about your experience with the book.</p><p>Registration link: <a href="http://www.customersuccesssummit.com/">http://www.customersuccesssummit.com</a></p><p>Book link: <a href="http://www.farmdonthunt.com/">http://www.farmdonthunt.com</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4yqkNmBkJGPSkr5WlW_Nig.jpeg" /><figcaption>customer success friends that are coming to #CSSummit17 this year</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52d1a6d4f2c8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farm-dont-hunt/see-you-at-cssummit17-in-few-weeks-52d1a6d4f2c8">See you at #CSSummit17 in few weeks</a> was originally published in <a href="https://medium.com/farm-dont-hunt">Farm Don’t Hunt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who’s in customer success?]]></title>
            <link>https://medium.com/farm-dont-hunt/who-is-responsible-for-customer-success-68758d767e5e?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/68758d767e5e</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Wed, 25 Jan 2017 23:41:34 GMT</pubDate>
            <atom:updated>2017-04-14T16:46:40.860Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*toUb1KIhdpibs35-TcMxmQ.jpeg" /></figure><p>The focus in growth and attention of customer success within an organization is definitely a very positive trend. Many companies, including very large enterprises, are remodeling their businesses to support customer centric organizational structures. They actively fund, staff and resource customer success initiatives.</p><h3>Is there too much customer success?</h3><p>Too much customer success is a problem. Or better put, relying too heavily on customer success teams to ensure the delivery of value to customers is a problem. Companies with customer centric cultures are built such that everyone in the company is part of the customer success mission. The decision making and prioritization is organized so that delivering value to customers is the mission of the engineering, product, marketing, sales <em>and</em> customer success teams. Not just the customer success team.</p><p>Putting the customer in the center of the company isn’t just a good idea. It’s also not realistic that a single team can solely own the success of the customer. It is often dependent on the products: their fit with the needs of the customer, the quality and the experience of the services, to name just few of the additional factors.</p><p>In most companies, there are many talented people with great skills and capabilities that can benefit the success of the customer who are not in customer success. If only there was a way to enable and enlist them into the “customer cause.”</p><p>Ask people in your company — “Who owns the customer?” If the answer comes in the form of a customer success manager’s name, then you know it’s the wrong answer. The right answer is — <strong>we all are</strong>. The team owns the customer, or better put, the company owns the customer.</p><h3>Customer success as company goal</h3><p>From working with thousands of customer success organizations, I’m now able to recognize patterns and behaviors that differentiate customer centric enterprises and functional organizations.</p><p>It starts with culture, mission and values, but it doesn’t stop there. It continues with day-to-day behaviors that can be encouraged, unlocking the great potential that already exists within organizations.</p><p>This is going to be the topic of my keynote at #CSSummit17, on Feb 27–28 — tickets are still available at <a href="http://www.customersuccesssummit.com/">www.customersuccesssummit.com</a>. I hope you can join me there!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*xVfgdQqtTVR0Nlvdag_lUw.gif" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68758d767e5e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farm-dont-hunt/who-is-responsible-for-customer-success-68758d767e5e">Who’s in customer success?</a> was originally published in <a href="https://medium.com/farm-dont-hunt">Farm Don’t Hunt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quick advice for sales/marketing emails]]></title>
            <link>https://medium.com/@guynirpaz/quick-advice-for-sales-marketing-emails-159f051f3cc?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/159f051f3cc</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[startup]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Tue, 03 Jan 2017 23:56:54 GMT</pubDate>
            <atom:updated>2017-01-04T16:48:59.274Z</atom:updated>
            <content:encoded><![CDATA[<p>This is not my usual topic, but it does connect to customer centric thinking, looking at the customer from the “<em>outside in”</em>.</p><p>I’ve received the following email this morning:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8E1Nh0v-D8jVyyr8WnsyTQ.png" /><figcaption>bad marketing email I’ve sent to a startup CEO</figcaption></figure><p>As I was at the end of my morning coffee, I’ve taken the time to write the following response to the very ineffective sales person.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5drJFRXn9xfOB2ed9hKQ6g.png" /></figure><p>I have a lot of respect and sympathy to people that are making their living in sales and trying to penetrate into customer accounts. I do believe that If you can be empathetic with the person your are trying to reach you’ll be way more successful.</p><p>My points are:</p><ol><li>Think of me first as your customer</li><li>Start with value to me short and to the point</li><li>Don’t ask for my time, at least not yet, show me of your value before you ask for my time.</li></ol><p>I’m not trying to be an arrogant prick, I’m just very busy, and like many other people, I’d like to make sure my days are productive and fruitful. I’m also very curious person and I’m a big fan of new technologies.</p><p>Bottom line, if you’ll follow those three rules, I can guarantee you that you’ll have more success with me.</p><p>If you find this useful, please like it and share it with your SDR/BDR/Marketing team members ;)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=159f051f3cc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing #CSSummit17, Feb 27–28]]></title>
            <link>https://medium.com/farm-dont-hunt/announcing-cssummit17-feb-27-28-41ad6bbb9e08?source=rss-13cfa7557c98------2</link>
            <guid isPermaLink="false">https://medium.com/p/41ad6bbb9e08</guid>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Guy Nirpaz]]></dc:creator>
            <pubDate>Wed, 07 Dec 2016 21:05:08 GMT</pubDate>
            <atom:updated>2016-12-07T21:05:08.934Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m happy to announce the 5th annual <a href="http://www.customersuccesssummit.com/">Customer Success Summit 2017</a> coming February 27–28 in San Francisco at the Marriott Marquis.</p><p>Since it’s inception in 2013, the Customer Success Summit is known for it’s high quality content and endless learning and networking opportunities. It is an event that promotes and progresses the practices and methods of customer success for individuals, teams and companies. It is always early in the year, so folks can bring back the learnings and impact the year.</p><figure><a href="http://www.customersuccesssummit.com/"><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9FjxTZGy9VbLGBigJ5u1Bg.jpeg" /></a><figcaption>Customer Success Summit 2017</figcaption></figure><h3><strong>Looking into the future of Customer Success</strong></h3><p>In the past 5 years, we’ve experienced an unbelievable momentum behind customer success. Companies have built organizations and practices around customer success principles.</p><p>At Customer Success Summit 2016, I’ve introduced the book <a href="http://farmdonthunt.com/"><strong>Farm Don’t Hunt</strong></a> — a book that was designed to share the foundational knowledge and best practices for the young practice of customer success. In the upcoming Customer Success Summit 2017, I plan to share my thinking on the roadmap for the future of customer success. We will look into the future of products, teams, customers, and experiences.</p><p>You’ll find the Customer Success Summit inspiring and practical at the same time, and I’m hoping you can join me, the Totango team and many of your peers February 27–28, 2017.</p><p>Tickets have gone on sale yesterday and there is a limited promotion of $700/ticket right now. Please visit <a href="http://www.customersuccesssummit.com/">http://www.customersuccesssummit.com</a> to reserve your spot.</p><p>I’m looking forward to seeing you at the summit,</p><p>Cheers,</p><p>Guy</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=41ad6bbb9e08" width="1" height="1" alt=""><hr><p><a href="https://medium.com/farm-dont-hunt/announcing-cssummit17-feb-27-28-41ad6bbb9e08">Announcing #CSSummit17, Feb 27–28</a> was originally published in <a href="https://medium.com/farm-dont-hunt">Farm Don’t Hunt</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>