<!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>Collaborative Business Intelligence Virtual Assistant</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Olga Cherednichenko</string-name>
          <email>olga.cherednichenko@univ-lyon2.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Fahad Muhammad</string-name>
          <email>fahad.muhammad@eric.univ-lyon2.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Artificial Intelligence, Collaborative Business Intelligence</institution>
          ,
          <addr-line>Virtual Assistance, Machine</addr-line>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Univ Lyon</institution>
          ,
          <addr-line>Univ_Lyon 2, UR ERIC - 5 avenue Mendès France, 69676 Bron Cedex</addr-line>
          ,
          <country country="FR">France</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Current business environment requires new methods that incorporate more intelligent technologies and tools capable to provide fast, accurate and reliable information for decision making. This paper deals with data mining applications. It describes the unified business intelligence semantic model, coupled with a data warehouse and collaborative unit to employ data mining technology. The virtual assistant for collaborative business intelligence is suggested.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Learning</p>
    </sec>
    <sec id="sec-2">
      <title>1. Introduction</title>
      <p>Ukraine</p>
      <p>2023 Copyright for this paper by its authors.</p>
    </sec>
    <sec id="sec-3">
      <title>2. Background</title>
      <p>Data exploration is an important component of the BI process, which involves collecting,
identifying, and analyzing data to discover meaningful insights and patterns. The main goal of
data exploration is to identify key business opportunities and challenges that can drive
decision-making and improve business performance.</p>
      <p>The main idea of our research is to model CBI processes in distributed virtual teams via
interaction of user and CBI Virtual Assistant (Fig. 1).</p>
      <p>Results
Command</p>
      <p>Execution
Collect and Keep</p>
      <p>Results</p>
      <p>User
User s Request</p>
      <p>Questions /</p>
      <p>Comments
Request Identification</p>
      <p>Request Classification</p>
      <p>User s Answer
Command
Identification
to interact with data and extract insights, making decision-making processes more efficient and
effective. Natural Language Querying (NLQ) can also make it easier for non-technical users to
access and analyze data.</p>
      <p>The goal of a virtual assistant is to make data exploration more accessible to a wider range
of users and to reduce the time and effort required for data analysis. It is an idea of creating
innovative CAs is to transform the way users interact with data and ML models and to make
data science more accessible to a wider range of users.</p>
    </sec>
    <sec id="sec-4">
      <title>3. The state of the art</title>
      <p>
        Chatbots can be classified into different categories based on their functionalities and the type
of collaboration they facilitate [
        <xref ref-type="bibr" rid="ref4 ref5 ref6">4, 5, 6</xref>
        ]. They can provide insights, recommendations, or
predictions based on the available data. Chatbots can also send notifications and alerts to users
triggered by predefined actions, such as changes in data or anomalies in key metrics.
      </p>
      <p>
        Although a chatbot is a type of conversational agent (CA), not all CAs are chatbots. CA is
a broader term that includes any computer program or system that can engage in natural
language interactions with users [
        <xref ref-type="bibr" rid="ref7 ref8">7, 8</xref>
        ]. CAs can be rule-based or use machine learning (ML)
and natural language processing (NLP) techniques to comprehend and respond to user inputs.
      </p>
      <p>
        Drawing upon a review of 233,085 papers, the authors of [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] observed that despite the
widespread interest in chatbot integration, only 81 papers met the evaluation criteria for
inclusion, such as a relevant abstract, clear methodology presentation, full-text availability,
relevance, and use of English. The findings from [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ] indicates that "chatbot" and "artificial
intelligence" are the two keywords with the highest co-occurrence in the selected papers. The
use of the Python programming language is prevalent in developing chatbots [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ].
Consequently, we can conclude that while the topic is not novel, it is still cutting-edge, with
numerous successful chatbot and conversational agent implementations demonstrating their
potential. Various tools and language models are available to implement the personal shopping
assistant.
      </p>
    </sec>
    <sec id="sec-5">
      <title>4. Methods and Materials</title>
      <p>We propose to consider the following main stages of the research. First, a domain must be
