The history of Enterprise software is rich with hype, but time and time again has failed to deliver the promise that accompanied all the fanfare. We are reminded of the Charlie Brown cartoon, where Lucy would hold the football for Charlie to kick, and then at the last second would pull it away. That’s how a failed promise feels to many organizations. Being told the next version of something is the answer to all their problems, then, yet again, discovering that it isn’t.

But now, in 2018, everything has finally changed. Now there’s a new word on everyone’s lips, “chatbots”. And this time it’s different. Because chatbots really will change the Enterprise software world forever. This is not a fad, it’s a revolution. And so, in IntraSee fashion, let us count the 10 reasons this revolution will happen.

1. Instead of humans having to learn how to communicate with machines, machines will learn how to communicate with humans.

Chatbot Communication

Figure 1: No training required to interact with a chatbot.

From the dawn of computing time, the first thing humanity had to accept was that machines had to be interacted with in very specific ways. Otherwise they would not know what we wanted them to do. And even then, individual software applications had completely different UI’s. PeopleSoft had a different UI to Oracle, which had a different UI to Salesforce, etc. It all became so confusing to people.

Now we are finally getting closer to the top of the computing self-actualization pyramid, because machines now are capable of understanding humans using a natural conversational UI.

In all our years in the software industry we have never seen a UI create so much joy when we demonstrate its capabilities. Conversational UI via chatbot is what the world has been waiting for (even if the world didn’t know it until now).

2. Introducing: Zero navigation.

Chatbot Flow

Figure 2: No navigational menus needed. The chatbot escorts you to where you need to be.

With chatbots, we are now entering a navigation-less world. The tyranny of drop down menus and multi-click access is now behind us. Now you no longer need to grapple with finding what you need; you just tell the chatbot what you want to do and it will escort you through the entire process.

3. One UI to rule them all, and in the chatbot bind them.

One UI: Chatbot

Figure 3: One UI for all your Cloud and on-premise systems.

Every single organization that we know of has a multitude of on-premise and Cloud systems that the people in their organization need to access daily. And, of course, each one of them has its own UI and is often built on different technology stacks.

The beauty of chatbots is that you will now be able to interact with your entire Enterprise via a single unified UI. A conversational UI. Now, everything will look the same and act the same, and will be easy to use because it won’t require any training. Just the ability to type a sentence. Or speak to it.

4. Guided human-like conversations.

Chatbot on Skype Animation

Figure 4: Chatbot wil guide you through a process.

Do you remember the last time you had to do something complicated and important on a web site, and were transferred to a huge form packed with data fields that had to be completed perfectly… or else! Yes, it wasn’t a good feeling. Chances are that one of four things happened:

  • You gritted your teeth, and spent the next hour dutifully filling out every field, resenting every single moment of your wasted time.
  • You flew through the form, filling it out as fast as possible knowing you’d made a ton of mistakes. But, what the heck, that’s someone else’s problem. You shouldn’t have had to do this in the first place.
  • You called up the help desk and eventually got through to someone who helped answer your questions on what to do. But then had to call back an hour later because you got stuck again.
  • Wrote a nasty email to the CIO of your company telling them that they should be ashamed of themselves for letting such awful software be implemented (btw, we know someone who did this, so we aren’t making this up).

If you feel tense just reading this, then that means you’ve been there and we greatly sympathize with you. But, thank goodness, now there is a better way.

The chatbot will guide you through the entire form in a conversational fashion, not letting you make mistakes, and not ending the conversation until the task is successfully completed. If this isn’t Enterprise software heaven, we don’t know what is.

5. Always available.

Chatbot Help

Figure 5: Chatbot is always ready to help.

Chatbots don’t sleep, they don’t take vacation, and they don’t call in sick. And what’s more, one chatbot can handle thousands of requests all at once. They are always available, and always chipper and in a good mood. They are us on our best day. Every day.

6. Faster, more accurate, more consistent, more scalable.

Super Chatbot

Figure 6: Better in so many ways…

