Today's guest post comes from Ashley, founder of Nose Graze, a specialty shop for Wordpess themes and plugins.
If you use live chat to talk to your customers (and I hope you do), it's easy to grab visitor information like login name and account email if they're logged into a WordPress account.
Here's how to do it:
April is All Hands Support Month here at Olark, during which we'll be sharing tips and stories on how to bring your entire team closer to your customers.
Chief Marketing Olarker, Sunir Shah, recently took time from the 'hurricane' that is South by Southwest (SXSW) to talk with Tech Cocktail about why we do All Hands Support.
Our JavaScript API documentation has an updated look and feel, with new content that can be updated by any Olarker. We've introduced a single page format with visual guides and useful examples. This means that you can decide, how, when and where to display the chat box on your site, as well as view and update visitor information.
All Hands Support has become a cornerstone of culture at Olark. Every Olark employee does direct customer support on a regular basis. In this video, our founders discuss how the practice began and how it's impacted the growth of Olark to 10,000 customers.
10,000 paying subscribers worldwide are now using Olark to make their customers happier.
San Francisco, CA, February 17, 2015 – Olark live chat (www.olark.com) today announced it is now serving more than 10,000 paying businesses on its worldwide network. This includes businesses such as Acquia, Casper, Front, PagerDuty, Product Hunt, ShippingEasy, WordPress.com, and thousands others who offer instant service, sales and support using Olark to make customers happy.
When Olark passed the 10K customer mark in 2015, my co-founders and I reflected on five years of bootstrapping and building Olark live chat from a hobby to a business. We have lots to be thankful for, but I am most thankful for my awesome and flexible teammates who care about how we work together.
The challenges we took on in 2014 raised tough questions about our organization. What are our most important projects? How do we determine our priorities? How do we find the right teammates to solve a problem? Who makes decisions in a "flat" structure? Should we remain flat?
Olark is the first software company I co-founded. Starting out I really had no idea what to expect. Previously I worked for several years as an early employee at another startup, so I had a fuzzy picture in my head of what I wanted Olark to look like, but I wasn’t sure how to get there or how long it would take.
Now it’s 2015, our team is over 30 people, and we have thousands of customers. People ask me all the time about those early years: how long it took to become profitable, what “typical” revenue growth looks like, or when to make that first hire. Time has really put those first few years into perspective, and as we get set to cross a major customer milestone next week, I thought it’d be helpful to share what those early years were like for us.
Here at Olark, you may have noticed we've implemented a new reporting system, which includes feedback on how visitors feel your operators are doing.
