<?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[The HelpDocs Blog - Medium]]></title>
        <description><![CDATA[Insights on Helping Your Customers Succeed - Medium]]></description>
        <link>https://medium.com/helpdocs?source=rss----951be9c070fc---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The HelpDocs Blog - Medium</title>
            <link>https://medium.com/helpdocs?source=rss----951be9c070fc---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 21:08:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/helpdocs" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Stumbling to CTO: My Journey Becoming a Developer]]></title>
            <link>https://medium.com/helpdocs/stumbling-to-cto-my-journey-becoming-a-developer-fc521dcfa787?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/fc521dcfa787</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[learning-to-code]]></category>
            <category><![CDATA[coding]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Thu, 23 Aug 2018 13:26:10 GMT</pubDate>
            <atom:updated>2018-08-23T13:26:09.988Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yHiiAQDL3LKNPrzwCXlUuw.png" /></figure><p>I’m perched up against a cushion with my legs splayed out on a super soft grey sofa.</p><p>On my desktop I have 5 terminal windows messily scattered around, two Atom code editors lying around, and a pull request yet to merge. A few years ago I wouldn’t have known what any of these meant. What do terminals have to do with atoms? Who’s pulling what?</p><p>Now this is my roosting place. I’m happy switching between windows and tend to warp into code mode, letting my fingers do the tapping writing git commands while my brain thinks about what else needs doing.</p><p>But it’s been a long journey. I never thought of myself as a developer and always wanted to pursue design (luckily they go together pretty nicely).</p><p>I wrote my first line of code at around twelve. Now 13 years later I’m building product here at HelpDocs. Let me explain how it all started and how I got here — eventually.</p><h3>A virtual hotel, some virtual skills</h3><p>As a twelve year old, I (embarrassingly) spent <em>way</em> too much time on <a href="https://www.habbo.com/">Habbo Hotel</a>, a pixelated world. I used to run home from school to chat with online friends and place pixelated furniture in a fake room.</p><p>Habbo was (and still is) a sort of public chatroom for teenagers to chat, waste money buying pixelated furniture, and generally explore others’ rooms. Although I suspect they aren’t <em>all</em> under 40 years old. ☹️</p><p>One of the strangest things about Habbo was its loyal fanbase. From prepubescent DJs playing queued up songs to hundreds of fansites, us “guests” in the virtual pixelated hotel took things pretty seriously. It was on one of these fansites that I wrote my first line of HTML.</p><p>Inside a table with fake airport timings. Yep, you read that right.</p><p>I was honoured with the task of updating these regularly for our incoming passengers (i.e. people entering the room and going past a set of virtual furniture).</p><p>Although this was a strange way to enter the world of development, helping out with fansites did give me some insight into how websites were set up, maintained, and built — back then, anyway (wow, I feel so old).</p><p>I learnt how you had to buy a server from a hosting company, you made websites with Dreamweaver, and you hosted radio using Winamp. All in the pursuit of being popular on Habbo.</p><p>While I learnt all this, the furthest I managed to get was change a dog’s color purple using HEX codes, DJ for literally tens of people while altering my voice virtually to make me sounds less squeaky, and create a site of iframes.</p><h3>“I can’t be a developer”</h3><p>Fast forward 10 years and at the ripe age of 23 I’d barely touched code since my teen years. I’d followed the design route creating pixel art and vector illustrations in my spare time rather than focusing on development.</p><p>So when Jake (my awesome co-founder) suggested I could become a developer, I immediately scoffed. “What, me?!”.</p><p>We’d already founded a few startups together and I felt bewildered that he suggest I change paths. Besides, his development ability was great and mine was nonexistent. Though looking back, my marketing skill was pretty much on the same level, I found it preposterous.</p><p>I’d failed miserably at maths. I was awful at problem solving. I just didn’t have the brain for <em>that</em>. But he continued. “Yeah, why not?” he said encouragingly. I listed my reasons above but he persisted. “Yeah, and? You can learn all that along the way”.</p><p>I started my journey on CodeSchool, going through various courses. JavaScript fundamentals, AngularJS, HTML, CSS, jQuery, and Git.</p><p>Then I proceeded to buy a book (Eloquent Javascript — it’s a goodie). Then React and JavaScript on Treehouse. And back to Eloquent Javascript again. And again. And again.</p><p>I’d fallen into a trap I hear many newbies at development do.</p><p>I was so worried about actually writing any code on my own that I’d limited myself to <em>only</em> learning through courses. They’re great and all, but self-directed development is just as important.</p><p>Being in the thick of things, getting annoyed, blaming the compiler, then realizing it’s always your fault. Writing a function from scratch, organizing your folders, and getting a “Hello World!” up on the screen are all frustrating but ultimately rewarding.</p><h3>Practice never makes perfect</h3><p>After many failed attempts of “becoming a developer”, I’ve come to realize that you never truly become one. No matter my skill level, I’ll never think of myself as good enough. I think that speaks true to every position, particularly in a startup that’s constantly trying new things.</p><p>Over the course of HelpDocs my role has changed drastically. I’ve been a salesperson, a marketer, a developer, and a success rep. As we grow it’s time to define each of our roles.</p><p>That’s why I’m excited and terrified to be taking the lead with development as Chief Technical Officer. We’ve come so far with our product and I’m thrilled to help move it forward. There’s some fantastic things in the pipeline I can’t wait to release.</p><p>Let the journey continue! 🚢</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/">The HelpDocs Blog</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc521dcfa787" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/stumbling-to-cto-my-journey-becoming-a-developer-fc521dcfa787">Stumbling to CTO: My Journey Becoming a Developer</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Strategies to Navigate Confused Customers Towards Your Knowledge Base]]></title>
            <link>https://medium.com/helpdocs/strategies-to-navigate-confused-customers-towards-your-knowledge-base-32c35c137b7?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/32c35c137b7</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[knowledge-base]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Thu, 19 Jul 2018 05:04:52 GMT</pubDate>
            <atom:updated>2018-07-19T05:04:51.888Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*R1xap327Q2lVoJlsp66XAw.png" /></figure><p>Releasing a knowledge base to your customers is like a cruise ship on its maiden voyage. Building a ship takes a lot of effort and resources. But if nobody ever gets onboard, it’s been a drain with no reward.</p><p>You’ve spent hours organizing, writing, and publishing articles. It’s makes sense to put a little extra time into making it a success, right? You can’t dock a ship without a port.</p><p>In the end customers and team members will reap the rewards. Customers won’t have to wait around. Your support team will find customers asking less similar questions. It’s a win-win.</p><p>Below I share some strategies you can put in place to help customers find your docs. It’s better to launch your knowledge base with champagne rather than a tumbleweed.</p><h3>Alter your support workflow by mentioning articles</h3><p>Already chatting with customers over live chat, ticketing software, or email? Perfect! By having conversations with existing customers, you can make your knowledge base known.</p><p>If you’re replying to a customer who’s question exists in your knowledge base, add a link. Yep, it’s as simple as that. This does two things:</p><ol><li>It shows them you have a knowledge base to look at in their hour of need</li><li>Gives them more context with the solution they’re looking for</li></ol><p>Let’s say a customer of ours is looking to set up HTML templates. It might not be clear to them how to set this up. Luckily, it’s in our knowledge base.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YpjAYBKZz7_8jspl.png" /></figure><p>In my response, it’s best to write a clear solution <em>first</em>. They didn’t spend the time to get in touch to have a link sent to them and then get brushed off.</p><p>After a clear solution, it’s time to add a little context. More info here and a link should do it. It’s like extra reading. If they need more context they’ll click the link, if they don’t they won’t. They’ll know self-help exists now, though.</p><p>This means they’re more likely to find the solution themselves next time. <strong>More</strong> likely being the operative word. New users and existing customers are unlikely to know your knowledge base exists.</p><p>It’s all about rerouting help traffic from 1-on-1 help to self help.</p><h3>Built into onboarding</h3><p>There’s few places you can make as big an impact for new users as onboarding. It’s the process all new customers will go through, so why not make a point of your support options?</p><p>It may seem a little too proactive but pointing out the fact you have a support site and where it lies is super helpful. Pair it with linking to a getting started category and signups will be off to a flying start.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8PzLtw3hEDVZ2u_F.png" /></figure><p>You’ll need build your knowledge base into the user help workflow</p><p>If you’re a task management app, learning how to create tasks and set due dates is going to be essential in success. Instead of waiting for questions to come in, make it known in your onboarding.</p><p>Proactive onboarding exists outside software, too. Check out the example below with Nest’s <a href="https://uxmag.com/articles/unboxing-nest">clever packaging</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*A1QdrI-h3S6QzXb5.jpg" /></figure><p>Nest direct people to help with their packaging</p><p>Before opening it up, it prompts buyers to check if the hardware is compatible with homes in that country. By heading to nest.com/works, it avoids headaches for both customers and support reps. Customers won’t get frustrated it doesn’t wire up while support reps avoid repeat questions and issuing refunds.</p><p>So how can you apply these principles inside your own onboarding?</p><ul><li><strong>Learn what frustrates new users</strong>. Write articles for these and create a getting started category. Show a link at the end of the onboarding prompting them to check it out.</li><li><strong>Think about the unboxing moment</strong>. If you sell a physical product, educate customers about where to find help. This could be on the packaging or in a supplementary manual.</li><li><strong>It’s better customers know where to find help</strong>. Show them your options up-front. Otherwise they’ll be in contact right away, all frustrated and impatient.</li></ul><h3>Build it in-app</h3><p>Many products now make it clear where help is available, and these tend to link to a knowledge base. A simple question mark is usually enough to guide users to the right place.</p><p>You’ll want to build an in-app help menu, but the way it acts will depend on your support load.</p><p>Let’s take a look at Dropbox. It has a simple button in the lower right hand corner that links straight to their knowledge base.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/0*g6rCpEx8xBMujaq_.png" /></figure><p>Dropbox highlight help with a simple icon</p><p>To me, that tells me they have a high support load. Why? Because they don’t make a direct contact link obvious. It’ll only appear if you hit the ellipsis button, but even then it suggests their help center.</p><p>If you’re going to make it hard for users to get in touch, you’ll need a thorough knowledge base. If 9/10 times they don’t find what they’re looking for it’ll become irritating. Luckily, Dropbox have well organized, helpful articles. This does take time. If you’re starting a knowledge base from scratch, it’s unlikely you’ll hit bullseye on the first try.</p><p>Inside our app we use our <a href="https://www.helpdocs.io/lighthouse/">Lighthouse</a> (our own widget). Ours is a sort of hybrid. We show relevant articles based on the page the user is on, but contacting us is simple and clear.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*KRipysG7EYXTONl6.png" /></figure><p>We use Lighthouse to steer customers in the right direction</p><p>Building help inside your app is a personal, company-specific thing. It depends on:</p><p><strong>Your customers</strong></p><ul><li>Are they technical?</li><li>What demographic are they?</li><li>Do they get in touch often about the same things?</li></ul><p><strong>Your support team</strong>.</p><ul><li>How big is your support team?</li><li>Do the same tickets come in day in, day out?</li><li>Are you ted around the globe or in the same office?</li></ul><p><strong>Your product</strong>.</p><ul><li>How much are you charging?</li><li>Do you offer white-glove onboarding?</li><li>Is it tricky to set up?</li></ul><p>If you have no idea how users will react, start with a simple help navigation item. Or use a widget that’ll require less technical help to change and iterate.</p><p>Start with something simple. Then see how these affect your knowledge base views and ticket numbers. Adjust and repeat.</p><h3>Get traffic flowing</h3><p>The main difference between a useful knowledge base and a redundant one is whether people use it or not. You spent time and resources getting it set up, so it makes sense to ensure it helps customers succeed.</p><p>If nobody is onboard, is there any point in keeping it updated and trying?</p><p>When responding to support queries, add simple link to an article that answers it. Make sure to let new users know it exists — and where. Keep help scalable by building a system that works for you in your app.</p><p>Have your own strategies in introducing your knowledge base to users? I’d love to hear them in the comments 🤗</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/">The HelpDocs Blog</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=32c35c137b7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/strategies-to-navigate-confused-customers-towards-your-knowledge-base-32c35c137b7">Strategies to Navigate Confused Customers Towards Your Knowledge Base</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How ready2order Scaled Support for Store Owners Across the Globe]]></title>
            <link>https://medium.com/helpdocs/how-ready2order-scaled-support-for-store-owners-across-the-globe-c7f2f52f3edc?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/c7f2f52f3edc</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[customer-stories]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[knowledge-base]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Wed, 04 Jul 2018 12:42:36 GMT</pubDate>
            <atom:updated>2018-07-04T12:42:36.127Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MGyzZUvTku64D5HRr_bKNw.jpeg" /></figure><p>Setting up a new store is a wild, messy, exciting time. Fitting it out, finishing up the last coat of paint, and arranging the big day when you’re finally open for business.</p><p>The thing you’re probably <em>not</em> thinking about is stock management, discounting, order management, and customer profiles. But these all matter just as much — if not more — than the lilac you chose for the reception area.</p><p>This is where <a href="https://medium.com/u/152b97bffc7d">ready2order</a> come in. They provide a platform independent point-of-sale system for small to medium sized companies. This makes it possible for smaller companies to take advantage of the same tools that their bigger brothers use. New store owners, rejoice!</p><h3>Growing company, struggling support</h3><p>As ready2order started to scale and transition from hundreds to thousands of customers, it was starting to become difficult for the team to overlook the downsides of their current knowledge base solution.</p><p>Christoph Schachner, Marketing &amp; SEO Manager, is the person responsible for their knowledge base. After talking with their customer success team it was obvious things just weren’t working out anymore.</p><p>“It was enough while we only had a couple hundred customers, but once we got to thousands of customers, we had to look for a solution that can scale with us” explains Christoph.</p><p>“We had a chaotic knowledge base, where articles were outdated, search queries had to be entered to exactly match the title of the article and building topic clusters plainly said, just wasn’t possible. We had something but it wasn’t ideal for us”.</p><p>After struggling with their current solution, they went looking for something easier to use and better at scaling their support. “A higher support demand and the lack of an easy to use interface then brought us to HelpDocs”.</p><h3>Scaling &amp; restructuring self-serve support</h3><p>After writing, copying, and updating articles the team added a little customization to make things look familiar for customers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OWHJH4IzoD3SIqXu.png" /><figcaption>ready2order’s knowledge base</figcaption></figure><p>The team also connected up Slack to feed in notifications and create articles, Intercom to chat to customers right from their knowledge base, and Google Analytics to keep track of views and popularity.</p><p>“Every new customer requires their own acquisition, activation and the cost associated with the process while existing customers require such process only once per customer” says Christoph. “Since using HelpDocs, our customer success team has managed to demonstrably reduce the number of calls, that just require some basic support. So it is a huge relief for our support team”.</p><p>Now with customers in the thousands and a knowledge base with HelpDocs, the team find it far easier to educate customers about their POS system and how it all fits together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/296/0*3fXKl_tHiIUzsGPG.jpeg" /><figcaption>Christoph Schachner, Marketing &amp; SEO Manager</figcaption></figure><blockquote><em>“Before HelpDocs we answered the same question a couple of times a day. Now we can cut down the working hours and scale our customer success team”.</em></blockquote><p>Switching also changed their customer support practices, making their self-serve support a first class citizen. “We try to communicate our knowledge base to our customers whenever possible”.</p><p>“Be it when they start a conversation with us on Intercom, that we just forward them the link to an article. Or that we make them aware of our knowledge base during support calls. We definitely changed the way we support our customers”.</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/">The HelpDocs Blog</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7f2f52f3edc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/how-ready2order-scaled-support-for-store-owners-across-the-globe-c7f2f52f3edc">How ready2order Scaled Support for Store Owners Across the Globe</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Hotels Have Taught Me About Customer Support]]></title>
            <link>https://medium.com/helpdocs/what-hotels-have-taught-me-about-customer-support-843cec6d5325?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/843cec6d5325</guid>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[hotel]]></category>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[customer-experience]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Tue, 03 Jul 2018 10:03:06 GMT</pubDate>
            <atom:updated>2018-07-03T10:03:06.041Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fT4o261X2Z0Wo0RnxBjncg.png" /></figure><p>When we started building HelpDocs, I had a lot of assumptions about customer support.</p><p>I believed the loudest, angriest customers got all the rewards. I thought doing small favours for customers was a recipe for disaster. And, like most, I grew up with the idea “the customer is always right”. If a customer is unhappy, it’s always our fault.</p><p>Once I started travelling, staying in hotel after hotel, I realised how wrong I was.</p><h3>Loud and Angry Rewards Are Short-Lived</h3><p>I’ve seen many occasions when support staff bent over backwards to keep the most vocal customers happy. Even when that customer was being unreasonable. It happens a lot in hotels. No doubt you’ve experienced it first hand. The angry, middle-aged man with a briefcase, shouting at the reception staff because he’s out of complimentary soap.</p><p>The standard response to a reception stand-off is a freebie. A room upgrade, or a free meal. Some hotel swag, like the more luxurious towels and toiletries they save for their first-class visitors.</p><p>At first glance, as a polite guest, it seems unfair. If only I were angry enough to degrade receptionists, maybe I would get a free meal! But experience these situations enough times, and you might notice a trend.</p><p>After a few times, I’ve realised guests who get upgraded after a bout of obnoxious aggression, pay the price. That price is less-than-enthusiastic service. I’m trying hard not to say “bad service” here. Because, in my humble opinion, it is relative to the abuse the staff suffer.</p><p>Of course, it’s only anecdotal. But I’ve observed — from many stays in hotels ranging from “wow, this is incredible” to “welp, at least the floors not mouldy” — the loud, angry, upgraded customer at reception getting the cold shoulder on more than one occasion.</p><p>They’re all-but ignored by staff in the restaurant, at the bar, and by the pool. Their “do-not-disturb” door hanger might disappear in the night, resulting in an unexpected 6 am wake-up call. Or worse, their wake-up call might never come, making them late for whatever they had in store for the day. Ok, so those last two are supposition, but you get the idea.</p><p>The fact is, hotel staff are not stupid. Degrading staff might get a short-term win, but it also gives them a “get out of jail free” card. It alleviates the pressure for them to offer good service for the rest of the stay. After all, they already know they’ve got a bad review. Best case scenario, the staff keep the guest at arm’s length so as not to cause further offence.</p><h3>Small Favours Can Boost Loyalty</h3><p>I used to think discounts and freebies cheapen your product. It’s rare they would guarantee customers remain happy. Everyone wants a freebie, and once you bend to the pressure you set expectations. If you stop, you lose the business altogether. All because of a small favour.</p><p>Well, that’s not true at all. The truth is, small, unexpected surprises can make a heap of difference to customer opinion.</p><p>It doesn’t have to be a massive thing. You don’t have to upgrade a customer’s plan or give them a huge discount. It could just be a feature they need or bumping a few limitations without charging extra.</p><p>I remember when we were travelling around Vietnam, we’d planned a stop off in Ho Chi Minh. We were staying at the Renaissance, but for some reason, there was an issue with our booking and we ended up having to book the worst room.</p><p>As nomads, we stay in one location for a few weeks at a time, so weren’t too pleased with the accommodation. But, I figured, that’s life.</p><p>Out of nowhere, the hotel upgraded me to a top executive room, on a club floor, with the lounge included. The appreciated my situation. They knew I had booked for a long time and the room I was in was not great for extended stays. Maybe they also knew that lounge access is the single thing that could improve my stay 100%.</p><p>The key is, there was no ticketed reason for the upgrade. I hadn’t complained. They hadn’t done anything wrong that they were making up for. In fact, it was only when I was in the lounge to checking-in that I realised I had a hefty upgrade.</p><p>Now, I have a much higher opinion of the Renaissance brand. In fact, we are staying in a Renaissance hotel right now, I liked it so much.</p><p>When nice customers look for one small thing to make their experience more pleasant, going above and beyond to make them happy buys long-term loyalty. Go the extra mile to make sure a customer knows you’re there for them.</p><p>This was an extreme level of surprise and it had the desired result. They will always be on my list of places to stay as we continue to travel around the world. Your favours don’t have to be lavish gestures like that. Although, I do love my room upgrades. Who doesn’t!</p><h3>Being Personal Means Everything</h3><p>While we were visiting Seoul, our hotel went above and beyond to offer a friendly and personal service. I received a free keychain when I checked in; I returned to my room after a trip to find the staff had left me a pot of rock that spelt “Seoul”; and when I left the hotel, the team wrote a personal message in a card based on our interactions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2VW1ca4gjNby7X1l.jpg" /><figcaption>A small gift left in my room</figcaption></figure><p>These small, insignificant touches make a more personal customer experience. Let’s face it, it feels great when someone remembers you. It feels amazing to know a hotel that deals with hundreds of bookings a day have paid attention.</p><p>Taking the time to remember who the customer is, what they enjoy, or something you remember talking about before can make all the difference. It shows you care about them having a good experience. It means they aren’t just another reservation, another guest, or another number in your billing software.</p><p>And let’s face it, 1-on-1 personal help is scalable. You just need to care enough to do it.</p><h3>Some People Will Try Their Luck</h3><p>Sometimes, it might feel like customers are just out to troll you and your team. To be honest, sometimes they are. There will always be customers who try their luck. There will always be people who want something because they think they can get it. And if they think they can, they will push and push until you break.</p><p>In these circumstances, we’ve found the best thing to do is suggest they find an alternative. We have adopted a no-nonsense approach to service and product fit. We believe the best way to offer good service is to treat customers like real people. Be personal. Chat often, and find ways to reward users. In the rare cases where there are anger and conflict, don’t be afraid to question product and culture fit.</p><p>There will always be customers who are just out to make your team feel bad. Help them move on, and focus more of your attention on the customers who are pleasant.</p><p>Life’s too short not to.</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/">The HelpDocs Blog</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=843cec6d5325" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/what-hotels-have-taught-me-about-customer-support-843cec6d5325">What Hotels Have Taught Me About Customer Support</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Simple Steps to Make Sure First Time Users Have a Great Experience]]></title>
            <link>https://medium.com/helpdocs/simple-steps-to-make-sure-first-time-users-have-a-great-experience-7f3187800fc5?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/7f3187800fc5</guid>
            <category><![CDATA[experience-design]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[customer-success]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 08:47:41 GMT</pubDate>
            <atom:updated>2018-06-28T08:47:40.736Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RnkG04IM1fY32nYFXQBhyA.png" /></figure><p>Landing in a new destination is always a little daunting. How should I get to my hotel? Do I need cash? How should I greet someone? Luckily signs and interactive maps point you in the right direction, and when they fail there’s always someone there to help out.</p><p>Take away the signs, maps, and people and you’re pretty stuffed. Too many signs or people, though, and things start to get head-scratchingly confusing.</p><p>This is why the first experience for a user is so important (aka onboarding). Too little help and there’s a small chance a user will get the hang of things. Too much help gets irritating and makes matters worse.</p><p>So what’s the right balance? And when should you reach out to people? I’ve a lot to learn about making a great first impression, but here’s what I’ve learned in the last few years.</p><h3>Subtle at the start</h3><p>There’s a lot of information out there that suggests bombarding your users with a tutorial to follow is the best way to help them get started. I disagree.</p><p>I, for one, click through tutorials like there’s cake at the end of it (like, really fast). I wonder if anyone reads these things and takes in the information. If there’s one thing I’ve learned by going through a lot of airports recently is that people <em>really</em> don’t like being told what to do.</p><p>Please wait until the seatbelt signs have been turned off? Let’s all stand when the plane parks. You’ll need to take your water out of your bag for security? Let’s take this massive bottle of water through. I could go on, but I’ll spare you.</p><p>As support, product, and tech people we love to think of users as complacent people. Who wouldn’t love to spend 5 minutes learning about our amazing product? Oh, they might not click on this. They totally need to click on this.</p><p>But if people don’t like being told what to do in the real world, the problem is even worse when it comes to being a new user with your product. Let us tap, drag, and mash everything until we know what we’re doing. Or at least, have clicked everything.</p><p>One way to build with this human behavior in mind is to highlight important steps, but in the background.</p><p>An example of this is using placeholders — sometimes called ‘Empty State’. One of my favorite placeholders is Fullstory’s. It gives you useful information without getting in the way of clicking furiously.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*05M6_TjySiR8eETz.jpg" /><figcaption>FullStory empty state (image via <a href="http://nicelydone.club/products/fullstory/empty-state/fullstory-19/">nicelydone</a>)</figcaption></figure><p>If you think about it, there’s around an hour of time where you’re clicking around and getting familiar with the product. It’s then you should reach either through a messenger or through email.</p><h3>Segment based on user type</h3><p>Not every user of your product is the same, so why send them the same stuff?</p><p>If users can have roles in your product, one easy way to give different users the information they might need/want is to segment based on this.</p><p>For example, it’s unlikely someone with the role Editor is going to want to fiddle around with settings, so we send them stuff about writing and editing articles, not customizing their knowledge base.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*16f20T8O6FDnwDLw.png" /></figure><p>Segment by role or user activity</p><p>If you don’t have an easy way to segment based on something like a role, it could be useful to segment based on their usage. If we didn’t have roles, I might segment based on something like activity.</p><p>I know that writers are usually customer support reps or product managers. That information that help me direct the information I show them. For example, tips and tricks about writing and editing docs, customer support, and product management would be useful, whereas technical engineering posts probably aren’t that interesting.</p><p>Just try getting in the users shoes. The mistake most make when setting up onboarding is assuming they have a lot of free time and they’d love to hear from you, so when you do reach out make sure it’s useful at that time and to that person.</p><h3>Point towards your knowledge base</h3><p>I know, it was bound to happen. A knowledge base product harping on about the usefulness of a knowledge base. Predictable, right?</p><p>But <a href="https://www.helpdocs.io/guides/building-a-knowledge-base-from-scratch/">pointing to your knowledge base</a> can save you and your customers a bunch of time and waiting around. If they know self-serve resources exist — and you make them easy and obvious to get to — they’ll likely use them and become happier for it too.</p><p>Having pointers to your knowledge base baked into your live chat, onboarding, support email, and app can help keep customers on the road to succeeding without being limited by timezones and reply times.</p><h3>Adapt and evolve the first experience</h3><p>Once you first set a campaign as live, start segmenting users, adapt the product for subtle hints, and bake your knowledge base into the process, you’ll have no clue whether it’ll go well.</p><p>But as you start talking to users, start getting replies, feedback, and start seeing it affect subscription rates, you’ll get a better idea.</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/">The HelpDocs Blog</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f3187800fc5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/simple-steps-to-make-sure-first-time-users-have-a-great-experience-7f3187800fc5">Simple Steps to Make Sure First Time Users Have a Great Experience</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Helping Real Estate Agents Match Hearts with Homes]]></title>
            <link>https://medium.com/helpdocs/helping-real-estate-agents-match-hearts-with-homes-a4c6f85276f2?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/a4c6f85276f2</guid>
            <category><![CDATA[knowledge-base]]></category>
            <category><![CDATA[real-estate]]></category>
            <category><![CDATA[case-study]]></category>
            <category><![CDATA[customer-stories]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Tue, 19 Jun 2018 10:03:52 GMT</pubDate>
            <atom:updated>2018-06-19T10:03:51.593Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OIi7lsbBeeMf-YRQsc8Wpw.jpeg" /></figure><p>For many buying a home is one of life’s most important and memorable steps.</p><p>Real estate agents are there to help find the perfect pad for you. Whether the clients are a young couple eager to put down a deposit on a first home or a growing family looking to escape the noise and up sticks to the suburbs, matching heart and home is a tough job.</p><p>But real estate agents aren’t always tech savvy. With a shortage of time to put into creating a website that wows, many real estate agents just don’t have the energy to post home details and make them easy to understand.</p><p><a href="https://www.easyagentpro.com/">Easy Agent PRO</a> makes the first step of this journey that little bit easier for real estate agents. It’s no secret more house hunters are skipping the offline hunt in favor of an online search, so by providing design for professional real estate websites the team enable these agents to generate leads online and grow their business without the hassle.</p><p>With a product that allows customers to create a site from scratch, product education is essential. “We can centralize all of our support documentation in one, easy-to-use location and share that at scale with our client base” says Michael Blowers, Head of Sales and Onboarding at the company.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zuBPYisX_E4KTdGT.png" /><figcaption>Easy Agent PRO’s knowledge base</figcaption></figure><p>Prior to switching to HelpDocs Michael and the team were using an alternative knowledge base provider to scale their support and help educate customers on how to use their software. However, they found it difficult to use and maintain their docs on the platform.</p><p>“The software was somewhat difficult to use and maintain for support documentation” explains Michael. “It was also more expensive than we would have liked and was not strictly focused on support documentation functionality”.</p><blockquote><em>HelpDocs is an integral part of our business. It saves labor hours trying to answer every question manually and offers a 24/7 support solution for clients exploring the features and possibilities of our product!</em></blockquote><blockquote><em>— Michael Blowers, Head of Sales and Onboarding</em></blockquote><p>After making the move over they’ve found their knowledge base a breeze to maintain, simple to customize, and best of all their customers are more successful because docs are updated more regularly and they can use analytics to measure their performance. “The metrics are phenomenal, it’s easy to use, the 301 redirect tool is amazing, and it looks great!” says Michael.</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/">The HelpDocs Blog</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a4c6f85276f2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/helping-real-estate-agents-match-hearts-with-homes-a4c6f85276f2">Helping Real Estate Agents Match Hearts with Homes</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</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 Send Prospects to Competitors If We’re Not a Good Fit]]></title>
            <link>https://medium.com/helpdocs/why-we-send-prospects-to-competitors-if-were-not-a-good-fit-c75f7ebd5e70?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/c75f7ebd5e70</guid>
            <category><![CDATA[sales]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[competition]]></category>
            <category><![CDATA[startup-lessons]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Thu, 14 Jun 2018 12:27:26 GMT</pubDate>
            <atom:updated>2018-06-14T12:27:25.891Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K1Q8VFDtoS8cY-Kij5Ck_A.png" /></figure><p>As a customer it can often feel like the person on the other end of the line or more appropriate these days — messenger, doesn’t have your best interests at heart.</p><p>No matter if you’re a good fit for their product or not, you’re going in their funnel and whatever you say, the product is just <em>perfect</em> for your use case. It can almost make getting in touch feel like a pointless task and that perhaps you should skip the debacle and try everything until you find a product that feels right.</p><p>For better or worse, we’ve never been great at sales. There’s no doubt it’s a great way to grow your business and maybe in the future we’ll give it another spin. But to me it seems like sales is a game with many reps trying to squeeze commission out of every prospect.</p><p>Sometimes we get visitors who are looking for something specific. They’ve been thinking about what they need for a while and we show up on their radar. As much as we’d appreciate the extra revenue, we sometimes send visitors to our competitors. Why? Because they’re not a good fit for our product.</p><h3>A better, honest interaction</h3><p>We have pretty interesting conversations with visitors and customers. It’s great to get to know the person behind the screen and understand the problem they’re trying to solve — whether that’s finding the right software or debugging an issue.</p><p>I’d like to think people who speak with us over live chat or email have a better impression of HelpDocs after our conversation. That’s really what we aim for in our support.</p><p>One of the ways we try and make sure this happens is by being honest and open.</p><p>Yes, the point of a business is to make money but isn’t it also to make people happier? Did you create a business to just to make dollars or was it about something more than that? Call me naive but for me, there’s nothing more rewarding than making someone’s day better. If we can do that we’ve done a good job no matter the cost.</p><p>For example, I walked into a Starbucks for the fourth time in Singapore today and the barista remembered I liked a short black filter coffee in a ceramic mug. I was surprised and a smile gleamed across my face. While the coffee chain made a few bucks and the coffee itself was good, it was the fact someone remembered my order that made me really happy.</p><p>The point is if a visitor can understand that actually, you have their best interests at heart, that’ll make them happy no matter if they buy from you or not.</p><h3>We don’t do everything well</h3><p>Right now we’re a great fit for small to medium companies that want to set up a quick, simple, customizable external knowledge base for their customers.</p><p>While we do tick some of the boxes for enterprise and internal knowledge bases, sometimes internal teams ask for tighter controls on permissioning and enterprise prospects ask for certain single sign on providers we don’t yet support.</p><p>So what’s the best thing to do in this situation? It’s easy to over-promise and try to push the visitor into buying your product. Answers like “I’ll talk to the product team about this, shouldn’t take very long” or worse yet “I’ll have to get back to you on that, I’m not sure. You could sign up and take a look” and never get a follow up.</p><p>If something is on our roadmap, we try to give an estimation of when it’ll be done. Like many product people know things get pushed back, delays happen, and sometimes it’s disappointing — nobody’s perfect. So along with an estimation of when it’ll get implemented we provide competitors who already support the feature.</p><p>“Yep, that’s on our roadmap for the next 6 months. You might wanna check out COMPETITOR, I think they have that feature already”.</p><p>If you’ll never do the feature be upfront about that too. There’s nothing like a bit of honesty to gain trust. Plus, it’s just the right thing to do.</p><p>It might seem horrifying to let a prospect know about your competitors, but chances are they’ve had a good look around and you might be able to point them in the right direction.</p><h3>Avoid dreaded churn</h3><p>If you’re a subscription business churn can be a painful part of the job. People cancel because your product just isn’t right for them. It might be that you’ve done a bad job of setting exceptions or they’ve simply grown out of your software.</p><p>So why would you lead innocent prospects into a river that ends with a plummeting waterfall?</p><p>Your team and users invest money, time, and energy into trying to make the product fit their needs. If it was never meant to be that’s just a waste of all three resources.</p><p>You might get a few bucks out of the customer but they’ll churn and be unhappy with their decision. It can also harm their career and reputation in the company. Convincing their team to invest in your product and then having to pull out can have embarrassing consequences and is unlikely to win you a good reputation.</p><p>So be upfront when they ask questions. Does it do the job they want it to do, and if not, will it and by when? Your tool can’t and shouldn’t do everything so be honest to avoid churning customers back out right away.</p><h3>Creating a better landscape</h3><p>If I don’t like being oversold the dream and tricked into trying something that clearly wasn’t right for me, why would I contribute to the system?</p><p>Don’t get me wrong — there are plenty of businesses out there that try to do the right thing by customers and prospects. Unfortunately I think there are many more that don’t.</p><p>I understand why. Managers expect results and these results are usually based on revenue. You can’t exactly measure performance on prospect happiness alone. But perhaps giving up a quick dime or two is better in the long run.</p><p>A bad company reputation is easy to gain but a great one is exceptionally difficult. Just take a look at hotel reviews. Many customers are delighted, but just a few too many bad experiences can cause an overall score to plummet which means less bookings.</p><p>I’d love to leave a good mark on software as a service. Did we make as much revenue as we perhaps could’ve? Maybe not but we did it the way we thought ethical and right.</p><p>Like the golden rule states — treat others how you want to be treated. For us, there’s no better way to do business.</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/">The HelpDocs Blog</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c75f7ebd5e70" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/why-we-send-prospects-to-competitors-if-were-not-a-good-fit-c75f7ebd5e70">Why We Send Prospects to Competitors If We’re Not a Good Fit</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Our First Guide: Building a Knowledge Base from Scratch]]></title>
            <link>https://medium.com/helpdocs/introducing-our-first-guide-building-a-knowledge-base-from-scratch-6a93333cbaf1?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/6a93333cbaf1</guid>
            <category><![CDATA[knowledge-base]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[knowledge-management]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Tue, 12 Jun 2018 10:44:06 GMT</pubDate>
            <atom:updated>2018-06-12T10:44:06.094Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HpRYYdPmBfIQ85hoL38OnQ.png" /></figure><p>It’s easy to leave setting up a knowledge base at the bottom of your to-do list. Or y’know, assign that one to another teammate. No biggie. 🤨</p><p>Like an author getting started on their next novel, writing and organizing a knowledge base can be a daunting, confusing task. Thinking about how to fit everything into neat little buckets of information that everyone can understand could make you break a sweat on your brow.</p><p>Besides, do you even <em>need</em> a knowledge base? Is it too early? What if customers don’t use it? Am I overthinking this?!</p><p>These are all questions we wanted to answer in our first guide: <a href="https://www.helpdocs.io/guides">Building a knowledge base from scratch</a>.</p><p>In it, we’ll show you how to work out if you even need a knowledge base (and if you don’t, what else you can use), how to start creating categories and which ones users might find useful with templates, plus a host of extras like tips on keeping docs updated and using them within your customer support ticketing or live chat system.</p><p>Here’s the full breakdown by chapter:</p><ul><li>Introduction</li><li>The need for self-serve</li><li>The matter of scaling support</li><li>The humble FAQ page</li><li>Transitioning from an FAQ page to knowledge base</li><li>Getting started writing your docs</li><li>Growing and updating your knowledge base</li><li>Increase customer success using your knowledge base</li><li>Final word</li></ul><p>Yes I admit, there’s a little self-promotion in there but what can I say? We try to make the tools our users need the most. If you’re a busy bee and wanna take it with you there’s an <a href="https://www.dropbox.com/s/rlddtki3awt964v/Building%20a%20knowledge%20base%20from%20scratch.epub?dl=1">ePub</a> and <a href="https://www.dropbox.com/s/w061bh7fyd2i2jb/Building%20a%20knowledge%20base%20from%20scratch.pdf?dl=1">PDF</a> version available for download too.</p><p>To start reading head on over to <a href="https://www.helpdocs.io/guides">this page</a>. As always, we’d love your feedback on the guide if you have any questions or comments. Just get in touch.</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/"><em>The HelpDocs Blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a93333cbaf1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/introducing-our-first-guide-building-a-knowledge-base-from-scratch-6a93333cbaf1">Introducing Our First Guide: Building a Knowledge Base from Scratch</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Organizing Our First Company Retreat as a Bootstrapped Remote Startup]]></title>
            <link>https://medium.com/helpdocs/organizing-our-first-company-retreat-as-a-bootstrapped-remote-startup-3d2497d04e64?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/3d2497d04e64</guid>
            <category><![CDATA[travel]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[retreats]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Thu, 07 Jun 2018 09:35:24 GMT</pubDate>
            <atom:updated>2018-06-07T09:36:18.800Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KqsAATQJ7U00DRaROzlkMA.png" /></figure><p>For us the benefits of being a remote company are obvious. You can work when and where you’re most comfortable, you’re able to travel or spend time with family, and you can <a href="https://open.buffer.com/state-remote-work-2018/#benefits">skip the office politics</a>.</p><p>But despite software making it easier than ever to feel connected while being thousands of miles away from one another, it’s always nice to get some face-to-face time. Striking up random conversations about different topics just doesn’t happen as spontaneously over Slack, and getting to know one another a little better is always helpful.</p><p>That’s why we made it a priority to set up our first company retreat when we hired our first (and awesome) engineer Phil.</p><p>Here’s how I put it all together earlier this year.</p><h3>Getting the team together</h3><p>It seemed like good timing to get together at the start of the year to organize our product roadmap. We’ve got a ton planned and it’s good to get everyone together face-to-face.</p><p>So, deciding on a location wasn’t too difficult. It had to be in Europe since low-cost airlines make it <em>super</em> affordable to travel around. And as you might’ve heard, British people hate the cold weather, so Northern Europe just wasn’t an option. We had to escape the winter chills.</p><p>That left the southern parts of Europe. The South of France, Portugal, Italy, and Croatia. Not too shabby.</p><h3>What kind of accommodation and where?</h3><p>Now that I’d narrowed down the options of countries, it was time to whittle it down further.</p><p>First up was deciding what kind of accommodation to choose. There were three choices in the end: villas, hotels, or apartments. Each had their pros and cons.</p><h3>Villas</h3><p>Turned out villas were a good fit for a company retreat. You sure get a lot of bang for your buck with a villa. There’s a ton of space to work, the furnishing are usually good, and many of them are serviced.</p><p>The big problem with villas is they usually require a car which affects the price somewhat. Driving for groceries is a must, and that’s just not very ideal, fun, or cost-effective. After looking for a couple hours, I found a couple good options, but they were an hour drive away from the airport.</p><p>When I positioned it against living in a city with a major airport, it just didn’t make sense for us.</p><h3>Hotels</h3><p>I briefly looked into getting some rooms in a hotel, but not for long. Hotels in Europe are actually super expensive and coupled with having no way to cook (which means eating out all the time) it would totally blow our budget.</p><p>Not only that, but there’s less room to work. So that was a big no go.</p><h3>Apartments</h3><p>Apartments are kinda in between the two. You can more space than a hotel room, and you can also get serviced apartments so if anything goes wrong, you’ll get help.</p><p>In cities, they’re close to airports which means less travel time and more things to do, places to go, and cafés to work from.</p><p>Because of all of these benefits, it was a no brainer to go for an apartment in a city with a major airport. Now it was time for me to choose where that would be.</p><h3>Searching the internet for accommodation</h3><p>Finding quality accommodation for a good price is tough, so by sharing my experience I hope you’ll find it quicker to find what you’re looking for. Here’s what I tried.</p><h3>Searching for villas</h3><p>To start with I tried Booking.com, a site I regularly check out for booking places. Unfortunately, their selection of villas was pretty dire. The quality was terrible and the prices were pretty outrageous. It’s better for finding hotels and apartments, for sure.</p><p>After that, I went onto Airbnb and <a href="https://www.spain-holiday.com/">spain-holiday</a>. Again, the quality for the price just wasn’t very good. It seemed like there was a split: cheap villas that weren’t appealing or luxury villas that would blow anyone’s budget.</p><p>After sifting through hundreds of listings, I finally just Googled ‘villas in PLACE’. I found a couple independent local villas companies who has way better prices for quality villas.</p><p>Trouble was, they were still too far from the airport which meant renting a car. Another issue was that some of them were simply too large for three people.</p><h3>Searching for hotels</h3><p>The easiest way to search for hotels I found was to use Kayak. If you add your filters and copy and paste the query parameters at the end of the URL, it’ll save you a ton of time.</p><p>Ideally, I was looking for hotels under Hilton, Marriott, Starwood, and Club Carlson as Jake has a card that gives us membership to their loyalty programs. You can earn a ton of points and get things like free Wifi and breakfast, bringing down the cost significantly.</p><p>The problem I faced with hotels was the fact we wanted to go in less than 3 weeks time. The prices seemed to get inflated closer to the time to a ridiculous degree. With all the disadvantages of hotels, I ditched this idea pretty quickly.</p><h3>Searching for apartments</h3><p>Depending on where you search, apartments can be hit or miss. I’ve been to really good ones and some terrible ones. Sites like Airbnb have a lot of selection, but can be overpriced for what you get.</p><p>I tried Googling ‘serviced apartments for CITY’. This worked pretty well. I managed to find several independent companies offering accommodation for a reasonable price.</p><p>In the end, I carried on searching on Airbnb and managed to find a gem. But it turned out the host was actually a company. So I hopped onto their website and found the exact same apartment for less. Booking direct certainly helped me get the price down.</p><h3>Narrowing down the location</h3><p>Now we’d settled on getting an apartment in a city, it was time to narrow down exactly where it would be. There were a few options here.</p><h3>South of France</h3><p>The south of France is a sought-after area and is only around two hours away by plane from London. There’s some lovely cities including Nice known for its lovely boardwalk and climate, Cannes for the film festival, and Montpellier for its wine.</p><p><strong>Pros</strong></p><ul><li><strong>We can <em>kinda</em> speak French</strong>. Jake and I know a little bit of French which is useful when visiting, well, France. Although admittedly, Jake is far better than me at speaking with locals.</li><li><strong>Not far from the UK</strong>. As I mentioned, the South of France isn’t very far from the UK so it won’t take long to travel there. This means our customer support won’t suffer.</li><li><strong>Cheap airfares</strong>. A flight from London to Nice can be had for less than £40 return. Not a bad price at all.</li></ul><p><strong>Cons</strong></p><ul><li><strong>Lack of accommodation choice</strong>. When I looked for apartments there just wasn’t that much choice. It might’ve been because I left it so late (2 weeks before going 🙈).</li><li><strong>Not very warm</strong>. The average temperature in Nice is around 6 ℃ which is still pretty warm compared to the UK, but not warm enough to escape the winter.</li></ul><h3>South of Spain</h3><p>The south of Spain certainly has a tarnished reputation in the UK from tourism, but it’s still a beautiful destination with a great climate. Airports in Alicante and Málaga make it accessible and attractive for European travelers.</p><p><strong>Pros</strong></p><ul><li><strong>Warm climate</strong>. The average temperature in February is 13℃, much better than France and Northern Europe.</li><li><strong>Plenty of accommodation in low season</strong>. Most flock to the south of Spain in the summer when it’s baking. In low season, there’s plenty of choice with apartments as most are empty.</li><li><strong>Cheap airfares</strong>. Again, the airfares from London to Málaga are dirt cheap for how far away it is. You can get a return for £54 — that’s less than a train ticket from Cambridge to London!</li></ul><p><strong>Cons</strong></p><ul><li><strong>Quality of accommodation wasn’t great</strong>. Compared with the other cities I looked at, the accommodation in the South of Spain wasn’t great, even at the high end of our budget.</li><li><strong>Much of the choice required a long drive to/from the airport</strong>. There wasn’t much choice is Málaga or Alicante, so driving further down the coast to other cities made sense. There’s Marbella, Calp, and Benidorm. In the end, this was the problem I was trying to avoid with villas.</li></ul><h3>Portugal</h3><p>Having spent some time in the Algarve (a lovely destination) I knew Portugal was definitely on the list. Lisbon and Porto are both becoming popular for digital nomads for their low cost of living and charming streets.</p><p><strong>Pros</strong></p><ul><li><strong>Quality Accommodation</strong>. Compared to the South of Spain, I found the accommodation to be pretty high quality.</li><li><strong>Cheap airfares</strong>. The airfares from London to Lisbon are also cheap. A little more pricey than the others, but at the right time you can get a ticket for £80 or less.</li></ul><p><strong>Cons</strong></p><ul><li><strong>Accommodation</strong>. While the accommodation was higher quality, the cost of the apartments were higher.</li></ul><h3>The destination of choice</h3><p>In the end I decided on Madrid which is in central Spain. The airfare was a little more than in the cities but the city is an up-and-coming tourist destination which means the accommodation is high quality at lower prices.</p><p>The weather is good and it’s just over 2 hours from the UK. A good rounded choice for our first company retreat.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*m961lVbjiw7XLm-h.png" /></figure><h3>The future of our retreats</h3><p>When we organize another company retreat, I’d do things differently. First of all, I’d hire a freelancer to help me narrow down the choices. As HelpDocs scales I have less time to spend on browsing accommodation.</p><p>I’d also consider places outside Europe as we’ll likely have employees outside of the area. The cost of flights has dropped dramatically and apartments in places like Bangkok and Vietnam is reasonable, offsetting the cost of the flights anyway.</p><p>—</p><p>Organized your own company retreat? Think there was a way I could’ve got a better deal or done a better job of organizing it? I’d love to know if you have any tips in the comments below. :)</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/"><em>The HelpDocs Blog</em></a><em> on March 23, 2018.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d2497d04e64" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/organizing-our-first-company-retreat-as-a-bootstrapped-remote-startup-3d2497d04e64">Organizing Our First Company Retreat as a Bootstrapped Remote Startup</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bolstering Self-Serve Support at Scale with HelpDocs]]></title>
            <link>https://medium.com/helpdocs/drift-helpdocs-customer-stories-264bc7710b3?source=rss----951be9c070fc---4</link>
            <guid isPermaLink="false">https://medium.com/p/264bc7710b3</guid>
            <category><![CDATA[customer-success]]></category>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Jarratt Isted]]></dc:creator>
            <pubDate>Sat, 17 Mar 2018 08:20:56 GMT</pubDate>
            <atom:updated>2018-03-17T08:22:10.736Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XeX4rBgL-v4PP14ed_VKiA.png" /></figure><p><a href="https://medium.com/u/5a3bd01d25cc"><strong>Drift</strong></a><strong> is building a new way for businesses to buy from businesses</strong>. Through the power of intelligent bots and playbooks, over 50,000 businesses are able to direct visitors to book meetings or take other actions when they land on their site.</p><p>From its headquarters in Boston, the company is rapidly expanding its team and recently opened a new office in San Francisco. The team have also announced their second HYPERGROWTH in both Boston and San Francisco — a conference for the Drift community to talk and listen all things sales and marketing.</p><p>With all of that expansion, customer support usually takes a hit, but the team have been using processes, as well as internal and external tools to combat the surge in customers.</p><p>Our customers are reading our documentation rather than asking questions right away, and we’re using HelpDocs internally to onboard new employees!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lR_MjLVi7rhOCiJp.png" /><figcaption>Dan and Sara working at Drift HQ</figcaption></figure><p>Finding the right software that helped them scale their support wasn’t easy. “It wasn’t scalable, and customers wanted to be able to self serve, but couldn’t” says Sara. After previously trying out two other platforms, HelpDocs stuck and has been powering their help documentation for over a year.</p><p>Their favorite feature? The <a href="https://support.helpdocs.io/article/vgOuMo2Szi-setting-up-the-chrome-extension">Chrome extension</a>. “The chrome extension is a HUGE help” says Sara. “HelpDocs is making it easier to find the right article to send to the right people in the easiest way possible”.</p><p>By regularly updating docs, creating helpful videos, and having their own bot connected with their knowledge base, Drift are able to dramatically reduce their support load. “We use HelpDocs to host all of our help documentation regarding our product” says Sara. “We’re in there every week, if not multiple times a week to add and edit docs”.</p><p>Drift are the world’s first and only conversational marketing platform. With the assistance of HelpDocs they’ve been able to scale their support and keep on focusing on one thing: the customer.</p><p>💝<em> Originally published on </em><a href="http://blog.helpdocs.io/"><em>The HelpDocs Blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=264bc7710b3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/helpdocs/drift-helpdocs-customer-stories-264bc7710b3">Bolstering Self-Serve Support at Scale with HelpDocs</a> was originally published in <a href="https://medium.com/helpdocs">The HelpDocs Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>