defined in which collaborative analysis and BI can be modeled. Considering different goals,
preferences, experience and conditions, different users will access the same data with different
requests forming the content of collaborative session. Second, data sources need to be
identified. Combining data from different sources requires solving the problems of data
consolidation, cleaning, and standardization. Thirdly, one of the main stages is the formation
of a knowledge base of collaborative decision-making cases. At this stage, you need to develop
an information model for collecting data about each session, including user behavior and the
results of his research, as well as interaction with other users. Fourth, it is necessary to develop
a convenient interface for visualizing data and organizing interaction in the virtual space. The
final stage is associated with the processing, analysis, and summarizing of the collected data
about user behavior. We believe that as a result we will be able to create a CBI framework and
prove models and technologies for supporting virtual space, which will expand the
functionality of the BI4people project platform.</p>
      <p>
        Let us describe the data we use for experimenting. For each bodily accident occurring on a
road open to public traffic, involving at least one vehicle and causing at least one victim
requiring treatment, information describing the accident is entered by the law enforcement unit
(police, gendarmerie, etc.) which intervened at the scene of the accident [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ]. These entries are
compiled in a form entitled bodily accident analysis report. All of these files constitute the
national file of traffic injury accidents known as the "BAAC file" administered by the National
Interministerial Road Safety Observatory "ONISR".
      </p>
      <p>
        The databases, extracted from the BAAC file, list all the bodily injury accidents occurring
during a specific year in mainland France and in the overseas departments with a simplified
description. This includes accident location information, as entered, as well as information
regarding the characteristics of the accident and its location, the vehicles involved and their
victims. Every year, road accidents cause thousands of deaths. People are wondering what the
causes are, what specific issues influence the most, who are under the risk etc. We use the
dataset available at [
        <xref ref-type="bibr" rid="ref11">11</xref>
        ] as an example how people can explore data collaboratively and show
how the Virtual Assistant can support them. The data consists of four datasets which are
describe features of accidents (tabl. 1), places (tabl. 2), users (tabl. 3), and vehicles (tabl. 4).
      </p>
      <sec id="sec-5-1">
        <title>1 – Motorway</title>
      </sec>
      <sec id="sec-5-2">
        <title>2 – National road</title>
      </sec>
      <sec id="sec-5-3">
        <title>3 – Departmental road</title>
      </sec>
      <sec id="sec-5-4">
        <title>4 – Communal roads</title>
      </sec>
      <sec id="sec-5-5">
        <title>5 – Outside the public network</title>
      </sec>
      <sec id="sec-5-6">
        <title>6 – Car park open to public traffic 7 –</title>
      </sec>
      <sec id="sec-5-7">
        <title>Urban metropolis roads</title>
      </sec>
      <sec id="sec-5-8">
        <title>Width of the central reservation (TPC) if it exists (in m)</title>
      </sec>
      <sec id="sec-5-9">
        <title>Width of the carriageway</title>
        <p>allocated to the
circulation of vehicles
does not include hard
shoulders, TPCs and
parking spaces (in m).</p>
      </sec>
      <sec id="sec-5-10">
        <title>Surface condition Int Int Str</title>
        <p>not specified
not specified
-1 – Not specified
1 – One way</p>
      </sec>
      <sec id="sec-5-11">
        <title>2 – Bidirectional</title>
      </sec>
      <sec id="sec-5-12">
        <title>3 – With separate carriageways</title>
      </sec>
      <sec id="sec-5-13">
        <title>4 – With variable assignment channels not specified</title>
      </sec>
      <sec id="sec-5-14">
        <title>The value -1 means that the PR is not filled in The value -1 means that the PR is not filled in</title>
        <p>-1 – Not filled in