Actually, chatbots aren’t us on our best day. They are better than that. They can answer questions, look up data, and complete transactions faster than any human clicking through a myriad of web pages. They also bring a consistency to everything they do. Configured and taught properly, they are the ultimate subject matter experts who always apply best practice solutions on every occasion. And they never get tired or forget things. They are the Superman (or equally fantastic Superwoman) of the software world. Here to save us all from bad data entry, calls to the help desk, wasted time, and low morale.

7. Reduced help desk calls/operational costs.

Better and Cheaper Diagram

Figure 7: Better and cheaper.

Talking of calls to the help desk. The chatbots main reason for being is to let people do what they need to do without making that dreaded call to a live agent. And why is that call such a bad thing?

Two main reasons:

  • Calling the help desk still means the issue takes a long time to be resolved. Chatbots will typically resolve most tier 1 requests in less than a few minutes. Whereas a typical help desk resolution can take many hours.
  • The cost to an organization of that call can be very expensive indeed. The average per-query cost of a human agent is somewhere between $15-$200. For a chatbot it is around $1.

8. Better routing to live agents.

Chatbot Agents

Figure 8: Chatbots can transfer requests to the correct human agent, if they can’t fulfill themselves.

Have you ever spent 20 minutes on hold trying to get in contact with a support agent, then 5 minutes identifying who you are and what your issue is, only to be told that the agent can’t help you and you need to be transferred? It’s a horrible, soul-sucking feeling. Then you have to wait another 20 minutes and start all over again. And even then, there’s no guarantee the next person is the right person.

In the world of the chatbot there will be times that they won’t be able to help you resolve your issue. However, when that happens they will know exactly which department to transfer you to, and will pass on all your information to that person. That in itself is priceless. And if you agree with that statement: please press 1 (that’s supposed to be an IVR joke btw). And yes, people don’t like IVR either.

9. Improve Accessibility.

Chatbot AI

Figure 9: Accessible via voice or text in more languages than your Enterprise systems natively support.

A big problem with most Enterprise systems is that because they are built with different technologies by different vendors, and across different eras of time, they have huge accessibility issues. These could be ADA issues (such as the sight impaired), or just simple device issues (ex: they don’t work well on phones). Also, some vendors support some languages that are spoken in your organization, while others don’t. Rarely do they all support all the languages you’d like them to.

And this is the beauty of a conversational UI. It’s accessible via many channels of communication and in many languages. It won’t matter what your Enterprise system supports, so long as the supports it. This alone will make a huge difference: from a usability perspective, and from a cost perspective (it’s not easy or cheap to add multi-lingual support to many Enterprise software systems).

10. Improve organizational satisfaction.

Satisfied Mobile Users

Figure 10: Chatbots are more often than not the preferred way to interact.

71% of consumers want the ability to solve most customer service issues on their own


65% of consumers feel good about themselves and the company when they can handle an issue without talking to a live person


HR departments today spend 60-70% of their time answering basic questions and fielding requests from employees

This is a win-win for everyone: your internal business organizations who will be freed to do more strategic things for you, and your workforce, who will be happier and more productive.

In summary, our advice to organizations (which echoes Gartner’s), is to start the process of implementing chatbots with a short (12 weeks will suffice) and inexpensive pilot. That way you will be able to see exactly what you would get in a full implementation, and come to an understanding of what it would take in terms of effort and cost.

As we are sure you can imagine, the art will be in the implementation. At IntraSee we believe, and can prove it, that implementing a sophisticated solution can be done in a short period of time with a small amount of people. We have spent ten years building the tools that allow us to plug an advanced chatbot into your organization, and in a way that is simple to maintain. We are the only company in the Enterprise software space that can do this.

Please contact us to learn more.

Contact Us

It was a pleasure to attend a fantastic Gartner conference in Las Vegas last month (December 4-6, 2017). And while there was a chill in the desert air, the team at Gartner brought plenty of heat with terrific keynotes and sessions.

So, what we’d like to do is break down the key messaging that we got from the conference, based on the tracks that we followed, and then we’ll apply what we think is very sound advice to practical steps that can be applied today.

So here we go: Gartner’s key messaging from December 2017.

IT organizations need to learn a new word: “Yes”

Over many years, IT has become known for using the word “no” far more often than the business community would like to hear it. Gartner believes that in the new era of digital disruption, IT needs to transform itself from the party of “no”, to the party of “yes”. Much of what followed during the conference was clear advice on how to go about this transformation.

