<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Towards Continual Learning in Interactive Digital Assistants for Process Automation</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>(Short Paper)</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Praveen Venkateswaran</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vinod Muthusamy</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Yara Rizk</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vatche Isahagian</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>IBM Research AI</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Cambridge</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>Business process automation (BPA) has recently emerged as a multi-billion dollar industry, revolutionizing how businesses manage their processes 1. It develops solutions for automated decision making, data management, and workflow optimization. Many of these solutions leverage digital assistants that can speak the language of business users to make these automations more accessible to non-tech-savvy end-users [1, 2, 3]. In enterprise settings, conversational assistants may be used by teams of people to automate role-based tasks (e.g., in HR, sales, or accounting) and they may want to refine them over time to meet changing business needs. However, existing commercial oferings of digital assistants for process automation from companies like IBM, Microsoft, and UIPath provide a fixed set of automation capabilities. Expanding their functionality is often restricted to domain experts with programming skills. Hence, most end-users are unable to customize or create new process automation capabilities to suit their process management needs. This, in-turn, can result in user frustration and decreased adoption of process automation tools. One possible approach to increase adoption is to empower end-users to intuitively and naturally develop customized and improved automation capabilities from existing automations within these digital assistants by teaching them. Unlike the personal chatbots in [4], digital assistants in business automation settings may be more role-driven. Hence, they would be used by multiple end-users who need to customize them based on company processes, roles and team preferences. In this paper, we posit that the next generation of digital assistants within enterprise settings will be iteratively taught in-situ through intuitive multi-modal interactions dependent on the type of task and skill of the teacher(s). These assistants should be characterized by their ability to continually learn, customizability by end-users with minimal coding expertise, evolution with changing business processes, and generalizability to new process automation tasks by understanding their context. We also discuss some of the challenges of realizing these assistants, focusing on challenges in machine learning, process management, and interactive task learning.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Traditional offline refinement
(separate Use and Build phases)</p>
    </sec>
    <sec id="sec-2">
      <title>2. The Next Generation of Digital Assistants</title>
      <p>The traditional development cycle, in Figure 1 (left), splits the use and build phases of digital
assistants for process automation. Run-time failures encountered by users are logged, and
used by expert developers to eventually build and deploy new versions of the assistants with
improved automation skills. This is a relatively longer process, which due to lack of developer
resources, can result in developers prioritizing the creation of some skills and resolution of
certain issues over others, leaving behind frustrated and disconnected users.</p>
      <p>We instead envision an iterative in-situ refinement of digital assistants, as in Figure 1 (right),
where users are empowered to address automation shortcomings by teaching the assistant new
capabilities. There are three aspects to this approach that difer from the traditional way that
assistants are built. First, failures while using a digital assistant interrupt the user’s task and the
system enters a teaching mode. These failures may occur due to developer or business-defined
guardrails that limit the execution bounds for the assistant, or because of the user explicitly
indicating they were dissatisfied with the assistant’s actions. For example, an assistant used to
book a trip may only know what to do for domestic trips, and a guardrail can be triggered when
a user tries to book an international trip. Second, the user is repairing a specific failure in the
context of the task they were in. Since teaching happens in the context of the failures, it enables
the user to quickly address the issue. We believe this is an easier way for non-developers to
teach and refine the assistant. Third, the same user interacting the assistant is responsible for
teaching the assistant how to handle the failure. This empowers users to evolve and customize
the assistant according to their needs.</p>
      <p>There can be two variants of the iterative in-situ refinement approach: Mode 1 where the
user resumes their task after repairing the failure; and Mode 2 where the user restarts their task
with the new version of the automation. The latter may be appropriate if there have been no
side efects so far, or if the automation can roll back or compensate the steps taken so far.</p>
      <p>
        This in-situ teaching mode needs to be intuitive to non-tech-savvy end-users by leveraging