0 – Not applicable
1 – Cycle path
2 – Cycle lane
3 – Reserved lane
- 1 – Not specified
1 – Flat
2 – Slope
3 – Top of hill 4 – Bottom of hill
-1 – Not filled in
1 – Straight part
2 – Curved left
3 – Curved right
4 – “S” shaped
not specified
not specified
-1 – Not specified
1 – Normal
2 – Wet
3 – Puddles</p>
      </sec>
      <sec id="sec-5-15">
        <title>4 – Flooded</title>
      </sec>
      <sec id="sec-5-16">
        <title>5 – Snowy</title>
        <p>6 – Mud
7 – Icy
8 – Fats – oil
infra</p>
      </sec>
      <sec id="sec-5-17">
        <title>Planning - Infrastructure Int situ</title>
      </sec>
      <sec id="sec-5-18">
        <title>Situation of the accident Int env1</title>
      </sec>
      <sec id="sec-5-19">
        <title>Maximum authorized speed at the place and at the time of the accident</title>
      </sec>
      <sec id="sec-5-20">
        <title>9 – Other</title>
        <p>-1 – Not filled in
0 – None</p>
      </sec>
      <sec id="sec-5-21">
        <title>1 – Underground - tunnel</title>
      </sec>
      <sec id="sec-5-22">
        <title>2 – Bridge - flyover</title>
      </sec>
      <sec id="sec-5-23">
        <title>3 – Interchange or connecting ramp 4 –</title>
        <p>Railway
5 – Developed crossroads
6 – Pedestrian zone
7 – Toll area
8 – Construction site
9 – Others
-1 – Not specified
0 – None
1 – On the road
2 – On hard shoulder</p>
      </sec>
      <sec id="sec-5-24">
        <title>3 – On shoulder</title>
      </sec>
      <sec id="sec-5-25">
        <title>4 – On sidewalk</title>
      </sec>
      <sec id="sec-5-26">
        <title>5 – On a cycle path</title>
      </sec>
      <sec id="sec-5-27">
        <title>6 – On another special lane</title>
      </sec>
      <sec id="sec-5-28">
        <title>8 – Other</title>
        <p>Possible values</p>
        <p>not specified
the seat occupied in the vehicle by the
user at the time of the accident (detail
is given by the illustration)
10 – Pedestrian (not applicable)
1 – Driver
2 – Passenger
3 – Pedestrian
1 – Male
2 – Feminine
-1 – Not specified
0 – Not filled in
1 – Home – work
2 – Home – school
3 – Shopping – purchases
4 – Professional use
5 – Walk – leisure</p>
      </sec>
      <sec id="sec-5-29">
        <title>9 – Other</title>
        <p>-1 – Not filled in
0 – No equipment
1 – Belt</p>
      </sec>
      <sec id="sec-5-30">
        <title>2 – Helmet locp</title>
      </sec>
      <sec id="sec-5-31">
        <title>Location of the pedestrian Int actp</title>
      </sec>
      <sec id="sec-5-32">
        <title>Action of the pedestrian Int etatp an_nais</title>
        <p>num_veh</p>
      </sec>
      <sec id="sec-5-33">
        <title>This variable makes it</title>
        <p>possible to specify
whether the injured
pedestrian was alone</p>
      </sec>
      <sec id="sec-5-34">
        <title>User's year of birth</title>
      </sec>
      <sec id="sec-5-35">
        <title>Identification of the vehicle</title>
        <p>1 – PK or PR or ascending mailing