IT needs to stop building stuff that already exists

In the year 2018, it’s amazing how much has already been built, productized, and is fully supported by one vendor or another (including IntraSee). And most of it is now available for subscription in the Cloud. Gartner’s clear advice for IT is to stop building things that are already built. Ultimately, it’s not just a waste of time and money, it also contributes to IT being primarily focused on being in “maintenance mode”, instead of “innovation mode”. Which, in turn, leads to the word “no” being an automatic response to many requests that would be hugely beneficial to the organization. If IT is always busy reinventing the wheel, then there’s no time available for tasks that really do add value.

IT should embrace disruption and be a force multiplier

By utilizing products, tools, and knowledge that already exists, and not embarking on lengthy DIY projects, IT can accomplish a lot more with the same amount of effort and money. IT should become the catalyst for ensuring things get done the right way and for the right cost. And by doing so, can transform itself to becoming a group that enables differentiation and innovation in the enterprise. This, Gartner says, is a critical path in the evolution of IT.

Plan on multiple chatbot pilots in 2018, but don’t try and build solutions in-house

Gartner strongly advises that building chatbot solutions in-house is not the way to go, as they feel there is enough already built that can be re-used in the Cloud. However, they do feel that now is the right time for organizations to dip their toes into the chatbot pool, and that by the end of 2018 organizations should aim to move some of these pilots into production. You can read more about our own chatbot pilot program.

Stop customizing your Enterprise software

This is a very interesting one, and we totally agree. But one thing we’d add is that the vast majority of customizations are made for UX reasons. And if there’s one place you shouldn’t be making UX changes, it’s in an Enterprise system. We would suggest that a portal/PaaS technology is a better platform for UX changes, and hugely alleviates the need to customize your Enterprise system. This is a great example of spending money to save money. That’s called a win-win!

IT needs to use a different toolbox

For years, many organizations have been building solutions using a vast array of on-premise technologies. Gartner’s advice is to start using more advanced tools that exist in the Cloud. While this may sound easier said than done, 2018 is the year to start doing it. For example, many of our clients have been using PeopleTools as a development platform for a number of years. Well, today there are many options in the Cloud that provide better capabilities, and are also not entering deprecation-status (Note: PeopleSoft has a finite shelf-life).

To that end, we’ve created a simple guide that describes what you have now, and what we think is the equivalent in the Cloud that you should look at adopting instead.  And the great news is that it’s not as daunting as you may think. And, also, is often something you can do prior to moving off PeopleSoft. In fact, we would strongly recommend that many of them are among the first things you should do, as they will better prepare you for life in the Cloud, and the new era of AI and digital disruption.

ON-PREMISE PEOPLETOOLS: Fluid Tiles & Navigation

CLOUD EQUIVALENT: Content & Experience Cloud

There’s a general principle that states that building a UX solution inside your HCM system is a bad idea. The reason being that it is now tied to one HCM solution, and if you change your base HCM solution, you then lose your entire UX investment. Better to create a UX solution that is “portable” across any Enterprise configuration, and can easily adapt to more complex requirements. This principle would include Campus solutions as well.

Also, Fluid Tiles is a PeopleTools technology solution that lacks the flexibility to integrate cleanly with all the other applications in your Enterprise, as well as having a very basic UI. Plus, as this is a legacy solution you’ll soon be moving away from, any investment in this technology will be lost.

Fluid ESS Screenshot

Figure 1: Fluid Tiles ESS Landing Page

WHY IS THE CLOUD VERSION BETTER? It’s far more polished and user friendly, plus it’s a technology solution that’s state of the art, and much easier to maintain. It can also be used with your PeopleSoft solution today, and any Cloud provider too. You also get the advantage of now being on a stack that is getting a lot of investment by Oracle, and can be integrated with their entire Cloud stack, as well as your PeopleSoft stack.

CEC Landing Page Screenshot

Figure 2: Plug & Play Modern Tiles with Oracle’s Content & Experience Cloud

ON-PREMISE PEOPLETOOLS: Approval Workflow Engine (AWE)

CLOUD EQUIVALENT: Oracle Process Cloud

