Last week, I blogged about why “Social Software needs to be a Layer, not a Feature, in the Enterprise.” Now, from an architectural perspective, I’ll riff on what we’ve done to make this a reality. Back in June, we launched Socialtext Connect, a new offering that enables companies to surface critical events from enterprise applications and inject them as streams into our social software platform, where employees across an organization collaborate and take action.
On a high level, we made a strategic bet with Socialtext Connect that an embrace of Open Web standards and REST APIs will make it easier for companies to integrate their traditional systems with social applications.
Here are four reasons we have made bets on the open web in the enterprise.
- REST APIs — We’re developing to where the puck will be, not where it’s been. We’re helping channel the wave of open web standards inside the enterprise firewall. A large number of enterprise IT departments have been rethinking their approach to their enterprise architecture, using REST instead of SOAP – for faster and more agile development cycles, better scalability, and cleaner separation between client/device and server/service. We’ve focused on REST as our API strategy from the very beginning, and we’re doubling down on that bet with Socialtext Connect.
- Bringing architectural patterns, not just Twitter and Facebook, from Web 2.0 to Enterprise 2.0 — We continue to monitor emerging patterns in the consumer Web 2.0 space for relevant value within the enterprise firewall. The most recent of these are Twitter Annotations, Webhooks, and activitystrea.ms – all of which we’re incorporating into Socialtext Connect. Our co-founder, Adina Levin, has also blogged about the power and usefulness of these standards in the enterprise.
- To escape application silos, the Social Layer needs to be usable by non-users of applications — Ease of use remains key – application streams and App Bots are designed to facilitate productive, context-based conversation around reports, events, and exceptions in the underlying application, by injecting these into what was previously only a channel for conversation between people. AppBots aren’t just persona that “tweet” – they are interactive agents that can respond to queries and drilldowns by users – all of which contributes rich context to the overall conversation about a specific event or exception. This video can highlight what I mean.
- We’re trying to straddle and connect the applications and social worlds without binding you to either — With regards to integration and architecture, we take a different approach that our competitors in the Enterprise 2.0 world. Some believe that social technology should be an add-on feature to their departmental application, and therefore produce a programming model that’s an extension of their application model. Others think social software should be a heavyweight Java container, where you pour your development resources, time and money. Our objective is to enable you to liberate information, events, and transactions from application silos and the user community silos that are captive to them – by liberating your development resources from a monolithic, stack-bound development model.
By embracing open web standards and making social a layer in the enterprise architecture, we’re already seeing how this can play out with our customers. As we shared recently, Hayes Knight, an accounting consultancy in Australia, used Socialtext Connect to integrate their CRM system with Socialtext Signals to make it easier and faster for the company’s accountants to collaborate and answer important customer questions.
“The speed with which we’re answering questions has been cut in half, and is a full 7−8 minutes faster on average,” says CTO Jack Pedzikiewicz, a very active member of our SocialDev community, which shares best practices on Socialtext Connect. “The wonderful thing is, as we capture these great answers inside of Socialtext workspaces, we also cut back on repetition where questions cover the same issue and build best of breed responses and knowledge on key issues of importance. It allows us to serve our customers faster and more consistently.”
We believe Hayes Knight’s success is just the beginning, and look forward to sharing more customer stories in the coming months.
Subscribe to our blog
Subscribe to our newsletter
Watch us on YouTube