Echo Blog

Echo serves over 1 billion real-time streams per month on behalf of brands including Discovery Channel, ESPN, Showtime, Sports Illustrated, The Washington Post, Universal Music Group, USA Networks and WWE.

Recent Comments


Subscribe

or Via Email

Delivered by FeedBurner

Search

Also find us on...

CommunityTag Archives:

Initial thoughts on the Synaptic Web ( comments)

As many of you may know, before the Echo team sat down to design and build Echo, we first set about writing down what we all think the present and the future of the Internet looks like. We did this because we believed that if we are going to design a product, you must first know the kind of world in which the product is going to exist.

We called this world view ‘Synaptic Web’.

We published our thoughts on a wiki so that others could learn from our insights and our customers can understand the framework from which we make decisions about Echo.

Since then, due to popular demand, we have continued to give talks about, and write about, the Synaptic Web. We have also encouraged the community to help contribute to the idea so that we can all learn and grow together.

The latest such example is a Blog post I guest posted on Louis Gray‘s blog entitled “Synaptic Web: Real-time is just the beginning“.

Also, Khris Loux’s video from his Defrag Keynote is now posted in the sidebar of the SynapticWeb.org wiki.

I encourage you to check them out so you learn about the kind of world we see, and to better understand the vision for Echo.

JS-Kit videos by our mates at AgMates ( comments)

Our mates at Agmates have kindly made some great videos explaining JS-Kit comments. They are designed for the Agmates community but I wanted to share their great work with you.

Video 1: Register as a commenter

Video 2: Using the comment system

Changing the face of customer service ( comments)

There’s a fantastic post on The Friday Challenge in response to JS-Kit’s pro-active support policy. I want to quote it in it’s entirety because its a wonderful reaction to JS-Kit’s unique support team.

Because of the comments on comment limits in yesterday’s post, JS-Kit’s remarkably proactive customer support folks contacted me, to tell me the per-post limit is going up to 10KB in about two weeks and that permanent links to individual posts in threads are in QA now and coming soon. I’m still slightly stunned by the first part of this, though. They contacted me. This never happens. Don’t these people understand how the software technical support escalation chain traditionally works?

Step 1. Deny that there’s a problem.

Step 2. Admit that the customer may be experiencing what appears to be a problem, but state that your technicians are unable to replicate it.

Step 3. Admit that the customer actually has a problem, but say it’s because they’re using an old version and they need to download and install the latest version. Ideally, sell them the upgrade.

Step 4. Blame the customer’s hardware and tell them they need to upgrade or replace the most expensive part of it.

Step 5. Blame Microsoft.

I’m sure I’ve missed a few steps in the chain of escalation, but this is the gist of it. Any steps you’d add or technical support horror stories you’d like to share?

In the meantime, I’m going to go have another cup of coffee and bask in the wonder of it all. JS-Kit technical supported contacted me, proactively. Wow…

We’re glad to have surprised you Bruce, we look forward to continuing to exceed your expectations.

Be sure to check out the original post here.


© 2012 Jacknyfe Inc. | All Rights Reserved | Privacy Policy