AWE is a PeopleTools solution that has been both complicated and limited in capability for many years. There are better solutions you can use now that can also be used in the Cloud and are not tied to one technology. Plus, like some other PeopleTools features, this one doesn’t migrate to the Cloud either.

AWE Screenshot

Figure 3: PeopleTools AWE

WHY IS THE CLOUD VERSION BETTER? It’s more intuitive, has far more capability, and is used widely within the Oracle PaaS suite. Plus it can be used with your PeopleSoft system today. This means it’s a tool for both the present and the future. What’s also interesting is that not only can Process Cloud be used for transactional workflow (like MSS approvals), it can also be used within the Content & Experience Cloud for content management approvals.

Process Cloud Screenshot

Figure 4: A More Modern Way to Create Workflow

ON-PREMISE PEOPLESOFT: Interaction Hub Content Management System (CMS)

CLOUD EQUIVALENT: Oracle Content & Experience Cloud CMS

We know there’s a lot of organizations using the CMS that comes delivered with the Interaction Hub. It is used to house literally millions of digital assets worldwide. And while it has been very useful in many situations, it does still lack the slick UX that CMS’s come delivered with today. The great news is that moving from one CMS platform to another should be pretty straight forward given the suite of API’s to support this within the Interaction Hub. Plus if the receiving CMS also has a suite of API’s, then the entire process can be automated. As an FYI, at IntraSee we will be offering automated content migration from the Interaction Hub to the Oracle Content & Experience Cloud in 2018.

iHub CMS Screenshot

Figure 5: Interaction HUB CMS

WHY IS THE CLOUD VERSION BETTER? Content Management Systems (CMS) have changed a lot over the years. Not only have the UI’s become much better, but there are even more API’s available if you want to go the “headless CMS” route that is becoming more and more popular today (and with the advent of Chatbots, this is pretty much a requirement these days). This translates to a more flexible way for managing, and publishing, all your digital assets.

CEC CMS Screenshot

Figure 6:Modern Digital Asset Management


CLOUD EQUIVALENT: Visual Builder Cloud Service (VBCS)

While we believe that using delivered Fluid components is a great idea (and many of our clients do this), we wouldn’t recommend building your own Fluid Components. Other than the obvious reason of obsolescence when you retire your PeopleSoft system, there’s also the massive amount of retraining of your IT group that this would entail. Building Fluid components is not a simple process and will require a huge amount of skillset retooling. Why do that in 2018 when there are other options that don’t have such a short shelf-life? As Gartner says, time to use a different toolbox.

Fluid IDE Screenshot

Figure 7: Fluid Component Development

WHY IS THE CLOUD VERSION BETTER? It’s more intuitive, and can be used in a collaborative fashion by teams of business experts and developers, and is used widely within the Oracle PaaS suite. Plus it can be used with your PeopleSoft system today. If you’re looking for a form creation tool that can work with Oracle HCM Cloud, PeopleSoft, and other REST based SaaS systems, then this is it.

ABCS Screenshot

Figure 8: A More Modern and Collaborative Component Builder


CLOUD ALTERNATIVE: Oracle Intelligent Bots, plus other’s

There is no PeopleTools based chatbot framework – hence the N/A. Because of this you may end up waiting multiple years before you do anything with this technology, and that will be way too late. By the year 2020 Chatbot development will surpass mobile development, according to Gartner. Now is the time to put your toe in the water. Your business community undoubtedly wants to do this, so now is the time to say, “Yes”!

HOW TO PILOT/POC A CHATBOT SOLUTION: Thankfully this is something you can do today, regardless of whether you are using PeopleSoft or any other Cloud application.  And what’s more, it can be done in twelve weeks. You’ll get to see how it works in your organization, and how logistically it is implemented and maintained. And you’ll be able to test it in key functional areas, while also getting feedback from multiple business groups. Implementing a chatbot solution can be done efficiently and within a reasonable budget, so try it in a pilot and see for yourself. Make 2018 the year you figure out what works best for you with your first step to AI and chatbot adoption.

We are now entering a new era of digital disruption. Getting your organization ready to thrive in this new reality will be the most important thing you can do today. To find out more, please contact us:

Contact Us

