unblu Technical Documentation

There are two ways to get unblu running: In the Cloud or in a Cloud.

This documentation is ostensibly designed for on-premises installations; where you build the unblu Cloud behind your own firewalls, under your complete control... but don't leave just yet if you're a Cloud customer; while you may be spared the pain of large-scale integration you are spared none of the functionality contained therein.

But why should you read these documents? And who are you anyway? And while we’re at it what, exactly, is unblu?

It’s a co-browsing solution? Right?

It is a co-browsing solution but co-browsing is just the tangible layer of a way to Web-enable your customer-facing, and internal, communications. But it’s more than that, it’s a constructor kit for people who want to build knowledge networks that maximize your in-house expertise (although, with unblu, the house is no longer a requirement).

You might picture an unblu implementation as a nervous system, or a neural network but, unlike regular neural networks, which use weightings and iterations to blindly figure out patterns, each node in an unblu network is a human being.

This all sounds complicated, and installing on-premises is certainly complicated compared to, for example, our Cloud solution (which provides equivalent power by simply copying a single snippet of code to magic your Web pages into the raw materials of a communications solution).

But here’s the rub: Once the techie parts are done you get to build knowledge networks that unleash 100% of the potential of every individual who works for you. And that part is not only pretty easy, it can even be fun. Modelling your unblu network is not unlike using a child’s constructor kit. All of the complexities you will face when integrating unblu at the deepest level pay dividends when it’s time to create a system that can capture the needs of your visitors and pair them to the optimum help and advice that you can offer. And that system can be quickly redesigned and refactored as your needs and the desires of your visitors evolve.

So, now we know that co-browsing is the method unblu uses to extract all there is from all you have; who are you and why should you read these documents?

Technical documentation is traditionally designed to enable technical people to do technical things. This has not changed. Your techies need to know how to do techie stuff. However, this documentation should also be read by your leaders, managers, business process designers, in fact, anyone who might contribute. Once the heavy lifting (of creating an unblu Cloud on your own hardware) is done you will be in control of an extremely malleable system, where reconfiguring and redesigning your visitor-engagement strategies can be done without the need for any skills outside of those that you bring to the table.

The introduction to the collaboration server is a good place for everyone to start. It gives a flavour of the kind of close collaboration required within your own teams to get to an optimal solution. Then your technical people might want to look at order of deployment followed by some instructions on setting up the collaboration server.

Another must read for all participants is the introduction to the Agent-Desk. This is the place where everyone in your organization can gain insight into exactly what it all means and why. It is non-technical to the extent that no specialist knowledge or coding is required to understand it. The Agent Desk is the place where you will implement your designs and strategies, as well as engage with visitors, and each other, when it’s all up and running. As you will find out, the hierarchical nature of the design means your ideas can cascade through the entire system. Distance is no longer an issue, nor is scaling users or localization. Settings can be propagated through the whole system then tweaked or reversed according to the finer resolution required by each discipline and culture and service you intend to offer your visitors.

Developers might want to dive right into our JavaScript API or Web API documentation or find out how to install the filter or proxies or to see overviews of various architectures.

Some of these technologies, such as Webhooks or Docker Containers or even the odd blob might be new to you. Concepts such as embedded co-browsing or universal co-browsing are almost certainly unfamiliar to most so we have embedded a glossary into these documents to make it easier to get through sentences strewn with new concepts.

Implementing an unblu on-premises solution is very like regular software development but designing your engagement strategy, by manipulating settings in the Agent Desk, is best performed iteratively by people with seemingly unrelated or disparate skill sets, and can only be properly done in a highly-collaborative setting.

Cloud customers are also invited to peruse these documents, especially the Agent Desk. All of these aforementioned (visitor-engagement) design considerations apply also to our Cloud solution (with the added bonus of becoming aware of how cool it is to do almost everything described here by simply copying a snippet of code to your Web pages).

In conclusion, and before you get started, know that both the unblu Cloud (snippet copy & paste) and on-premises (a big job) carry almost identical feature sets and deliver the same experience. And whether there are internal directives or external regulations that compel you to fabricate your own 'unblu Cloud', or whether you've just copied and pasted a snippet into a Web page, you'll use the same Agent Desk to open and route direct communications between the people who need to be talking to each other; and you'll have access to the same analytical tools that will shape the evolution of your engagement system.

Hot Tip! Whether you use the Cloud solution or an on-premises solution, after you are up and running you still have to configure the properties/settings. With many hundreds of settings to choose from this can seem daunting. But never fear! Have a quick look at this page to get a handle on how to do it.

  • deploycloud
  • deployonprem

results matching ""

    No results matching ""