<?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 Bernadette Forward on Medium]]></title>
        <description><![CDATA[Stories by Bernadette Forward on Medium]]></description>
        <link>https://medium.com/@Forward_B?source=rss-a1d16704ba44------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ahVXszKIsyCmbmvZ.png</url>
            <title>Stories by Bernadette Forward on Medium</title>
            <link>https://medium.com/@Forward_B?source=rss-a1d16704ba44------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 21:25:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@Forward_B/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[If the channel is the message, what are you telling your customers?]]></title>
            <link>https://medium.com/adventures-in-startup-customer-success/if-the-channel-is-the-message-what-are-you-telling-your-customers-ceb30bbc1f1f?source=rss-a1d16704ba44------2</link>
            <guid isPermaLink="false">https://medium.com/p/ceb30bbc1f1f</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[messaging]]></category>
            <dc:creator><![CDATA[Bernadette Forward]]></dc:creator>
            <pubDate>Tue, 06 Jun 2017 21:45:18 GMT</pubDate>
            <atom:updated>2017-06-07T16:10:44.683Z</atom:updated>
            <content:encoded><![CDATA[<p>How and when you communicate is as important as what you’re saying; the medium is part of the message. Which begs the question, which channels are best for your message, your customers, and/or your product? We compare some popular channels at your disposal so you can send your message the best way possible.</p><ol><li><strong>In-App notifications</strong></li></ol><p><a href="https://www.linkedin.com/in/bernadetteforward/">Bernadette</a>: In-app notifications are my favorite! I like them simply because your message is received when it is most useful, when your user is in your product. These messages are perfect for onboarding, product announcements, and encouraging users to try features they are overlooking. Messages can be automated and triggered by different page views or actions. It’s effective and scalable but it can require a good bit of planning and iteration to figure out which messages get the results you want. It also requires some development resources to get everything implemented. In-app notifications are a powerful way to speak to your customers when the are most receptive. It’s totally worth the effort.</p><p>Cost to implement (1 being least expensive, 3 being very costly): 2</p><p>Tech resources required (1 minimal tech resources, 3 heavy tech involvement): 2</p><p>Scalable (1 very scalable, 3 resource heavy): 1</p><p><strong>2. Live Chat</strong></p><p><a href="https://www.linkedin.com/in/bettyschung/">Betty:</a> Live chat offers a way to provide <strong><em>immediate assistance</em></strong> to users that may be stuck when using your app. <a href="https://www.forbes.com/sites/steveolenski/2016/08/10/its-alive-why-live-chat-is-so-important-for-brands/#53d1a70753d1"><strong>92% customers feel satisfied when they use the live chat over other channels</strong>, revealed a recent Zendesk study.</a> When we first launched our solution with a client, users had a lot of questions — and were sending a lot of emails to our client, making it seem like our product was rife with issues (quite the contrary — they just wanted to learn more about the platform!). Once we implemented Live Chat, user emails to our clients were cut by more than 80%, and we were able to address issues in a much more timely manner. An additional benefit — users like interacting with a human, in lieu of phone calls.</p><p>Over time, it’s important to review the transcripts and identify common issues to hand off to the product team, and templated answers to speed up the resolution.</p><p>Cost to implement: 1</p><p>Tech resources required: 1.5</p><p>Scalable: 1</p><p><strong>3. Phone</strong></p><p><a href="https://www.linkedin.com/in/bernadetteforward/">Bernadette</a>: Phone often gets a bad rap as disruptive, time-consuming and not particularly scalable. But when it comes to building relationships with your customers, there is no better way to connect. Picking up the phone is the best way to manage a delicate conversation, get customers excited about a new functionality, and understand any remaining questions in your customers in mind. I find that the time-spent in quality conversations during onboarding pay off in the long run. This definitely should not be your sole method of communication but if the email chain starts getting too long or if you don’t know how your email might be read, just give them a call.</p><p>Cost to implement: 1</p><p>Tech resources required: 1</p><p>Scalable: 3</p><p>4. <strong>Instructional videos and/or knowledge base</strong></p><p><a href="https://www.linkedin.com/in/bettyschung/">Betty:</a> Most companies have a knowledge base that users can reference when they have a question. My own personal experience/research — no one reads voluntarily these days, especially not lengthy descriptive how-to texts!</p><p>I do find that it’s helpful to provide links to the knowledge base or to short 1–2 min videos whenever questions are prompted via one of our other support channels. That way, the content is specific to the issue at hand, the answer is readily available, and it cuts down on the back and forth/lengthy explanation.</p><p>I’ve also created (very) simple instructional videos via Keynote. The challenge is keeping the content fresh and updated, particularly if your product is new and there are frequent releases and updates as you get more feedback from your users. To ensure your videos don’t look to amateur, <a href="https://blog.kissmetrics.com/creating-a-explainer-video/"><strong>use these tips from Kissmetrics when writing your script</strong></a><strong> </strong>(no, you can’t just wing it no matter how much you know your product), and make sure your audio and images are crisp!</p><p>Cost to implement: 1.5</p><p>Tech resources required: 1.5</p><p>Scalable: 2</p><p>5. <strong>Webinars (not just for sales!)</strong></p><p><a href="https://www.linkedin.com/in/bernadetteforward/">Bernadette</a>: Webinars are great for communicating complex ideas in a one-to-many format. I’ve used webinars for new feature announcements, especially if it’s major functionality that will require users to change their habits. Webinars are also great ways to position your company as thought leaders and help your customers think outside the box. Webinars aren’t just for marketing and sales, the more engrained your product is in your users’ lives, the stickier your product becomes. When it comes to getting users to adjust their daily workflow or expand their product usage, don’t assume they’re going to read through your email. Seeing is believing.</p><p>Cost to implement: 1.5</p><p>Tech resources required: 1.5</p><p>Scalable: 2</p><p>Word of Caution: There is no one-channel-fits-all. You’re likely already using a combination of channels for different purposes. Whatever channels you choose — make sure that you keep your user’s experience in mind. A few tips:</p><ul><li>Using too many channels or switching different channels too often can make it confusing for your users</li><li>Make sure your language/terminology is consistent across channels, particularly with frequent updates of your product (if it’s new).</li><li>Cross train your team across multiple channels</li></ul><p>What are your favorite channels for supporting your users?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ceb30bbc1f1f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adventures-in-startup-customer-success/if-the-channel-is-the-message-what-are-you-telling-your-customers-ceb30bbc1f1f">If the channel is the message, what are you telling your customers?</a> was originally published in <a href="https://medium.com/adventures-in-startup-customer-success">Adventures in Startup Customer Success</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why aren’t your clients using your product?]]></title>
            <link>https://medium.com/adventures-in-startup-customer-success/why-arent-your-clients-using-your-product-2624b38e8f06?source=rss-a1d16704ba44------2</link>
            <guid isPermaLink="false">https://medium.com/p/2624b38e8f06</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Bernadette Forward]]></dc:creator>
            <pubDate>Tue, 28 Feb 2017 16:03:58 GMT</pubDate>
            <atom:updated>2017-02-28T16:03:58.399Z</atom:updated>
            <content:encoded><![CDATA[<p>Effective tactics for client engagement</p><p>When sales signs a big deal, there’s a rush to allocate resources to the account. There are robust revenue forecasts based on usage. Everyone’s patting each other on the back for bringing on this milestone client and how it could really catapult the business to the next level. Then your client goes silent.</p><p>I’m sure you’ve been through this scenario, and we’ve been there too. Here’s what we think is going on, and more importantly, our recommendations for prevention, triage, and revival.</p><ol><li>The users of your platform weren’t involved until after the deal was done, or there is turnover within the group.</li></ol><p><strong>Betty’s Tactics:</strong> Understanding is key — who are these users, what do they do on the day-to-day, and what benefit would they get from using your product? The last thing you want to be is one more thing these people have to log into and use, and have them resent you for it. If possible, I recommend a face-to-face meeting to get their perspective on how this solution impacts them and brainstorm how you can make it more useful in their day to day operations. The more you know about them, the more you’ll impact their success! A weekly call until trust is developed would help stay top of mind as well.</p><p><strong>Bernadette’s Tactics:</strong> Betty hit the nail on the head — you really need to understand the players and their roles. We recommend bringing the operatives in early, even during the decision-making stage whenever possible. If the end user was not involved in the purchasing decision, your first task is to communicate the value of your product during onboarding. Make sure that the training and setup is appropriate for each user’s role so that it addresses their specific pain points, processes, and responsibilities; otherwise, adoption will suffer. We have usage dashboards that monitor key features. If there’s a dip, reach out. If there is team turnover, onboard again!</p><p>2. Implementation is more resource intensive or complex than expected.</p><p><strong>Betty’s Tactics:</strong> <a href="https://plus.google.com/106746113104441455574">Alex Turnbull</a> from Groove recently wrote, <a href="https://www.groovehq.com/blog/friday-qa-february-03-2017">“most businesses…are far too optimistic in their estimates.”</a> When there are recurring issues that arise with implementations, it’s time to have a sit-down with the internal stakeholders — product, engineering, and anyone else who may be involved. List out the issues and prioritize based on the impact on the client. Make sure the stakeholders understand the issues from the client perspective since they may not have the direct access that you have. Then put together a plan to resolve the top priority issues, and assign a qualified project lead for each issue for accountability. <a href="https://www.groovehq.com/blog/friday-qa-february-03-2017">“Being brutally honest with yourself about how much productive time your team will go a long way in getting better and more accurate at project planning,” </a>says Alex.</p><p><strong>Bernadette’s Tactics:</strong> Set realistic expectations about how long it will take and what’s involved. If there are tasks that need to be completed by your customers, make the process as explicit and simple as possible. We’ve even done setup tasks together with some less tech-savvy users. If integration is being done on your end, keep the lines of communication open at every level. Progress reports are essential and messages should align with your users’ top priorities.</p><p>3. It’s been a few months and clients have yet to see the value promised.</p><p><strong>Betty’s Tactics:</strong> Once the contract is signed, the work starts! The client may not like this part as much, particularly if it takes more time and effort than expected to get the program off the ground (see #2), and the product is complicated or difficult to use.</p><p>Our clients’ success is dependent on their partners using our solution — the more users onboarded, the more value is realized. We figured out that clients need to see results within the first month in order to stay engaged, so we set a milestone in the implementation process where a small set of users got early access to the platform. The initial users loved being the first to participate in a new program, and it usually resulted in positive third party feedback back to our client. After this step, we see an increase in log-ins by our clients because they’re so eager to see user activity, and we have much more productive conversations about growing the program.</p><p><strong>Bernadette’s Tactics: </strong>During onboarding, we set goals with our clients. We set clear targets so that users can see the value our product is bringing them. Once those are set, we create action plans to map out how our customers can get there. It’s essential that we thoroughly explain all product features so there’s no question about how our users are going to reach their goals.</p><p>With this approach, ongoing tracking of these metrics and goals is essential. We’ve built in customer-facing dashboards in product so that users can see value and progress toward their goals. Behind the scenes, we know that certain feature usage is an indicator of success. We keep an eye on these, and reach out proactively if we think that the user may be on track to fall short of their goals.</p><p>More formally, we do quarterly business reviews to track metrics and usage, reevaluate goals, and set new ones.</p><p>Any other tactics we should consider? Would love to hear from you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2624b38e8f06" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adventures-in-startup-customer-success/why-arent-your-clients-using-your-product-2624b38e8f06">Why aren’t your clients using your product?</a> was originally published in <a href="https://medium.com/adventures-in-startup-customer-success">Adventures in Startup Customer Success</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Recipes for Customer Success: Developed for Big Teams, Reworked for Us]]></title>
            <link>https://medium.com/adventures-in-startup-customer-success/4-recipes-for-customer-success-developed-for-big-teams-reworked-for-us-a30bb7a6f013?source=rss-a1d16704ba44------2</link>
            <guid isPermaLink="false">https://medium.com/p/a30bb7a6f013</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-engagement]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Bernadette Forward]]></dc:creator>
            <pubDate>Thu, 27 Oct 2016 01:27:27 GMT</pubDate>
            <atom:updated>2016-10-28T21:49:01.548Z</atom:updated>
            <content:encoded><![CDATA[<p>We’re small but we think big. However, most of the CS advice out there doesn’t quite apply to us yet. Do you ever wonder how you can put some of those tips into practice? Here we’ve reworked tried and true CS tips for our early stage businesses.</p><ol><li><a href="https://medium.com/@ilos_Videos/how-to-rock-communication-with-your-customer-success-team-49740c6f4656#.u83mq4uwx">Clearly define roles and responsibilities</a></li></ol><p><strong>Chances are you are both support and success</strong>. Your clients expect super fast and effective service that they’re used to getting from larger companies, and it’s up to you to bring your team together to ensure things get done amidst all the other priorities. “<strong>I</strong><a href="https://medium.com/@ilos_Videos/how-to-rock-communication-with-your-customer-success-team-49740c6f4656#.htk76guc8"><strong>t’s essential to set up some common workflows so nothing gets lost in the shuffle during critical times</strong></a><strong>,” </strong>— especially if cross-functional teamwork is required to best service your clients. You can get the proactive ball rolling by documenting everything to build your knowledge base, regularly meeting with key team members, and iterating on processes as you learn.</p><p><a href="https://www.linkedin.com/in/bettyschung">Betty</a>: When I first started, our team was cranking on building the awesome software that our clients use today, while I was servicing clients on a legacy system. At first, it was a little chaotic inserting myself into the engineering workflow to get client issues resolved, and it was taking longer than it should. However, through regular daily catchups (sometimes 2x a day!), 2-way sharing of information on client goals and projects/tickets in progress, and verbal/written alignment on who was working on which tasks greatly improved the velocity of addressing client needs.</p><p>2) <a href="https://medium.com/success-hacking/is-your-customer-success-strategy-designed-to-win-3584a824e667#.5366rp5u1">Build to Not Lose</a></p><p>Failure may seem like the opposite of success, but it is a key part of a CS job! You don’t have the luxury of resources and time as you would in a larger company, and you’ll need to fail fast to get answers. Don’t be afraid to try something, even if it’s just a hunch, and be proactive about your clients’ success vs. a fire fighting mentality. <a href="https://medium.com/@toddceby">Todd Eby</a> of @SuccessHacker wrote, <a href="https://medium.com/success-hacking/is-your-customer-success-strategy-designed-to-win-3584a824e667#.7levkzni4">“Most companies …retrofitted [Success] into their operation after they had one too many “Oh sh*t!” moments.”</a> This doesn’t have to be you or your company, even if you were hired for that purpose. <strong>If you see an opportunity, take the initiative to grab it.</strong> The insight and understanding you develop now will provide more data points to make better, more informed decisions for your clients.</p><p><a href="https://www.linkedin.com/in/bettyschung">Betty</a>: I recently seized an opportunity that has since dramatically boosted the results for a client. Nothing was wrong with the current relationship, I just saw an area for improvement. I pitched my idea to the client, and we started small with a test batch of users. While it wasn’t a home run immediately, the learnings were huge. Since then, we’ve had multiple iterations on our initial test, and now the primary focus is on rapid expansion and growth. While one-off fire drills still happen, they get a lot less attention from the client.</p><p>3) Use Customer Success Management Software (sort of)</p><p>You won’t have enough clients or team members to warrant a Customer Success Software at first. But this doesn’t mean you shouldn’t be thinking ahead. Don’t have a complex health score algorithm? You’re not off the hook! <strong>You should still be aware of (or in the process of uncovering) with which behaviors and triggers indicate whether a customer is doing well or ready to churn.</strong></p><p>If you know how to use excel, you have a dashboard! Play around with different usage metrics. Get to know which KPIs are important to your CEO and customers. As leaders, this is an essential precursor to identifying <a href="http://www.gainsight.com/2016/08/26/track-roi-cs-team/">“metrics that show [CS] teams are contributing to our companies’ revenue”</a>.</p><p><a href="https://www.linkedin.com/in/bernadetteforward">Bernadette</a>: In the beginning, I ran around and around trying to figure out which usage metrics indicated a healthy customer. CSM software wouldn’t have helped me at that point. It took quite a few iterations of a monthly report to our customers to land on usage metrics that resonated with our clients and were strong indicators of health. It was an intensive task, but now we know!</p><p>4) <a href="https://medium.com/saas-user-onboarding-resources/bad-fit-customers-a-perfect-illusion-527dcc32e87#.30plwry7r">Understand who your bad fit customers are</a></p><p>In the beginning, you won’t know how to pick your best customers and deals will be made with less-than-perfect fits. Don’t worry, it’s actually a good thing. It takes in depth conversations with your customers in order to understand their “<a href="http://sixteenventures.com/desired-outcome">Desired Outcome</a>”. Customers who don’t ‘fit’ easily require you to stretch yourself and work harder to make it work. This process of understanding the needs and profile of the right customer and use case and help your company define it’s good and bad fits.</p><p><a href="https://www.linkedin.com/in/bernadetteforward">Bernadette</a>: Our onboarding process is so much different than it was when we started a year ago. <strong>We learned the most from accounts that struggled to get up and running.</strong> We thought we knew all the use cases and implementations for our product, but there was more out there. Now in onboarding we ask much more in depth questions, uncover issues that new users aren’t even thinking about, and position ourselves as trusted advisors as we solve our users’ problems. All thanks to our ‘bad fit’ customers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a30bb7a6f013" width="1" height="1" alt=""><hr><p><a href="https://medium.com/adventures-in-startup-customer-success/4-recipes-for-customer-success-developed-for-big-teams-reworked-for-us-a30bb7a6f013">4 Recipes for Customer Success: Developed for Big Teams, Reworked for Us</a> was originally published in <a href="https://medium.com/adventures-in-startup-customer-success">Adventures in Startup Customer Success</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>