Principles of bot design - Revision history

Slavinsky: Category:Qubot

2022-06-30T16:05:23Z

Category:Qubot

Mlipa at 13:25, 29 June 2022

2022-06-29T13:25:39Z

Mlipa at 13:23, 29 June 2022

2022-06-29T13:23:08Z

Mlipa at 13:00, 29 June 2022

2022-06-29T13:00:59Z

Mlipa at 12:59, 29 June 2022

2022-06-29T12:59:05Z

Mlipa at 12:56, 29 June 2022

2022-06-29T12:56:47Z

Mlipa at 12:19, 29 June 2022

2022-06-29T12:19:17Z

Mlipa at 12:17, 29 June 2022

2022-06-29T12:17:31Z

Mlipa: Created page with "== Principles of bot design =="

2022-06-29T11:46:50Z

Created page with "== Principles of bot design =="

New page

== Principles of bot design ==

← Older revision		Revision as of 16:05, 30 June 2022
Line 1:		Line 1:
		+	[[Category:Qubot]]
	== Principles of bot design ==		== Principles of bot design ==

@@ Line 23: / Line 23: @@
 '''Consider the following two designs:'''
-Design 1
+'''''Design 1'''''
 <br>
 [[File:V1.jpg|400px]]
-Design 2
+'''''Design 2'''''
 <br>
 [[File:V2.jpg|400px]]
@@ Line 38: / Line 38: @@
 == Rich user controls ==

← Older revision		Revision as of 13:23, 29 June 2022
Line 31:		Line 31:
	<br>		<br>
	[[File:V2.jpg\|400px]]		[[File:V2.jpg\|400px]]
		+
		+	Starting the bot with an open-ended question such as "How can I help you?" is generally not recommended. If your bot has a hundred different things it can do, chances are users won’t be able to guess most of them. Your bot didn’t tell them what it can do, so how can they possibly know?
		+	Menus provide a simple solution to that problem. First, by listing the available options, your bot is conveying its capabilities to the user. Second, menus spare the user from having to type too much. They can simply click. Finally, the use of menus can significantly simplify your natural language models by narrowing the scope of input that the bot could receive from the user.
		+
		+	Menus are a valuable tool when designing bots for a great user experience. Don’t dismiss them as not being "smart enough." You may design your bot to use menus while still supporting free-form input. If a user responds to the initial menu by typing rather than by selecting a menu option, your bot could attempt to parse the user's text input.
		+
		+	== Rich user controls ==

@@ Line 22: / Line 22: @@
 '''Consider the following two designs:'''
 <br>
-Design 1
+[[File:V1.jpg|400px]]
 [[File:V1.jpg]]
 <br>
-Design 2
+[[File:V2.jpg|400px]]

← Older revision		Revision as of 12:59, 29 June 2022
Line 22:		Line 22:

	'''Consider the following two designs:'''		'''Consider the following two designs:'''
		+	<br>
		+	Design 1
		+	[[File:V1.jpg]]
		+
		+	<br>
		+	Design 2
		+	[[File:V2.jpg]]

← Older revision		Revision as of 12:56, 29 June 2022
Line 20:		Line 20:

	== Language versus menus ==		== Language versus menus ==
		+
		+	'''Consider the following two designs:'''

← Older revision		Revision as of 12:19, 29 June 2022
Line 12:		Line 12:

	Users interact with your application through the user interface that you implement. For example, A simple chat window or a mobile app, or even a robot with a voice interface.		Users interact with your application through the user interface that you implement. For example, A simple chat window or a mobile app, or even a robot with a voice interface.
		+
		+	== The chatbot's first user interaction ==
		+
		+	'''First impressions matter'''
		+
		+	The very first interaction between the user and bot is critical to the user experience. When designing your bot, keep in mind that there is more to that first message than just saying "hi." When you build an app, you design the first screen to provide important navigation cues. Users should intuitively understand things such as where the menu is located and how it works, where to go for help, what the privacy policy is, and so on. When you design a bot, the user's first interaction with the bot should provide that same type of information. In other words, just saying "hi" won’t be enough.
		+
		+	== Language versus menus ==

← Older revision		Revision as of 12:17, 29 June 2022
Line 1:		Line 1:
	== Principles of bot design ==		== Principles of bot design ==
		+
		+	By learning the concepts described in this section, you'll become equipped to design a bot that aligns with best practices and capitalizes on lessons learned thus far in this relatively new arena.
		+
		+	The rise of artificial intelligence (AI) continues to drive changes in how enterprises innovate and communicate their business. But for the humans and consumers interfacing with products affected by this technology, what will an AI-empowered future look like? What will it feel like? Empowered by rapidly advancing machine intelligence, product designers are rethinking the fundamental principles that guide the way they work.
		+
		+	The QuBot platform enables businesses and developers to create ChatBot experiences that solve a variety of business problems. By learning the concepts described in this section, you'll become equipped to design a bot that aligns with best practices and capitalizes on lessons learned thus far in this relatively new arena.
		+
		+	== Building a bot ==
		+
		+	If you are building a bot, it is safe to assume that you are expecting users to use it. It is also safe to assume that you are hoping that users will prefer the bot experience over alternative experiences like apps, websites, phone calls, and other means of addressing their particular needs. In other words, your bot is competing for users' time against things like apps and websites. So, how can you maximize the odds that your bot will achieve its ultimate goal of attracting and keeping users? It's simply a matter of prioritizing the right factors when designing your bot.
		+
		+	Users interact with your application through the user interface that you implement. For example, A simple chat window or a mobile app, or even a robot with a voice interface.