From Charles Darwin’s seminal study, Origin of Species:

“It is not the strongest of the species that survives, nor the most intelligent that survives. It is the one that is most adaptable to change”

– Charles Darwin

This was the core philosophy behind his ground-breaking book, and has been paraphrased often as: adapt or perish.

Without doubt we are now entering a new era of digital disruption. Wherever you look, large organizations are either reinventing themselves (called self-disruption) or they are struggling to survive. Over the years we have seen once great companies that could not adapt fall by the wayside. Remember Blockbuster Video? A power house video rental company that could not adapt to the change to an online video consumption world. Now compare and contrast that with Netflix, a company built on the ability to rent DVD’s online via snail mail! Their world changed too, but they changed ahead of it, and rebuilt their entire business model. Now we see Walmart as a massive online presence, at the same time Amazon is purchasing Whole Foods. Even companies like IBM and GE are showing signs of struggling in this new era. Our world is being turned upside down by technology. And today, AI is leading the charge. In five years the corporate landscape will look very different than it does today.

Meanwhile, the Cloud introduced disruption to the Enterprise software market some ten years ago, and organizations have been moving in droves at an ever-increasing pace. To the extent that companies like Oracle have now reinvented themselves as Cloud providers. Something completely unthinkable just three years ago.

But, even more important than the Cloud, AI has burst to the forefront of our lives. And it’s here to stay.

“Conversational AI-first will supersede ‘cloud-first, mobile-first’ as the most important high-level imperative for the next 10 years”

– Gartner Sept 2016

For those of us that live in the world of Enterprise software, the big questions are: how will the current Enterprise software vendors deal with this disruption? And what should you do, given that you are probably in the process of selecting a new Cloud vendor. Knowing full well that your next decision will have a massive impact on your organization for what may be the most impactful decade in Enterprise software history.

Given all that, we believe that the most important aspect of any Cloud vendor for the next ten years will be its ability to be an enabler for adapting to new disruptions, and by not being a roadblock to innovation. Put simply, does that vendor provide the tools and flexibility needed for you to survive in this new era of digital disruption?

To paraphrase Darwin, the winning Cloud vendor won’t be the biggest, or the one with most features. It will be the one that provides solutions that can most easily be adapted by their clients to allow them to compete in the new era of digital disruption.

Because of this we do have concerns about the following recent announcements by Workday’s CEO, Aneel Bhusri, with regards to opening up access to their platform.

“Right now what we’re seeing is what I’d call small pieces of additional functionality rather than applications that have a larger purpose. So the potential impact is limited. You can bring whatever code you want but, we curate and certify everything that goes into that platform and will continue to do so. We have to because we have a responsibility to ensure that customers remain compliant”.

“We are approaching verticalization and extensions differently to others. We are curating everything and will discuss our plans with partners so that there is a clear line between the areas we will enter and those where our partners will have a free run

– Aneel Bhusri

The bolded comments are the ones we feel are most pertinent. In the new age of digital disruption, agility and innovation are the key requirements of any organization. Without these things, you cannot adapt. Having an Enterprise system that requires curation and certification will be an impediment to your ability to adapt to changing requirements in your world. And one thing we know for sure, is that change is coming, and it’s coming fast.

Our recommendation is to keep your options as flexible as possible. Do not invest any more in deprecated technologies, embrace the Cloud, embrace AI, and use this new era of digital disruption to adapt your Enterprise system to the new needs of tomorrow. And, above all, do not lock yourselves into a technological blind alley.

This is our very firm, high level, opinion of what is important. And, as a UX company, we believe that the next era of Enterprise software will be characterized by how it interacts with employees, managers, students and faculty, and will become less focused on how happy the back office is.

Organizations that focus too much on back office satisfaction will continue to see poor productivity and satisfaction in their organization, as well as high operational costs associated with unnecessarily labor-intensive processes.

The following video shows the kind of things we expect to become the new normal in the Enterprise:

