Smart Assistant at the Center of Every Digital Workplace
At Enjo, we are imagining a future where a smart assistant (aka multi purpose Copilot) for the workplace, powered by our conversational AI platform and deep integrations with business applications, is at the center of every digital workplace. Alexa and Google Assistant have shown us the potential of a personal Assistant at home. Imagine a workplace assistant that is able to answer your work-related questions, perform tasks on your behalf, brief you periodically on what needs your attention, recommend follow-up actions at every step and allow you to teach it new skills for your unique needs. The potential of this future is what drives us everyday.
Why Workplace Assistant?
Mundane work problem: According to a recent McKinsey report, employees spend 6 hours a week on repetitive tasks like data collection, approvals and updates. A smart workplace assistant can help automate many of these tasks.
Context switching problem: We are in the era of SaaS apps and organizations across the world are taking a best of breed approach to workplace IT needs. A typical employee is engaging with more than 4+ apps at workplace regularly*. While this is generally proven good for business, 70% knowledge workers say app switching is affecting productivity*. A workplace assistant can alleviate this problem with a unified smart interface to all workplace apps.
Cluttered communication problem: Historically emails became less useful when the admin work to declutter and find actionable information became too expensive. The spectacular growth of business chat platforms and the proliferation of chatbots are bringing with them similar problems to the chat world. Workplace assistant can address the problem with the potential to prioritize and streamline notification from across apps/bots, consolidate fragmented action items across apps/bots, Add context to data from across apps/bots.
Assistant Interfaces
Key challenge with building a resourceful Assistant for the workplace is solving the user interface problem. User needs to be able to interact with the Assistant intuitively without the need to learn a large bot vocabulary. Most chatbots today are command driven peppered with some button driven interactions. Chatbots driven purely by a NLU (Natural Language Understanding) engine have to solve some really hard problems with applying NLU in business use cases. In our experience Beta testing with customers, most were naturally drawn towards the smart button driven interactions complementing the NLU triggers.
NLU driven interaction
Interpreting user intent with natural language is the ideal approach to workplace requests classification. However there are some unique challenges with implementing NLU in the workplace. Typically interactions with a workplace chatbots are ambiguous short sentences that are not fully formed. Users type commands that are many times cryptic and expect quick relevant responses.
A key expectation from an Assistant is to be swifter than the alternative options on getting things done. In that context, it is important for the NLU engine to be trained and tuned to the nuances of typical workplace interactions.
At Enjo we are simulating a lot of these interactions and building training corpus that deliver better accuracies in classification. The key is for the machine's ability to continuously train and retrain with user interactions and connected knowledge systems so it can get better at unscripted interactions. For a secondary level of intelligence we introduce humans in the loop for continuous round the clock grooming. More on this topic in a separate blog.
Eventually the AI engine will be independent, building knowledge and experience from hundreds of thousands of conversations. Until then a smart multi modal interaction will provide for optimal user experience.
Command and Button driven interaction
In a typical command driven interface, the chatbot publishes a list of commands that it understands and requires the user to be familiar with them. Button driven interfaces work similarly in the sense that they both require the user to classify the request and trigger a specific action in the bot.
Commands triggers rely on a conversational followup to clarify and fulfill user requests. Button triggers rely on additional information in a visual popup form for the same. Buttons lend for easier discovery and quicker interactions and are also well suited for multi step workflow interactions.
The interface scaling challenge
Single purpose chatbots work with a finite number of user commands but with a smart Assistant that is multi-skilled, each skillset serves a set of intents. Scaling a command or button driven interaction across skills is not practical. Buttons can help alleviate the discovery problem by anticipating user’s needs based on user type, team, context etc and serve an optimal set of actions in a persistent fashion.
An interface that leverages the power of AI for anticipation and recommendation and fulfills the user’s request with a swift button assisted interaction is one that is well suited to scale.
Personalizing the Assistant
While Smart Assistant will bundle several skills, only a subset of them will be relevant for a user/team. Assistant’s ability to determine and activate the right set of skills and personalize them for the end user is critical to deliver optimal user experience.
Personalization also extends to how users are notified about events that pertain to them directly or to their team. Smart actionable notification delivery mechanism that is efficient in minimizing noise is key component of the Assistant.
Every team is different in the apps they use and in the workflows and processes they adopt. Workplace Assistant needs to be backed by a powerful suite of tools to connect to any business app, define and automate custom workflow and “conversationalize” interactions with the connected apps. A combination of customizable pre-built skills and a powerful skill builder toolkit are essential components of a workplace assistant solution.
Workplace Assistants are good for business
A resourceful smart assistant or Copilot is a win-win for employees and business stakeholders. Employees get to offload some mundane work and spend less time getting work done. Business succeed because a smart assistant
- Improves team productivity and saves a ton of time
- Maximizes ROI on existing app investments
- Instantly upgrades employee workplace experience
The Future
Advent of Smart Assistants in the workplace is inevitable. At Enjo our vision is to place a smart assistant at every workplace. Today we have started with focus on serving support teams using Slack and Teams as their business chat platform.
Our customers are helping us shape the future workplace Copilot, one skill at a time.
Why Workplace Assistant?
Mundane work problem: According to a recent McKinsey report, employees spend 6 hours a week on repetitive tasks like data collection, approvals and updates. A smart workplace assistant can help automate many of these tasks.
Context switching problem: We are in the era of SaaS apps and organizations across the world are taking a best of breed approach to workplace IT needs. A typical employee is engaging with more than 4+ apps at workplace regularly*. While this is generally proven good for business, 70% knowledge workers say app switching is affecting productivity*. A workplace assistant can alleviate this problem with a unified smart interface to all workplace apps.
Cluttered communication problem: Historically emails became less useful when the admin work to declutter and find actionable information became too expensive. The spectacular growth of business chat platforms and the proliferation of chatbots are bringing with them similar problems to the chat world. Workplace assistant can address the problem with the potential to prioritize and streamline notification from across apps/bots, consolidate fragmented action items across apps/bots, Add context to data from across apps/bots.
Assistant Interfaces
Key challenge with building a resourceful Assistant for the workplace is solving the user interface problem. User needs to be able to interact with the Assistant intuitively without the need to learn a large bot vocabulary. Most chatbots today are command driven peppered with some button driven interactions. Chatbots driven purely by a NLU (Natural Language Understanding) engine have to solve some really hard problems with applying NLU in business use cases. In our experience Beta testing with customers, most were naturally drawn towards the smart button driven interactions complementing the NLU triggers.
NLU driven interaction
Interpreting user intent with natural language is the ideal approach to workplace requests classification. However there are some unique challenges with implementing NLU in the workplace. Typically interactions with a workplace chatbots are ambiguous short sentences that are not fully formed. Users type commands that are many times cryptic and expect quick relevant responses.
A key expectation from an Assistant is to be swifter than the alternative options on getting things done. In that context, it is important for the NLU engine to be trained and tuned to the nuances of typical workplace interactions.
At Enjo we are simulating a lot of these interactions and building training corpus that deliver better accuracies in classification. The key is for the machine's ability to continuously train and retrain with user interactions and connected knowledge systems so it can get better at unscripted interactions. For a secondary level of intelligence we introduce humans in the loop for continuous round the clock grooming. More on this topic in a separate blog.
Eventually the AI engine will be independent, building knowledge and experience from hundreds of thousands of conversations. Until then a smart multi modal interaction will provide for optimal user experience.
Command and Button driven interaction
In a typical command driven interface, the chatbot publishes a list of commands that it understands and requires the user to be familiar with them. Button driven interfaces work similarly in the sense that they both require the user to classify the request and trigger a specific action in the bot.
Commands triggers rely on a conversational followup to clarify and fulfill user requests. Button triggers rely on additional information in a visual popup form for the same. Buttons lend for easier discovery and quicker interactions and are also well suited for multi step workflow interactions.
The interface scaling challenge
Single purpose chatbots work with a finite number of user commands but with a smart Assistant that is multi-skilled, each skillset serves a set of intents. Scaling a command or button driven interaction across skills is not practical. Buttons can help alleviate the discovery problem by anticipating user’s needs based on user type, team, context etc and serve an optimal set of actions in a persistent fashion.
An interface that leverages the power of AI for anticipation and recommendation and fulfills the user’s request with a swift button assisted interaction is one that is well suited to scale.
Personalizing the Assistant
While Smart Assistant will bundle several skills, only a subset of them will be relevant for a user/team. Assistant’s ability to determine and activate the right set of skills and personalize them for the end user is critical to deliver optimal user experience.
Personalization also extends to how users are notified about events that pertain to them directly or to their team. Smart actionable notification delivery mechanism that is efficient in minimizing noise is key component of the Assistant.
Every team is different in the apps they use and in the workflows and processes they adopt. Workplace Assistant needs to be backed by a powerful suite of tools to connect to any business app, define and automate custom workflow and “conversationalize” interactions with the connected apps. A combination of customizable pre-built skills and a powerful skill builder toolkit are essential components of a workplace assistant solution.
Workplace Assistants are good for business
A resourceful smart assistant or Copilot is a win-win for employees and business stakeholders. Employees get to offload some mundane work and spend less time getting work done. Business succeed because a smart assistant
- Improves team productivity and saves a ton of time
- Maximizes ROI on existing app investments
- Instantly upgrades employee workplace experience
The Future
Advent of Smart Assistants in the workplace is inevitable. At Enjo our vision is to place a smart assistant at every workplace. Today we have started with focus on serving support teams using Slack and Teams as their business chat platform.
Our customers are helping us shape the future workplace Copilot, one skill at a time.
Accelerate support with Generative AI
Stay Informed and Inspired
How to Automate IT Support with Slack Ticketing System?
Boost IT team productivity with Slack's ticketing system: efficient ticket management, real-time collaboration, and automated knowledge base integration.
Halp vs Enjo: Which Slack Ticketing System is Right for You?
Looking for an efficient Slack ticketing system? In this blog, we will give you an insight into two leading Slack ticketing systems.- Halp and Enjo
Step-by-Step Guide to Setting Up Your Slack Knowledge Base
Slack knowledge base helps employees with their daily tasks by providing instant access to information and streamlining knowledge retrieval.