Last edited one year ago
by Demo writer

MG Laser Consult and ChatBot introduction: Difference between pages

(Difference between pages)
No edit summary
Tag: 2017 source edit
 
No edit summary
Tag: 2017 source edit
 
Line 1: Line 1:
{{Organization Profile
<bs:uenoexport>{{ContentNav|homelink=Knowledge Base|hometext=1|pagePrevious=Onboarding{{!}}Checklist (Form)|pageNext=Travel reimbursement{{!}}Policy}}</bs:uenoexport>
|Logo=
<div class="databox">
|Headquarters=Regensburg
<div class="tbl">
|Contact since=2010
{|
|Status=active
|-
|Partnership=no Partner
!Author:
|Account Manager=Doe, John
|Robert Dirigl
|Technical Contact=Schreiber,Horst
|-
|Author=Angelika
!Reports to:
}}
|Marketing Team
<!--Kurze Beschreibung, woher der Kontakt kommt und Profil des Unternehmens-->
|-
!Report date:
|04/10/23
|}
</div>
<div class="tbl">
{|
|-
!Project:
|ChatBot
|-
!Reporting period / milestone:
|Q1-2023
|-
!Report status:
|'''finished'''
|}
</div>
</div>
==Executive summary==
The introduction of a chat bot as marketing/sales support was decided by management in 2022. The evaluation of various possible uses and different ChatBot services has progressed so far that a decision can be made. The following information provides an overview of the findings from the evaluation phase.


==Initial requirements==
==Details==
Major tasks that have been completed:


<span><br /></span>
{| class="wikitable" style="width:100%;"
==Installations==
!Business area
{{Project List}}
!Topic
!Highlights
!Major obstacles
unexpected project risks
!Lessons learned
|-
|Marketing
|Marketing/sales decided as the first user of the ChatBot technology
|
*Determination of the tasks of the ChatBot
*Ad Campaign: Planning complete
*Designs for ChatBot CI: Drafts are available
|
*Cost per use varies greatly depending on the bot
*Inclusion in website: time depends on website provider
|
*Good time to enter the AI world
*Risks rather minimal as costs can be planned incrementally
|-
|IT
|Evaluation of the different providers
|
*Shortlisted (xyAI, ChatSale, WinChat)
|
*Inclusion in CRM and ERM unclear
*Absence of admin staff in Q2
|
*In general, implementation within 3 months is conceivable
|-
|Support
|Processing and evaluation of chat contacts
|
*3 support staff will be trained accordingly
|
*no
|
*High motivation in the support team
*Support team needs a way to "train" the bots
|}
==Business review==
Assess the impact of the key findings for the reporting period.
{| class="wikitable" style="width:100%;"
!Metric
!Target
!Previous
period
!Current<span /><span /><span /><br />period
!Change
!New target
|-
|Number of ChatBot requests per month
|4000
| -
|<nowiki>-</nowiki>
| + 3000
|7000
|-
|Costs (up to 50000 requests/month)
| -
| -
|<nowiki>-</nowiki>
| -
|€400/month
|-
|Expected lead generation
|150
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|<nowiki>-</nowiki>
|400
|}


Links to the internal test system located at Hallo Welt!:
==Measures==
Based on the performance of the reporting period, the following actions are implemented for the above metrics.


==Project history==
===Number of ChatBot requests per month===
 
{| class="wikitable" style="width:100%;"
{| class="cuscosky" style="" width="100%"
! style="width:200px;" |'''Responsible'''
!'''Measures'''
|-
|-
!Year
| style="width:200px;" |Sibylle
!Milestone
|
!Contact
#Announcement of the ChatBot across all marketing channels
#In the initial quarter: Daily analysis of the chats conducted
|-
|-
|2022/02
| style="width:200px;" |Alex
|Upgrade to BlueSpice 4
|
|Maria Prüfling
#Guarantee 100% availability of the bot during the first week (emergency team is ready)
|}
 
===Costs (up to 5000 requests/month)===
{| class="wikitable" style="width:100%;"
! style="width:200px;" |'''Responsible'''
!'''Measures'''
|-
|-
|2014/03
| style="width:200px;" |Angie
|Custom: Mandatory categorisation
|
|John Doe
#Daily monitoring of user numbers. Informing marketing management when costs are exceeded.
|}
 
===Expected lead generation===
{| class="wikitable" style="width:100%;"
! style="width:200px;" |'''Responsible'''
!'''Measures'''
|-
|-
|2012/08
| style="width:200px;" |Thea, Malik
|BlueSpice pro self support (installation by customer)
|
|Maria Prüfling
#Evaluation of the chat questions that were asked and a graphical report to the marketing management
#Ensuring timely processing of all follow-up inquiries
|}
|}