various input modalities tailored to automation tasks and users’ teaching abilities. For some
tasks or users, it may be easier to “show” the assistant how to perform the task and thus requires
screen recording capabilities. Other tasks may be more easily taught through natural language
instructions. While [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] discuss multi-modality in the context of basic interactions, many of the
concepts can be adapted for our envisioned teaching mode. Furthermore, some users may be
more articulate than others in communicating their automation needs and hence, the assistant
must identify when more iterations with the user are required to fill information gaps.
      </p>
    </sec>
    <sec id="sec-3">
      <title>3. Challenges</title>
      <p>Realizing this next generation of digital assistants with multi-modal, iterative, in-situ
teaching requires addressing various research challenges and integrating multiple technological
advancements before successful deployment is possible.</p>
      <p>
        Metacognition: An important pre-requisite for learning in digital assistants is their ability to
recognize and understand what they do, and do not know [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. End-users may trigger multiple
automation skills, often in specific sequences, making it critical for assistants to identify gaps in
their capabilities. Without this, users may have to repeatedly teach the same skill, or assistants
may try to execute tasks that they are incapable of.
      </p>
      <p>
        Natural language understanding: Understanding the underlying intentions of user inputs is
critical for assistants to execute the right skills or determine when to get more information and
learn. Analyzing inputs in isolation can result in misinterpretation since information may be
provided through diferent modalities, combined across multiple inputs, or be missing altogether.
Prior work [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] limits end-user vocabulary, which is not practical for process automation settings
where users have diferent backgrounds, business needs, and expertise. For instance, the
terminology to automate the same skill can difer between IT support and HR, and novice users
may not articulate their needs as clearly as experts. Improving existing language models (e.g.,
BERT) is required to realise learning-enabled automation assistants, including the ability to
interpret domain specific terminology and process model concepts, learn ontologies, interpret
task signatures and inter-dependencies, etc.
      </p>
      <p>Interactive and informative experience: The teaching process can result in assistants
behaving diferently from user expectations (e.g., learning incorrect skills or misinterpreting key
information), which can prove costly. Hence, it is important to provide informative responses
reflecting the assistant’s understanding at every stage of the teaching process. This includes
“failing gracefully” by defining mechanisms to provide interpretable error messages and seek
appropriate user feedback, when users’ expectations are violated. The vast space of multi-modal
responses makes generating the appropriate response a dificult problem.</p>
      <p>
        Learning new skills: Automation skills vary in complexity, scope, and usage, challenging
assistants to learn new skills. Some may require incrementally updating to existing skills, or
learning a model through user-provided input/output examples, or even synthesising new code
from specifications, making it important to identify what and how to learn. Large teams of
users may teach overlapping skills, requiring assistants to disambiguate. Also, new skills must
be immediately available for use. Analyzing interaction logs to provide capabilities such as
auto-complete, and continually updating skills with changing business and user needs are
important capabilities that can make the assistant’s teaching model more intuitive.
Customization and generalization: Existing assistants often require users to provide
individual inputs to execute each skill and its parameters, incurring significant overhead for repeated
executions of large workflows. The ability to teach customizations such as macros to execute
groups of skills with a single input, pre-filling process parameters, and modifying process
execution should be enabled in assistants using eficient representations (e.g., user profiles).
However, since skills will be used by multiple users with diferent business needs, assistants
should be able to generalize the taught instructions and extrapolate to similar tasks. This will
enable them to perform an ever-increasing number of tasks, require fewer instructions, and
learn continually from subsequent interactions. Furthermore, new skills may be taught to the
assistant by multiple users (with diferent “teaching” abilities) which requires identifying similar
instructions and generalizing from them. While previous work focused on generalization in
specific domains [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], expanding the scope is challenging to achieve and requires identifying
entities, their values and the tasks that they can be incorporated in.
      </p>
      <p>
        Catastrophic forgetting: Teaching digital assistants new tasks runs the risk of conflicts
between new capabilities and old ones or even “forgetting” how to perform previously known
tasks. Existing literature [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] has studied this phenomenon in applications like transfer learning
where neural networks evolved their learnt weights to a point where they were no longer able
to perform previously learned tasks. In essence, the assistant would be replacing previous
knowledge with new knowledge as opposed to combining and augmenting their understanding
of the tasks. This would create a frustrating experience for end-users who may find themselves
re-teaching the system previously learned tasks. Hence, to create a digital assistant that can
truly learn from user interactions, we need to address this problem.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>J.</given-names>
            <surname>Sen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Ozcan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Quamar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Stager</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Mittal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Jammi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Lei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Saha</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Sankaranarayanan</surname>
          </string-name>
          ,
          <article-title>Natural language querying of complex business intelligence queries</article-title>
          ,
          <source>in: Proc. Int. Conf. Management of Data</source>
          ,
          <year>2019</year>
          , pp.
          <fpage>1997</fpage>
          -
          <lpage>2000</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>S.</given-names>
            <surname>Mani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Gantayat</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Aralikatte</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Gupta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Dechu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sankaran</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Khare</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Mitchell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Subramanian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Venkatarangan</surname>
          </string-name>
          ,
          <article-title>Hi, how can i help you?: Automating enterprise it support help desks</article-title>
          ,
          <source>in: Proc. AAAI Conf. Artificial Intelligence</source>
          , volume
          <volume>32</volume>
          ,
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Rizk</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Isahagian</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Boag</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Khazaeni</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Unuvar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Muthusamy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Khalaf</surname>
          </string-name>
          ,
          <article-title>A conversational digital assistant for intelligent process automation</article-title>
          ,
          <source>in: Int. Conf. Business Process Management</source>
          , Springer,
          <year>2020</year>
          , pp.
          <fpage>85</fpage>
          -
          <lpage>100</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>F.</given-names>
            <surname>Daniel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Matera</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Zaccaria</surname>
          </string-name>
          ,
          <string-name>
            <surname>A.</surname>
          </string-name>
          <article-title>Dell'Orto, Toward truly personal chatbots: On the development of custom conversational assistants</article-title>
          ,
          <source>in: Proc. 1st Int. Workshop on Software Engineering for Cognitive Services</source>
          ,
          <year>2018</year>
          , pp.
          <fpage>31</fpage>
          -
          <lpage>36</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>J. O.</given-names>
            <surname>Kephart</surname>
          </string-name>
          <article-title>, Multi-modal agents for business intelligence</article-title>
          ,
          <source>in: Proc. 20th Int. Conf. Autonomous Agents and MultiAgent Systems</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>17</fpage>
          -
          <lpage>22</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>M. T.</given-names>
            <surname>Cox</surname>
          </string-name>
          ,
          <article-title>Metacognition in computation: A selected research review</article-title>
          ,
          <source>Artificial intelligence 169</source>
          (
          <year>2005</year>
          )
          <fpage>104</fpage>
          -
          <lpage>141</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>A.</given-names>
            <surname>Azaria</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Srivastava</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Krishnamurthy</surname>
          </string-name>
          , I. Labutov, T. Mitchell,
          <article-title>An agent for learning new natural language commands</article-title>
          ,
          <source>AAMAS</source>
          <volume>34</volume>
          (
          <year>2020</year>
          )
          <fpage>1</fpage>
          -
          <lpage>27</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>M.</given-names>
            <surname>Nicolescu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mataric</surname>
          </string-name>
          ,
          <article-title>Natural methods for robot task learning: Instructive demonstrations, generalization and practice</article-title>
          ,
          <source>in: AAMAS</source>
          ,
          <year>2003</year>
          , pp.
          <fpage>241</fpage>
          -
          <lpage>248</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>R. M.</given-names>
            <surname>French</surname>
          </string-name>
          ,
          <article-title>Catastrophic forgetting in connectionist networks</article-title>
          ,
          <source>Trends in cognitive sciences 3</source>
          (
          <year>1999</year>
          )
          <fpage>128</fpage>
          -
          <lpage>135</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>