The Golden Rule for encouraging repeat customers - and growing a successful business in SL - is simple: Find a way to keep reminding people that your business exists. Nothing else is more important than this.
How many times have you visited a store in SL, and thought "hey, this place is pretty cool! ... I *must* come back here again!" ... and then, mere hours later, totally forgotten about it? If you're anything like me, that's probably a daily occurrence. My inventory is *full* of landmarks from places which - despite my best intentions at the time - I've never, ever, been back to.
Establishing some kind of communication channel to your keenest customers - the customers who think you have neat stuff, and who would actually *like* a prompt to come back to visit you from time to time - is absolutely fundamental to becoming a big player in SL. I mean ... yeah ... it's good to get a "NEW RELEASES, W00T!!" message out whenever you have new stuff for sale; but beyond that, the very act of sending out a message to people reminds them that "hey, that cool store still exists... I should really go back and check it out again!". Face it: there's a bazillion other places in SL that people could go - you *need* to keep pinging _your_ place on people's radars ... reminding them that you exist; reminding them that they thought enough of your products to consider visiting you again one day.
So, how do you do that?
Well, the most obvious approach is to set up a group. When I first set up business in SL, I also (naively, as it turns out) set up a group that my customers could join, to be notified of updates, offers etc.
Result? The thing flopped ... nobody joined. Despite my limitless self-conviction that my new clothing brand was *the* greatest thing to ever hit the SL club scene, the reality was I had about 6 products, and was selling out of the basement of some sleazy SL club. There was a much lower limit on the number of groups you could join in those days (15? something like that?...) - and nobody in their right mind was going to "waste" a group slot on a small-time operator like me. Turns out that groups can be a very hard sell, until you've become a reasonably big player on the scene. (unless you're pandering to a niche product - but that's another topic for another day)
Also, it's difficult to persuade somebody to actually go through the hassle of opening the search facility ... finding the group ... clicking the join button. Ideally, you need to dumb the process down - turn it into a one-click "impulse" decision. "Click this poster to join our update list" - that kind of thing. That wasn't really possible in days of yore; LSL has never been able to translate object clicks into group subscriptions (though the open-sourcing of the SL client has brought work-arounds - check out Cassini Creation's subscription bot services you're thinking of going down that path!).
Anyway, with these problem in mind, I set out to build myself an "alternative" to group messages; a device that could collate a mailing list for me, and then send out a notecard (or item... or an IM... or anything else I wanted) to everybody on that list, without taking up one of their precious group slots.
This was pretty much my first "real" scripting project in LSL... and the solution that I fashioned was a bit clunky (You couldn't make http calls from LSL in those days, so the system used e-mail for server communication, and most of the collation was actually done by an out-of-world process).
Yep, it was an ugly solution for sure... but it worked, and it solved my immediate problem. People happily clicked on my magic poster, and my mailing list gradually got larger and larger. Every time I sent out a newsletter, the store would fill up with green dots. Green dots begat more green dots, and my customer base expanded... yay! :)
Unfortunately, in recent times (and when I say "recent", I'm dodging the truth ... I guess I mean "during most of 2007") I kind of fell out of the habit of sending those newsletters. There's a couple of reasons for this - but, basically, growing the "Lucky Designs" company was getting pretty much 99% of my attention last year, which meant that there was comparatively little time available to work on new products for LapGirl (and there's a limit to how many times you can send out a newsletter without actually having new products to talk about!!).
Lucky Chairs - on the other hand - are a much bigger deal. They're the kind of "killer app" that you *can* persuade people to sign up to a group for ... so from the Lucky Designs perspective, I didn't really have a driving motive to make the mailing list system work. The other (more fundamental) reason for the lapse was the fact that the PC which handled the out-of-world components of my clunky subscription service went up in smoke, and I never did get around to re-installing the software on a different machine. So, for a while, all those LapGirl subscription requests were just building up in a mailbox ... un-serviced...
And you know what? As it turns out, failing to follow my own "Golden Rule" is probably the single dumbest "business thing" that I've ever done in SL. Over the last couple of weeks, I've started a harder push on promoting the LapGirl business again - including reviving the old mailing list ... and wow! - the tills are humming! For the first time in (longer than I can remember) LapGirl is turning over more cash than Lucky Designs. I really don't know why I ever let things slip so much!
Some considerable pain was involved getting the notification system up and running again - (including manually cutting-and-pasting details from about 400 subscriber emails that had been lingering in a neglected mailbox ... My CTRL-C/CTRL-V muscles are still sore!!) ... but everything is ticking over nicely now. ...That said, there's no denying the fact that - in these days of easy http access - the most sensible decision would probably be to think about retiring the existing system and starting again from scratch.
The more I think about that, the more tempted I am to use Zero Linden's silo back-end as a datastore... Admittedly, that approach would require *much* more hoop-jumping than a MySQL-based solution (I'd need to emulate some SQL-ish index and locking features from first principles, just to make it viable), but would - potentially - make the whole thing a *much* easier sell to third parties (kind of like a "host-it-yourself" alternative to the Subscribe-O-Matic, for the semi-web-savvy user ... "just drop this php onto a web server, and you're good to go!"). God knows I've had plenty of enquiries about buying the system in the past, and I've promised umpteen people that I might make a more polished version of it some time in the future. Maybe it's finally time to come through on that offer? ;)
Watch this space...
Recent Comments