掌握聊天机器人开发：从UX到盈利全方位指南

需积分: 9 72 浏览量更新于2024-07-19 收藏 3.46MB PDF 举报

"《构建更好的聊天机器人》是一本实用指南，专为开发者、程序员和对编程有一定基础的爱好者设计。本书详细探讨了在当今社交媒体平台上创建聊天机器人的最佳实践，特别是Facebook Messenger、Skype和KiK等渠道。作者Rashid Khan和Anik Das结合丰富的技术实施和用户体验（UX）知识，引导读者经历聊天机器人开发的生命周期。本书内容涵盖了从设置多渠道开发环境，如安装和配置开发工具，到实际构建聊天机器人，包括设计和编码过程。读者将学习如何与IFTT（If This Then That）和物联网（IoT）进行集成，实现更智能的功能。此外，书中还着重讲解了如何对聊天机器人进行数据分析和性能评估，这是优化用户体验和商业潜力的关键步骤。对于已有的聊天机器人开发者来说，本书能提供深入的洞察，帮助他们理解如何利用分析工具提升业务效率，并掌握如何在商业模式上实现盈利。随着各大科技巨头开放各自的聊天平台，聊天机器人已经成为品牌与客户互动的重要途径，这本书为那些希望在这个领域取得成功的人提供了宝贵的指导。《构建更好的聊天机器人》不仅包含了实用的代码示例，而且所有源代码都是开源的，便于读者下载和参考。整本书结构清晰，易于理解，无论是初次接触聊天机器人开发还是寻求进阶者，都能从中获益匪浅。版权信息和许可方面，书中的所有内容受到法律保护，确保了知识产权的尊重。通过阅读这本书，读者将掌握构建、优化和商业化聊天机器人的核心技能，从而在这个快速发展的领域取得竞争优势。"

CHAPTER 1 ■ INTRODUCTION TO CHATBOTS

The best use case for quick replies is to prompt the user to make a choice or ask the

user for their location (see Figure1-3). Quick replies are volatile in nature on Messenger

because after the user clicks, one of the quick replies disappears. Facebook Messenger

allows up to ten quick replies to be shown, and there is a restriction on the length of the

title of a quick reply; currently only 20 characters are allowed in the title.

Buttons

Buttons are key UI elements to help users choose between multiple options (see Figure1-4).

Buttons overcome the length restriction placed on quick replies. Buttons are nonvolatile;

in other words, they don’t disappear on user tap and can be tapped by the user at a

later time. The button action can be one of two types; on user tap, the button can send a

developer-defined payload or can open an external URL. The number of buttons that can

be displayed depends on the messaging platform, and we will discuss this when we show

how to build your first bot in Chapter 2. Buttons can contain the following:

• Title

• Payload text or URL

Figure 1-3. Quick replies on Facebook Messenger

Figure 1-4. Buttons on Skype, Slack, and Facebook Messenger

CHAPTER 2 ■ SETTING UP THE DEVELOPER ENVIRONMENT

Botframework

In Chapter 1, we went through the messaging platforms (Facebook Messenger, Skype,

Slack, Kik, Telegram, etc.) that have opened their platform to deploying chatbots.

Each platform has its own set of APIs to integrate to be able to receive and send messages.

The platforms have adopted similar UI elements. For example, Facebook has cards,

whereas Skype has carousels. These are similar UI elements from a user’s perspective, but

the naming convention is different from a developer’s perspective.

There are two ways to proceed further with the book.

• You can choose to build the integration for each platform where

you want to deploy your chatbot.

• You can go with an existing solution that already integrates with

the messaging platforms.

Building an integration for each of the platforms is complex and time-consuming.

Hence, for the rest of the book, we will go with the second option and use Botframework

from Microsoft.

Botframework helps connect your chatbot to various platforms with just the click

of a button. Botframework does the heavy lifting of integrating to all open messaging

platforms (Facebook, Skype, Microsoft Teams, Slack, Kik, etc.) and provides a simple-to-

use interface through a NodeJS SDK, C# SDK, and REST APIs to be integrated by your

chatbot application. To follow along with this book, you will be using NodeJS as the

primary programming language to build your chatbots. We will go through both NodeJS

SDK and REST APIs to integrate with Botframework. You will need a Microsoft Live ID to

use, and you do not need to enter your credit card information.

In the next chapter, we will go through the basics of bot building, including some of

the concepts around intents and entities. Also, we will be using Luis.AI, which is already

integrated with Botframework, to reduce some of the hassle of building intelligent bots.

Luis is an acronym that stands for Language Understanding Intelligent Service; it is a

product from Microsoft and is offered as an API for language understanding. Developers

integrate to Luis using the REST API provided and then pass each incoming request to

Luis, which responds to the chatbot with the intent and entities that were identified.

You’ll learn more about this in Chapter 3.

Local Installation

Moving forward, you will be developing your chatbot on your local development

machine. This will enable you to build the chatbot faster because you can use your

favorite text editor and can debug the code easily. Once you have completed the current

implementation, you can replicate the setup on a server and have the bot run perpetually.

In general, it is always a good practice to build and test locally before pushing the changes

to a production environment, so we will follow this methodology here.

剩余112页未读，继续阅读

向来痴SAS

粉丝: 30
资源: 71

掌握聊天机器人开发：从UX到盈利全方位指南

Build Better Chatbots A Complete Guide to Getting Started with Chatbots epub

Build Better Chatbots A Complete Guide to Getting Started with Chatbots 无水印原版pdf

build-better-chatbots:Rashid Khan和Anik Das的“ Build Better Chatbots”的源代码-Chat source code

Build-Incredible-Chatbots:Packt发布的用于构建不可思议的聊天机器人的代码存储库

Want_to_build_a_better_Set.zip_better

C:\Users\shunyue\Workspace\exam\master\node_modules\better-sqlite3\build\better_sqlite3.node

An better way to build and debug u-boot.zip

build

build：Netlify Build运行build命令，Build插件并捆绑Netlify Functions

build-essential_11.3.tar.gz_ build-essenti_build-essentia_build-

最新资源