address number
2 – PK or PR or descending postal
address number
3 – No mark
00 – Indeterminable
01 – Bicycle
02 – Moped &lt;50cm3
03 – Cart (Quadricycle with bodied
motor) (formerly "cart or motor
tricycle")
04 – Reference unused since 2006
(registered scooter)
05 – Unused reference since 2006
(motorcycle)
06 – Reference unused since 2006
(sidecar)
07 – LV only
08 – Reference unused since 2006 (VL +
caravan)
09 – Reference unused since 2006 (VL +
trailer)
10 – LCV only 1.5T &lt;= GVW &lt;= 3.5T
with or without trailer (formerly LCV
only 1.5T &lt;= GVW&lt;= 3.5T)
11 – Reference unused since 2006 (VU
(10) + caravan)
12 – Reference unused since 2006 (VU
(10) + trailer)
13 – PL only 3.5T &lt;PTCA &lt;= 7.5T
14 – PL only &gt; 7.5T
15 – HGV &gt; 3.5T + trailer
16 – Road tractor alone
17 – Road tractor + semi-trailer
18 – Reference unused since 2006
(public transport)
19 – Reference unused since 2006
(tramway)
20 – Special gear
21 – Agricultural tractor
30 – Scooter &lt; 50 cc
31 – Motorcycle &gt; 50 cm3 and &lt;= 125
cm3
32 – Scooter &gt; 50 cm3 and &lt;= 125 cm3
33 – Motorcycle &gt; 125 cm3
34 – Scooter &gt; 125 cc
35 – Light quad &lt;= 50 cc (Unbodied
motor quadricycle)
36 – Heavy quad &gt; 50 cm3 (Quadricycle
with motor without bodywork)
37 – Buses
occutc
obs</p>
      </sec>
      <sec id="sec-5-36">
        <title>Number of occupants in public transport</title>
      </sec>
      <sec id="sec-5-37">
        <title>Fixed obstacle struck obsm</title>
      </sec>
      <sec id="sec-5-38">
        <title>Moving obstacle struck choc</title>
      </sec>
      <sec id="sec-5-39">
        <title>Initial shock point Int Int Int</title>
        <p>Int
38 – Bus
39 – Train
40 – Tramway
41 – 3WD &lt;= 50cc
42 – 3WD &gt; 50cc &lt;= 125cc
43 – 3WD &gt; 125 cc
50 – Motor EDP
60 – EDP without engine 80 – VAE
99 – Other vehicle</p>
        <p>not specified
-1 – Not specified
0 – Not applicable
1 – Parked vehicle
2 – Tree
3 – Metal slider
4 – Concrete slide
5 – Other slide
6 – Building, wall, bridge pier
7 – Vertical signaling support or
emergency call station
8 – Pos
9 – Street furniture
10 – Parapet
11 – Island, refuge, high boundary
12 – Sidewalk curb
13 – Ditch, embankment, rock face
14 – Other fixed obstacle on roadway
15 – Other fixed obstacle on sidewalk
or shoulder
16 – Obstacle-free road exit
17 – Nozzle – aqueduct head
-1 – Not specified
0 – None
1 – Pedestrian
2 – Vehicle
4 – Rail vehicle
5 – Domestic animal
6 – Wild animal
9 – Other
-1 – Not specified
0 – None
1 – Before
2 – Front right
3 – Front left
4 – Back</p>
      </sec>
      <sec id="sec-5-40">
        <title>5 – Right back</title>
      </sec>
      <sec id="sec-5-41">
        <title>6 – Left Rear</title>
      </sec>
      <sec id="sec-5-42">
        <title>7 – Right side</title>
      </sec>
      <sec id="sec-5-43">
        <title>8 – Left side</title>
      </sec>
      <sec id="sec-5-44">
        <title>9 – Multiple shocks (barrels) manv</title>
      </sec>
      <sec id="sec-5-45">
        <title>Main maneuver before the accident Int num_veh</title>
      </sec>
      <sec id="sec-5-46">
        <title>Identification of the</title>
        <p>vehicle</p>
        <p>Str</p>
        <p>Standard metadata formats exist to facilitate their collection, search and automatic
processing. The retained metadata are as follows:
• Title
• Acronym
• Description
• Licence
• Update frequency
• Key words
• Temporal coverage
• Spatial coverage
• Spatial granularity
• Private mode</p>
        <p>On the one hand, data reusers struggle to identify quality datasets and to assess whether
such and such a dataset is worthy of interest. On the other hand, data producers are not
sufficiently encouraged and supported to improve the quality of their data. It is set up a
metadata quality score on data.gouv.fr.</p>
        <p>The table 5 is depicts the metadata used.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>5. Results</title>
      <sec id="sec-6-1">
        <title>Description</title>
      </sec>
      <sec id="sec-6-2">
        <title>The description of the data is of high quality (the description of</title>
        <p>the data set is sufficiently long).
- The update frequency is entered.
- The update frequency is respected
- The license is populated.</p>
        <p>- The license is open</p>
      </sec>
      <sec id="sec-6-3">
        <title>Presence of at least one resource with a declared open format - Spatial coverage is provided - The spatial granularity is filled in</title>
      </sec>
      <sec id="sec-6-4">
        <title>The temporal coverage of the data is entered</title>
        <p>In 2015, when the town hall of Paris launched its Cycling Plan, it could not have imagined
that the end of it would coincide with a health context favoring its utilitarian practice. If the
first plan was ambitious in its redevelopment of the city's cycle paths, the balance sheet of
bicycle accidents in Paris and the reasons relating to it question the effectiveness of the first
plan.</p>
        <p>The advent of the health crisis in 2020 relating to the Covid-19 pandemic favors cycling but
requires these recent developments to be maintained and expanded. The appearance of the
socalled "coronapists" with the aim of improving traffic flow and relieving public transport has
initiated many new cyclists. If many European cities like Saint-Etienne or Marseille decide to
erase them after a few weeks, the town hall of Paris obtains the agreement of the government
that they are supported in the plan “France Relance”. 2020 is becoming the year of the bike.
The culture of utilitarian cycling is anchored in the daily lives of many Parisians, questioning
their safety.</p>
        <p>The proportion of accident victims wearing a helmet is also the majority and raises the
question of prevention and risky behavior adopted by cyclists in Paris. Is it due to an
infrastructure problem that supports the idea that the roads are not safe enough, even for users
aware of the risks? How effective are city hall's prevention efforts? The data does not allow us
to determine the causes of the accidentology, nevertheless they shed light on persistent
problems.</p>
        <p>Based on the analysis done, there are several important features that must be implemented
in virtual assistant software in order to assist novice buyers effectively. These features include:
• The ability to perform various data exploration commands such as filtering, querying, selecting,
and setting parameters.
• An information retrieval module is necessary to find relevant information, explore options, and
research user needs.
• Item matching is necessary to compare different offers and proposals.
• Personalization based on user preferences, history, and behavior, which can enhance the
relevance and effectiveness of the recommendations provided by the assistant.
• Machine learning algorithms to continuously learn from user interactions and improve the
assistant's ability to provide personalized recommendations.
• Language understanding and text generation are both necessary in order to effectively
communicate with the user.</p>
      </sec>
    </sec>
    <sec id="sec-7">
      <title>6. Discussion and Conclusion</title>
      <p>In this paper we have presented an approach how to create, approbate and estimate
collaborative decision-making models. BI systems are vastly used as a tool to support
decisionmaking in different kind of organizations. CBI give even more opportunities for reasonable
decision-making as they allow using external information from various sources. We are
collecting and processing data, developing convenient interface and tools for collaborative
analysis. The next step is to implement a prototype</p>
    </sec>
    <sec id="sec-8">
      <title>7. Acknowledgements</title>
      <p>The research study depicted in this paper is funded by the French National Research Agency
(ANR), project ANR-19-CE23-0005 BI4people (Business intelligence for the people).
8. References</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <article-title>[1] Business intelligence for the people</article-title>
          . URL: https://eric.univ-lyon2.fr/bi4people/indexen.html.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Muhammad</surname>
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Darmont</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Favre</surname>
            <given-names>C.</given-names>
          </string-name>
          (
          <year>2022</year>
          )
          <article-title>The Collaborative Business Intelligence Ontology (CBIOnt), 18e journé es Business Intelligence et Big Data (EDA -22</article-title>
          ), Clermont-Ferrand,
          <year>Octobre 2022</year>
          ;
          <article-title>RNTI</article-title>
          , Vol. B-
          <volume>18</volume>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>D.</given-names>
            <surname>Power</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Sharda</surname>
          </string-name>
          ,
          <source>Business Intelligence and Analytics</source>
          , Wiley,
          <year>2015</year>
          . doi:
          <volume>10</volume>
          .1002/9781118785317.weom070011.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>J.</given-names>
            <surname>Masche</surname>
          </string-name>
          , N.-
          <string-name>
            <surname>T. Le</surname>
          </string-name>
          ,
          <article-title>A review of technologies for conversational systems</article-title>
          , in: International Conference on Computer Science,
          <source>Applied Mathematics and Applications</source>
          , Springer,
          <year>2017</year>
          , pp.
          <fpage>212</fpage>
          -
          <lpage>225</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>N.</given-names>
            <surname>Svenningsson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Faraon</surname>
          </string-name>
          , Artificial Intelligence in Conversational Agents:
          <article-title>A Study of Factors Related to Perceived Humanness in Chatbots</article-title>
          ,
          <source>in: Proceedings of the 2019 2nd Artificial Intelligence and Cloud Computing Conference (AICCC</source>
          <year>2019</year>
          ),
          <article-title>Association for Computing Machinery</article-title>
          , New York, NY, USA,
          <year>2020</year>
          , pp.
          <fpage>151</fpage>
          -
          <lpage>161</lpage>
          . doi:
          <volume>10</volume>
          .1145/3375959.3375973.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>G.</given-names>
            <surname>Caldarini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Jaf</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>McGarry</surname>
          </string-name>
          ,
          <source>A Literature Survey of Recent Advances in Chatbots, Information</source>
          <volume>13</volume>
          (
          <issue>1</issue>
          ) (
          <year>2022</year>
          )
          <article-title>41</article-title>
          . doi:
          <volume>10</volume>
          .3390/info13010041.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>M.</given-names>
            <surname>Akhtar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Neidhardt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Werthner</surname>
          </string-name>
          ,
          <article-title>The Potential of Chatbots: Analysis of Chatbot Conversations</article-title>
          ,
          <source>in: 2019 IEEE 21st Conference on Business Informatics (CBI)</source>
          , IEEE,
          <year>2019</year>
          , pp.
          <fpage>397</fpage>
          -
          <lpage>404</lpage>
          . doi:
          <volume>10</volume>
          .1109/CBI.
          <year>2019</year>
          .
          <volume>00052</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>R.</given-names>
            <surname>Bavaresco</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Silveira</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Reis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Barbosa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Righi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Costa</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Antunes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Gomes</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Gatti</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Vanzin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. C.</given-names>
            <surname>Junior</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Silva</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Moreira</surname>
          </string-name>
          ,
          <article-title>Conversational agents in business: A systematic literature review and future research directions</article-title>
          ,
          <source>Computer Science Review</source>
          <volume>36</volume>
          (
          <year>2020</year>
          )
          <fpage>100239</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Gamboa-Cruzado</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          , et al.
          <article-title>Use of chatbots in e-commerce: a comprehensive systematic review</article-title>
          .
          <source>Journal of Theoretical and Applied Information Technology. 101.4</source>
          (
          <year>2023</year>
          ). http://www.jatit.org/volumes/Vol101No4/3Vol101No4.pdf
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Wahde</surname>
            ,
            <given-names>Mattias</given-names>
          </string-name>
          &amp; Virgolin,
          <string-name>
            <surname>Marco.</surname>
          </string-name>
          (
          <year>2022</year>
          ).
          <source>Conversational Agents: Theory and Applications</source>
          . https://arxiv.org/pdf/2202.03164.pdf
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11] Bases de données annuelles des accidents corporels de la circulation routière - Années de
          <year>2005</year>
          à
          <year>2021</year>
          . https://www.data.gouv.fr/en/datasets/bases-de
          <article-title>-donnees-annuelles-desaccidents-corporels-de-la-circulation-routiere-</article-title>
          <string-name>
            <surname>annees-de-</surname>
          </string-name>
          2005
          <string-name>
            <surname>-</surname>
          </string-name>
          a-2021/#_
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>