And this really is the core of the issue as we see it. Workday’s reaction to the new era of change is to institute a model of curation and certification. This is very much a response we would expect from a company that is very much focused on back office usage of their software (which is excellent, btw). Unfortunately, what is missing is the recognition that the market is about to dramatically change, and that they need to change with it. Being a cool back office HCM system in the Cloud was what got them to where they are today, but that most certainly won’t work tomorrow. Also, while curation and certification make sense in a back office world, it most certainly doesn’t work once employees, managers, students, and faculty start getting involved. This demographic expects innovation and agility, because that’s what they are seeing everywhere else. And for organizations to see reduced operational costs, and increased organization satisfaction and efficiency, they will need to start giving access to their Enterprise systems in ways they never imagined before.

To illustrate the mindset, the classic measures of SaaS Cloud providers’ success are:

  1. How many issues were created by the client?
  2. How satisfied are the back office staff?
  3. How satisfied do the back office staff think the employees are?

It doesn’t take a rocket scientist to see that these are terrible indicators of success. Low issue counts can be achieved by giving as few people as possible access to the system, and by implementing the solution in the most conservative fashion possible. The theory being that the less people can do, the less things can go wrong.

And measuring customer satisfaction by asking the people who selected the SaaS provider what their opinion is, will always give you a false positive. Of course they like it, they (or their manager) selected it!

And asking the back office staff how happy they think the employees are will never give you an accurate rating. Of course they think everyone loves it.

Ultimately, what Blockbuster discovered (the hard way), was that improving the look of their stores, rearranging the shelves, and changing the rewind policy (remember that?) wasn’t good enough to save them. The things that worked when Blockbuster started were no longer relevant when Blockbuster finally went under. Netflix had it right, they saw the change coming and were agile and innovative enough to adapt.

This is the challenge facing organizations today and for the next decade at least. AI, and chatbots, combined with the Cloud, will transform how we interact with everything. Enterprise systems will no longer be the province of back office professionals, and will absolutely need to be opened up to every single person in the organization. Curation and certification will not be possible. UX innovations and AI will go hand in hand, and will require Cloud vendors to provide the tools (via PaaS), and an open lane (no roadblocks) to allow their customers to take advantage of the massive organizational benefits this will create.

Getting your organization ready to thrive in this new reality will be the most important thing you can start doing today. To find out more, please contact us.

Contact Us

In 2016 AlphaGo was the first computer to defeat a world champion at the ancient Chinese game of Go. Fast forward to October 2017, and the latest iteration, called AlphaGo Zero, crushed the previous version, AlphaGo Master, by 100 games to zero. Thus, making it “arguably the strongest Go player in history”.

That the latest version of something beat the previous version isn’t the shocking part of all this. We’ve become used to things getting better and better. Version 4 of something should be better than version 3. Now, what makes this a fascinating story is how AlphaGo Zero was built, and how it became so powerful. And with that, a very important lesson can be learned for the practical implementation of AI in the Enterprise

To the casual observer, and many experts, one would imagine that AlphaGo Zero had more powerful processors, access to more data, and more time to “learn”. Not so. In fact, the opposite was true. AlphaGo Zero had less processors, was provided with “zero” data (hence the name), and had a tiny amount of time to learn.

AlphaGo Efficiency Graph

Figure 1: Less is more

So, the big question is, how is this possible? There’s a very long answer to this question, but the short answer is that AlphaGo Zero was unencumbered with big data and was allowed to just think for itself. All it needed was the right algorithms.

The creator of AlphaGo Zero was a brilliant group called DeepMind (based out of the UK) that Google acquired for $500 million in 2014. Professor David Silver explains it succinctly:

“Algorithms matter much more than either computing or data available”

– Professor David Silver

This in itself is a breakthrough in AI, and massively impactful to not only future developments in AI, but also in the practical application of AI in organizations today. It also runs counter to the hype machine touted frequently, and should lead organizations to question the validity of being told over and over again, “implement AI, let it mine your data and learn, and in about a year you should start to see value from it”.

Advising people that implementing AI is a year-long process that would take lots of high-priced consultants to implement, with just the hope that it would work, was bad advice out of the gate. AlphaGo Zero has shown that there is a better way. A smarter way.