==Technical notes for maintenance and support==
==Accompanying Documents==
 
External studies and surveys:
*External access:
*Internal deployment notes:
*Special procedures (e.g. maintenance cycles, cooperation partners, handling the stage system...)


==Marketing and Sales==
*[https://eos-solutions.com/chatbot-survey-2021.html EOS Chatbot Studie 2021]
*[https://www.simplr.ai/blog/22-chatbot-statistics-for-2022 Chatbot statistics (simplr.ai)]
*[https://www.businesswire.com/news/home/20230201005218/en/New-Survey-Finds-Chatbots-Are-Still-Falling-Short-of-Consumer-Expectations Customer satisfaction survey (businesswire)]


*Special contractual provisions (maintenance, framework contract):
*Logo use:
*Usable screenshots (link):


==Other notes and experiences==
<bs:uenoexport>{{ContentNav|homelink=Knowledge Base|hometext=1|pagePrevious=Onboarding{{!}}Checklist (Form)|pageNext=Travel reimbursement{{!}}Policy}}</bs:uenoexport>
[[Category:Status report]]

Revision as of 15:22, 9 February 2023

Author: Robert Dirigl
Reports to: Marketing Team
Report date: 04/10/23
Project: ChatBot
Reporting period / milestone: Q1-2023
Report status: finished

Executive summary

The introduction of a chat bot as marketing/sales support was decided by management in 2022. The evaluation of various possible uses and different ChatBot services has progressed so far that a decision can be made. The following information provides an overview of the findings from the evaluation phase.

Details

Major tasks that have been completed:

Business area Topic Highlights Major obstacles

unexpected project risks

Lessons learned
Marketing Marketing/sales decided as the first user of the ChatBot technology
  • Determination of the tasks of the ChatBot
  • Ad Campaign: Planning complete
  • Designs for ChatBot CI: Drafts are available
  • Cost per use varies greatly depending on the bot
  • Inclusion in website: time depends on website provider
  • Good time to enter the AI world
  • Risks rather minimal as costs can be planned incrementally
IT Evaluation of the different providers
  • Shortlisted (xyAI, ChatSale, WinChat)
  • Inclusion in CRM and ERM unclear
  • Absence of admin staff in Q2
  • In general, implementation within 3 months is conceivable
Support Processing and evaluation of chat contacts
  • 3 support staff will be trained accordingly
  • no
  • High motivation in the support team
  • Support team needs a way to "train" the bots

Business review

Assess the impact of the key findings for the reporting period.

Metric Target Previous

period

Current
period
Change New target
Number of ChatBot requests per month 4000 - - + 3000 7000
Costs (up to 50000 requests/month) - - - - €400/month
Expected lead generation 150 - - - 400

Measures

Based on the performance of the reporting period, the following actions are implemented for the above metrics.

Number of ChatBot requests per month

Responsible Measures
Sibylle
  1. Announcement of the ChatBot across all marketing channels
  2. In the initial quarter: Daily analysis of the chats conducted
Alex
  1. Guarantee 100% availability of the bot during the first week (emergency team is ready)

Costs (up to 5000 requests/month)

Responsible Measures
Angie
  1. Daily monitoring of user numbers. Informing marketing management when costs are exceeded.

Expected lead generation

Responsible Measures
Thea, Malik
  1. Evaluation of the chat questions that were asked and a graphical report to the marketing management
  2. Ensuring timely processing of all follow-up inquiries

Accompanying Documents

External studies and surveys:


Discussions