how it works new


Our focus with CLEVVA has not simply been to offer you powerful build functionality. It has also been to offer you a way to manage the total capture and consumption of advisory logic across many operational systems and application areas, so that you can build many Virtual Advisors without worrying that they will start impacting negatively on each other’s logic. We have also realised that most people are not experienced in building Virtual Advisor logic, and so have really tried to make it easier and easier for people to build powerful VAs using our tried and tested templates and methodologies.

Key areas we have focused on to help make authoring multiple VAs easy for you include:


Allowing you to control the core decision-making components centrally (the data people need to consider; the factors they can apply; the content they can reference; and the entities e.g. clients, objects they can reference).


Allowing non-coding authors to build and maintain required logic, without being dependent on the IT team. This liberates the IT team to focus on supporting technology that enables business to meet their own strategic objectives.


Providing you with powerful roles and permissions that enable you to specify different authoring access and rights, as well as different user access and rights.


Allowing authors to build different VAs in unpublished forms, and only once they have been tested and approved do you make them visible to assigned users. This allows you to have many published and unpublished VAs on the same platform, and means your testing can be managed at the VA level, not the system level (once system testing is done, you can maintain logic changes off your production server).


Offering different authoring teams across the business different ways to apply these components to suit their needs. By this we mean you can allow a team to build a Virtual Sales Advisor referencing your product data in a specific way, while a separate team could build a Virtual Service Advisor referencing the same data in a totally different way (using different words, referenced content, triggers, logic). So when you update your product data, both solutions adjust automatically, yet apply the relevant interpretations in ways that remain relevant to the application they were built for.


Allowing you to deploy different VAs in different ways (or the same VA in multiple ways). For example, you may build a Virtual Technical Advisor that you give your customers access to via your website, but your infield technicians access it via a mobile app. The user’s roles can also offer a different experience, even though both are leveraging a single VA’s logic.


The CLEVVA back-end allows non coders to build the logic that powers the VA’s. This is done through an intuitive, user-friendly interface that makes it easy for authors to import data and build VA’s using the step by step wizards as well as drag and drop functionality. See below for an illustration of how you can build a VA with CLEVVA.


The following key roles are typically involved in the design, build and maintenance of CLEVVA VA’s:

Screen Shot 2016-07-11 at 4.33.33 PM


Backend authors and administrators are provided with a Virtual CLEVVA Advisor, accessible via the backend.

Authors, via Advice, get real time guidance on how to author a wide range of VAs, and how to perform every possible action using the back end (without requiring an expert to show them). So if they every have an authoring question, our aim is to ensure Advice can answer it for them.

See right for an example of how Advice works.


Having been exposed to many different approaches to VA designs, our Solution Architects have compiled a list of recommended methodologies that your teams can leverage when building their VAs. This helps take out a lot of the guess work, and allows you to benefit from what has worked in many other industries and organisations.

Screen Shot 2016-07-11 at 4.36.42 PM


When populating the Virtual Advisor Platform (VAP) with high impact VAs, we have found the best approach is to targeted specific decisions that are currently causing the business pain. These could be specific decisions errors that have a significant business consequence; and/or decisions that require the person to consider many factors and rules that only experienced people tend to be able to get right; and/or decisions that the business requires a record not simply of what was decided but how (for compliance or analytical purposes).

By offering users support that first solves their key pain points, you can then continue building VAs that address the next tier of decision-making errors, releasing VAs as and when they are signed off. This agile approach to building up your VAP ensures that business gets rapid benefits, and that your build teams learn and improve in their VA design approaches, based on real feedback and practical insights.

The approach many of our clients adopt is therefore as follows:

Tap into the growing CLEVVA authoring community

Different authors across different companies are learning new ways to build more and more powerful Virtual Advisors off their CLEVVA platforms. To help everyone benefit from this, CLEVVA has an authoring community Linked In group that looks to share insights with each other. The hope is that we can all help each other learn from design mistakes, as well as from design successes.