This whole story reminds us very much of the famous “Search war” that took place back in the late 90’s early 2000’s between Google and Yahoo (remember them)? Yahoo at the time had a massive lead in the Search ad revenue business. Only one problem: it was built using massively inefficient technology that required huge amounts of human interaction. Whereas Google built their search solution by implementing vastly better algorithms that allowed them to completely automate every process. Nobody needs a lesson in how this all turned out. Smart algorithms, automation, and scalable architecture always wins out in the end.

Which brings us to the original point of this blog: how can these lessons be applied to Chatbot implementations in the Enterprise? Let us count the ways…

1. Chatbots can only succeed if they are accompanied by clearly defined processes that define all interaction with your entire enterprise system.

Chatbots themselves are merely a UI. They are not “the brain”, they are a mechanism by which the user can communicate with the brain. Instead of clicking on links, now you can have a conversation with your Enterprise system.

So first, the neural network needs to be in place, and the paths through that network need to be defined. These paths are called processes. And the way to navigate through a process is via a conversation.

At IntraSee we have built, over the past decade, a way to turn your entire Enterprise into a neural map of processes that can be traversed via a browser. Now we have enabled the ability to traverse that same network via conversational AI. AKA Chatbot. The chatbot piece was relatively easy for us, the previous ten years of work was much harder 😊

2. Chatbots should be smart out of the gate. And if they are not, then you have implemented the wrong chatbot solution.

There’s two ways to attack a problem:

A. Lots of people, and no clear plan

B. With smart algorithms, few people, technology automation, and a plan

Option A was how Yahoo tried to win the Search war against Google. Option B was how Google won. At IntraSee we believe that option B is the only tenable way organizations should attempt to implement a chatbot solution.

It is our belief that many vendors in the chatbot market will bring huge teams of consultants to “solve” the problem. These teams will spend years manually building out spaghetti code dialog flows that will be both unmaintainable and unworkable.

It is the IntraSee approach to automate every aspect of a chatbot implementation.

We believe that chatbot implementations should be short projects that provide rapid returns on investment. Increases in customer satisfaction will be immediate, support costs will drop, and organizational efficiency will occur within weeks of the implementation.

3. Greater success will be achieved with one chatbot that understands your entire enterprise. Having multiple chatbots organized by one concierge chatbot is a recipe for failure.

If you click to search, you don’t need to find the right version of Google to get what you want. Google doesn’t fail to return results and suggest that you try a different version of Google to get the right results. Your chatbot shouldn’t do that either.

It’s our belief that many vendors will try to push a multi-chatbot solution, where each chatbot handles its own “silo”. This reminds us of the early days of portals where organizations ended up with hundreds of portals and people had no clue which one to go to. Multiple chatbots would be equally disastrous.

Imagine someone trying to have a conversation with a chatbot where some of what they needed was in Taleo, some was in PeopleSoft, some was in Oracle HCM Cloud, and some was in Oracle’s Content & Experience Cloud. This should be handled by one chatbot that understands each system. You can’t start bouncing people back and forth between chatbots, with each chatbot saying, “sorry, I don’t know the answer to that. Talk to the other chatbot”.

That said, nobody can chatbot enable their entire Enterprise with one chatbot overnight. It will be an incremental process initially, and then will expand rapidly as successes are realized and the correct, scalable, chatbot infrastructure is put in place. But this is clearly the path we believe organizations need to tread. Even Google didn’t index the world overnight. But they did implement the concept of one search engine then used technology-automation and smarter algorithms to eventually make Google the one place everyone went when they needed to find anything. This should be your chatbot goal too.  A chatbot that understands all “intents” within your organization, and can manage conversations across multiple Cloud and on-premise systems.

At IntraSee we know how to do this, and have built a scalable Enterprise-centric solution that will allow you to meet your organization’s goals at a price you can afford. And, more so, it is a solution that will automatically adapt to your changing infrastructure. Such that as you slowly migrate from on-premise solutions (like PeopleSoft) to Cloud hosted solutions (like Oracle HCM Cloud), the solution will adapt to the change, and thus protect your UX investment.

Ultimately, what AlphaGo Zero has taught the world is the importance of the “I” in AI. AI needs to be intelligent out of the box. Chatbot engines are frameworks that can be infused with intelligence from the get-go. That’s what we do at IntraSee. And this is what made AlphaGo Zero a winner.

Please contact us to find out more.

Contact Us