blog

archives

How Coinbase Uses Discourse to Educate Customers and Improve SEO

Erlend Sogge Heggen January 12, 2016

As part of our ongoing series of interviews with customers, our latest is with John Mardlin who helps traders, devs and humans use bitcoin at Coinbase — partly through their Discourse-powered community.coinbase.com.

coinbase-logo

What is Coinbase?

Coinbase’s mission is to make bitcoin accessible for normal people. Our core product is a wallet with +3MM users, which enables buying and selling of Bitcoin in over 30 countries (with more coming soon).

We also offer a range of services that are enabling the bitcoin ecosystem to flourish

  • the Coinbase Exchange for active traders and institutional investors
  • a powerful API for easily building bitcoin applications
  • payment processing tools for merchants

The company was started in 2012 by Brian Armstrong and Fred Ehrsam, and has grown to a team of over 120 people. Our investors include the NYSE and A16Z, and we service companies like Overstock, the Wikimedia Foundation and Expedia.

Why did you decide to build a community forum?

We launched our Discourse Community in January 2015. Before the launch, the whole support team pitched in to build out content on the community. The primary impetus, honestly, was to reduce the volume of support requests coming in through email, by making more answers publicly visible. It’s definitely helped with that, and had a lot of other beneficial side effects as well. In particular, the SEO benefits of allowing customers to ask questions and find answers using their own words.

Your community caters to a trending yet complex topic (Bitcoin). How do you deal with common queries & duplicate questions?

I replaced the stock Discourse FAQ with a very thorough, customized FAQ which addresses the questions we see the most. Just like the standard Discourse Guidelines, each heading has an easy to remember ID property for easy linking.

coinbase-discourse-faq

We still get repetitive questions, but I like to think the redundant posts just provide a new set of keywords customers can use to search for their answer.

Speaking of newcomers, your community ranges from first-time bitcoin users all the way down to bitcoin developers. Do you find that there’s some cross-pollination between these usergroups?

Yes. I really love seeing a community member stepping up to help out newcomers with general questions about bitcoin. It really helps us do our job, and it’s a clear signal of their enthusiasm for what we’re doing.

On the other hand, the general customer support topics in the forum can be quite noisy, so I feel the need to protect advanced users from that noise. Ideally, our Developer, Merchant and Exchange categories will feel like communities within our larger community, where these advanced user can discuss shared topics of interest. I really like the way that StackExchange and Reddit approach communities by creating distinct communities within them.

You have a knowledgebase that’s backed by a traditional 1-to-1 support ticket system as well as your community forum. How do you balance the two?

knowledgebase

It took us a while, but I think we’ve managed to strike a good balance between content on the knowledgebase (KB), and content on the forum. Articles in the KB give definitive answers about common product flows, and statements on policies. These KB articles feel more authoritative, and less mutable. This is complimented nicely, by the forum content, which is more conversational, and provides answers to the questions we could never have anticipated. Over time the KB and the Community have become increasingly interconnected. For example: each KB article has a big button requesting feedback on the content. The button links to a corresponding (hidden) forum topic, where customers are encouraged to provide feedback which we use to improve the quality of the article.

kb-link

Another “synergy”: whereas the KB articles are written using our own internal product lexicon, the forum gravitates towards the words that an uninitiated customer would use. So a KB article might be called “payment methods for US customers”, but a customer might be more likely to ask about “How to deposit dollars to a coinbase account”. When the question is asked in those words on the forum, the information becomes more easily discoverable to customers who use similar words for a google search. After a year of amassing content, we’re just starting to see our search engine traffic really take off.

A community built around money is bound to attract malicious actors. What kind of safeguards do you have in place to protect your users?

Our biggest concern is with phishing attempts to gain access to our customer’s Coinbase accounts. To prevent this, we prevent new users from posting links. This isn’t really the ideal new user experience, and it means we have to be really on top of the moderation queue to quickly approve posts by well intentioned new users.

What’s your favourite type of interaction on your forum?

I really enjoy seeing the community members that keep coming back throughout their journey with Coinbase and Bitcoin. Whether they’re developers starting out with our APIs, or just customers new to bitcoin, it’s gratifying to see them returning, asking questions, sharing their projects and offering help to others.

Also, what types of interaction are you hoping to see more of on your forum?

More meta stuff; with people who came because of a shared interest in Coinbase’ products, branching out to topics that aren’t strictly about Coinbase. I want Devs to talk more about their projects, I want traders to share more tips and advice about their strategies, and I want more people to talk about current events in Bitcoin in general.

You’ve opted for Categories as your landing page. Why is that?

