Skip to content

Commit 0f67579

Browse files
deniskyashifdeniskyashif
committed
updated slides
1 parent ae7ef8e commit 0f67579

File tree

5 files changed

+103
-27
lines changed

5 files changed

+103
-27
lines changed

‎slides/img/chat1.png

33.4 KB
Loading

‎slides/img/chat2-wide.png

70.5 KB
Loading

‎slides/img/chat2.png

142 KB
Loading

‎slides/img/chat3.gif

137 KB
Loading

‎slides/index.html

+103-27
Original file line numberDiff line numberDiff line change
@@ -62,57 +62,57 @@ <h4>Progress Virtual Classroom</h4>
6262
<td><strong>Course</strong></td>
6363
</tr>
6464
<tr style="color: lightgray">
65-
<td>February 28, 2018</td>
65+
<td>June 26, 2018</td>
6666
<td>9am - 1pm EST<strong></strong></td>
6767
<td><strong>Kendo UI &amp; Angular</strong></td>
6868
</tr>
69-
<tr style="color: #60BEA0; font-weight: bold">
70-
<td>March 7, 2018</td>
69+
<tr style="color: lightgray">
70+
<td>June 27, 2018</td>
7171
<td>9am - 1pm EST</td>
72-
<td><strong>Telerik UI for ASP.NET MVC and ASP.NET Core</strong></td>
72+
<td><strong>Kendo UI &amp; jQuery</strong></td>
7373
</tr>
74-
<tr>
75-
<td>March 8, 2018</td>
74+
<tr style="color: #60BEA0; font-weight: bold">
75+
<td>July 10, 2018</td>
7676
<td>9am - 1pm EST</td>
77-
<td><strong>Kendo UI &amp; React</strong></td>
77+
<td><strong>Telerik UI for ASP.NET MVC and ASP.NET Core</strong></td>
7878
</tr>
7979
<tr>
80-
<td>March 14, 2018</td>
80+
<td>July 11, 2018</td>
8181
<td>9am - 1pm EST</td>
82-
<td><strong>Kendo UI &amp; jQuery</strong></td>
82+
<td><strong>Kendo UI &amp; Vue</strong></td>
8383
</tr>
8484
<tr>
85-
<td>March 22, 2018</td>
85+
<td>July 12, 2018</td>
8686
<td>9am - 1pm EST</td>
87-
<td><strong>Kendo UI &amp; Vue</strong></td>
87+
<td><strong>Kendo UI &amp; React</strong></td>
8888
</tr>
8989
<tr>
90-
<td>March 27, 2018</td>
90+
<td>July 13, 2018</td>
9191
<td>9am - 1pm EST</td>
9292
<td><strong>Telerik UI for Xamarin</strong></td>
9393
</tr>
9494
<tr>
95-
<td>March 30, 2018</td>
95+
<td>July 16, 2018</td>
9696
<td>9am - 1pm EST</td>
9797
<td><strong>Telerik UI for WPF</strong></td>
9898
</tr>
9999
<tr>
100-
<td>April 5, 2018</td>
100+
<td>July 17, 2018</td>
101101
<td>9am - 1pm EST</td>
102102
<td><strong>Telerik Reporting &amp; Telerik Report Server</strong></td>
103103
</tr>
104104
<tr>
105-
<td>April 10, 2018</td>
105+
<td>July 19, 2018</td>
106106
<td>9am - 1pm EST</td>
107-
<td><strong>Telerik UI for WinForms</strong><strong></strong></td>
107+
<td><strong>Telerik UI for ASP.NET AJAX</strong><strong></strong></td>
108108
</tr>
109109
<tr>
110-
<td>April 12, 2018</td>
110+
<td>July 24, 2018</td>
111111
<td>9am - 1pm EST</td>
112-
<td><strong>Telerik UI for ASP.NET AJAX</strong><strong></strong></td>
112+
<td><strong>Telerik UI for WinForms</strong><strong></strong></td>
113113
</tr>
114114
<tr>
115-
<td>April 13, 2018</td>
115+
<td>July 26, 2018</td>
116116
<td>9am - 1pm EST</td>
117117
<td><strong>Telerik UI for UWP</strong></td>
118118
</tr>
@@ -185,20 +185,15 @@ <h2>New Venture Software</h2>
185185
</ol>
186186
</aside>
187187
</section>
188-
<section data-background="./img/progress-next.PNG" class="present" data-background-image="./img/progress-next.PNG" style="top: 135px; display: block;">
189-
<a href="https://www.progress.com/next" target="_blank">
190-
<img alt="" src="./img/transparent.png" class="no-border bg-transparent">
191-
</a>
192-
</section>
193188
</section>
194189
<section id="agenda" class="color-white" data-background-image="./img/school-board.jpg">
195190
<h3>Agenda</h3>
196191
<ul>
197192
<li class="fragment">MVC and Razor (Recap)</li>
198193
<li class="fragment">Telerik UI for ASP.NET MVC</li>
199194
<li class="fragment">Telerik UI for ASP.NET Core</li>
200-
<li class="fragment">Common Features</li>
201-
<li class="fragment">Community and Support</li>
195+
<li class="fragment">Common Features - Conversational UI</li>
196+
<li class="fragment">Q&A</li>
202197
</ul>
203198
</section>
204199
<section id="prerequisites">
@@ -1037,6 +1032,87 @@ <h3>Live Demo</h3>
10371032
<p>For ASP.NET Core</p>
10381033
</section>
10391034
</section>
1035+
<!-- Conversational UI -->
1036+
<section>
1037+
<section>
1038+
<h3>Chatbots</h3>
1039+
<div style="text-align: left; float: left; max-width: 500px">
1040+
<ul style="font-size: 0.8em">
1041+
<li>Knowledge and Transactional chatbots</li>
1042+
<li>Smart chatbots</li>
1043+
<li>
1044+
Benefits
1045+
<ul>
1046+
<li class="fragment">Cost savings</li>
1047+
<li class="fragment">Automation of repetitive tasks</li>
1048+
<li class="fragment">24/7</li>
1049+
<li class="fragment">Scalable</li>
1050+
<li class="fragment">Engaged users</li>
1051+
<li class="fragment">Customer satisfaction</li>
1052+
</ul>
1053+
</li>
1054+
</ul>
1055+
</div>
1056+
<div style="text-align: center; float: right;">
1057+
<div>
1058+
<img src="./img/chat1.png" width="350" class="no-border" />
1059+
</div>
1060+
<div>
1061+
<img src="./img/chat2.png" width="450" class="no-border" />
1062+
</div>
1063+
</div>
1064+
<aside class="notes">
1065+
<p>
1066+
Chatbots are another area which we believe will gain more traction in the future. <br/>
1067+
2 types of bots: limited amount of specialized processes that replace the need to talk to a person or use complicated UIs <br/>
1068+
No one likes stupid bots (and people).
1069+
</p>
1070+
<p>
1071+
Benefits
1072+
<hr/>
1073+
<p>
1074+
There are generally two types of chatbots. We have all heard or used Alexa, Cortana, Siri and Google Assistant. These are the so called knowledge chatbots, which are trained on enormous amount of data and aim to help the user making a decision or providing the requested information. On the other hand, there are the transactional chatbots, whose purpose is to execute a limited amount of specialized processes that replace the need to talk to an expert, or to use complicated Uis such as long forms or processes. Think what a bank operator can do for you over the phone – verify identity, block stolen credit card, provide working hours for nearby branches, or help out with information about outgoing transfer. Other examples could be booking a doctor appointment, buy a vacation, food or insurance. All these, are very good cases for where a transactional chatbot can deliver value, by helping the customers 24/7 without the need for large operator teams to pick up the phone. <br/>
1075+
</p>
1076+
<p>
1077+
There is a catch though. No one likes, stupid chatbots, so it is very important to utilize Natural Language Understanding service and to train your bot properly, so your users never get blocked. A rule of the thumb is that a user using the chatbot should be able to finish their task faster than using other means (e.g. filling a form or a phone call).
1078+
</p>
1079+
</p>
1080+
</aside>
1081+
</section>
1082+
<section>
1083+
<h3>Conversational UI</h3>
1084+
<div style="text-align: left; float: left; max-width: 450px">
1085+
<ul style="font-size: 0.8em">
1086+
<li class="fragment">Easy to navigate and engaging</li>
1087+
<li class="fragment">Cover web, mobile and desktop</li>
1088+
<li class="fragment">Framework agnostic</li>
1089+
<li class="fragment">Deliver natural conversation flow</li>
1090+
<li class="fragment">Part of your app with same look and feel</li>
1091+
<li class="fragment">No need for external channels</li>
1092+
</ul>
1093+
</div>
1094+
<div style="text-align: right; float: right;">
1095+
<img src="./img/chat3.gif" width="450" class="no-border" />
1096+
</div>
1097+
<aside class="notes">
1098+
<p>
1099+
Information presentation – easy to understand and engaging. <br/>
1100+
Introduced conversational UI in W M D. <br/>
1101+
Framework agnostic, easy to use, aid natural conv flow, no need to another channel – use your app <br/>
1102+
<hr/>
1103+
Another thing that have to be considered is presentation of the information in a easy to understand, and engaging way. This is where we decided our expertise can help and we introduced the Conversational UI story across the board of all of our UI product lines to aid developers in the implementation of engaging chatbots, whether in mobile, desktop or web applications. <br/>
1104+
The Conversational UI components, are framework agnostic, which means, not matter which framework you utilize, you can use Conversational UI for your user experience. They are easy to implement and provide the means to deliver natural conversation flow and most importantly, you can embed these bots in your existing applications with the same look and feel and without the need to send your users to external channels such as facebook, skype, etc
1105+
</p>
1106+
</aside>
1107+
</section>
1108+
<section data-background="#000">
1109+
<h3>Live Demo</h3>
1110+
<h4>Conversational UI Component for ASP.NET</h4>
1111+
<a target="_blank" href="https://www.telerik.com/aspnet-mvc/conversational-ui">
1112+
<img alt="" class="no-border" src="./img/chat2-wide.png" />
1113+
</a>
1114+
</section>
1115+
</section>
10401116
<!-- Common Features -->
10411117
<section>
10421118
<section>
@@ -1135,4 +1211,4 @@ <h2>Thank You!</h2>
11351211
});
11361212
</script>
11371213
</body>
1138-
</html>
1214+
</html>

0 commit comments

Comments
 (0)