We cater to a broad group of distinct user groups who typically come to the forum with a specific question in mind. Developers new to the forum aren’t terribly interested in basic support questions, and Wallet customers aren’t interested in API questions. It seems unlikely that the 15 most recent posts would be relevant to a given user. The categories page is less noisy than latest topics, and enables a new visitor easily reach the kind of content they’re most interested in.

You’re about a year in, so what are your likes, dislikes, and suggestions for Discourse?

Likes

  • Custom badge SQL queries. I just finished a Udacity course in PostrgreSQL, so I’m looking forward to making much more use of them to reward great community members.
  • The UI is awesome for power users. I love working in Markdown, and the shortcut keys both for text editing and navigation are easy to learn and use.
  • The mobile experience is excellent, even for advanced moderator actions.

Dislikes

  • It’s hard for staff to retrieve an email address. We regularly moving a conversation from the forum to email. Every time we do, we have to visit the user’s profile page, and click “show email”. I’d love to see an API function for getting the user’s email address.
  • If a post on a topic can be “unread”, why can’t I mark it unread again after reading it?
  • When I approve a post in the moderator queue, I often want to respond to it right away, unfortunately it disappears and there is no “recently approved posts” list to help find it.

Suggestions

  • A setting to have a topic present all comments as nested. This would be great for enabling an “Ask Me Anything” (AMA) format.
  • Richer badges, and metrics to incentivize participation like Stackoverflow.
  • This one is more of an epic than a feature… but I want more helpdesk like functionality. ie:
    1. Statuses for OPEN (needs action), OK (we’re good here) for topics.
    2. Ability to assign to other staff members.
    3. A queue for tracking new posts where we can quickly apply these statuses on topics like “new”, “open” (ie. needs a response from staff), closed (“our job here is done”) or OK (“we’re not needed here”) statuses. Several features are halfway there, like the “solved” plugin, and tags, and bookmarks, but applying them to this use case is ultimately shoe horning.
    4. A function to allow mods to attach a note to a thread for one another to see.

What is one of your fondest forum memories?

It took me a lot of thought to come up with this, but once I did it was pretty obvious. When TED first started opening up its brand and format to allow for independently organized TEDx events, I was pretty quick to get involved, and start organizing my own event, which eventually grew into TEDxVictoria.

A beautiful, large venue offered me a great price on a space with capacity for 400 people, but TED had a rule that capped attendance at an event at 100 people unless the organizer had attended an official TED event. I posted a question on the organizer’s mailing list looking for advice about how to make the most of a big space with a small audience.

What I got instead was a direct message from a member of TED’s staff offering me free attendance at the TEDGlobal 2011 conference in Edinburgh. I had been quite active on the list before that happened, trying to help out and share ideas with other organizers,… so I guess this is just an extreme example of the unexpected benefits that can be derived from helping others solve problems on the internet.


Thanks to John for taking the time to answer all of our questions. If you’ve ever been curious about Bitcoin or cryptocurriencies, Coinbase is a great place to start!

Notable Replies

  1. I was going to add that I'm still keeping my eye on the topic about warning on external links, e.g. bad guys posting phishing links like this:

    [totally safe and normal link](http://evil-phishing-site.com/bad-link)

    It might be best to warn (if enabled) on TL0 posted links, like so:

  2. cregox says:

    "Improving SEO" must be one of the best and often technically overlooked discourse features.

    For one, www.discourse.org have no mention of "SEO", "engine" or "google" (in this sense) after a quick CMD + F.

    Very good word choices for the title! :slightly_smiling:

  3. I suppose we should be opening new topics to discuss feature requests mentioned in the post?

  4. @john_mardlin incredibly helpful to read about your SEO strategy and results.

    Also, I am intrigued by how you link up your knowledge base and Discourse as that's a balance we're trying to strike as well and we'll probably just move forward, copying your approach with "feedback" buttons on the bottom that link to hidden docs.

    @codinghorror I'd love to see more blog posts about how people use Discourse, this was really helpful.

  5. Go nuts.

    It was a lot of work at first, but we eventually found some tricks to simplifying the process. The key was instead of manually creating a new topic, we made use of the /newtopic URL feature, and built a spreadsheet of all our KB articles:

    Hopefully that's enough to help you reverse engineer the process. :smile:

    To @cregox, SEO was actually more of a pleasant side effect. I typically think of SEO as a marketing tactic, although for us it's almost entirely SEO for people to help themselves. Though really the lines behind customers service and marketing are blurring, and both are good things to have. :chart_with_upwards_trend:

Continue the discussion meta.discourse.org

3 more replies

Participants