Agent Publish
2. Robot Publish
It is possible to publish the robot to two categories and three types of channels for External Integration Can Access/Public Access/Public Access and Configuration.
2.1 Publish to “External Integration Can Access (No Review)
Click “Publish” to choose to publish the robot to external integration can access (currently support web sharing, nails, API calls, JS embedded, WhatsApp 5 ways), later will access more end channels.




2.1.1 Web Sharing
Webpage: You can choose "Normal Mode/Customer Service Model". The difference between the two is that you can manually or customize the conversation segmentation, and the customer service mode supports users to evaluate the conversation.


2.1.2 IM System
-Currently, it supports DingTalk. Click “Configure” to bind the DingTalk bot to the bot created by Agent Studio via the DingTalk bot Client ID and Client Secret, so as to realize the effect that you can ask questions to the bot directly on the DingTalk terminal.
Group Chat Context Configuration: If there is a need for Group Chat, it can be configured for multiple sessions.

2.1.3 API calls
For API calls, click "Interface Key" to obtain the robot Token and unique identifier. Access the robot directly through API calls. You can view the "Interface Documentation" above.


2.1.4 Website Embedding
Embed the robot into a website, supporting two embedding forms, suitable for front-end technical colleagues to operate.

2.1.5 Whatsapp access is available
Supports hosting a specified bot on a WhatsApp account, which can automatically reply to users' messages. Currently supports single chat, group chat (@bot will reply). Users need to contact the product consultant to open the permission before using this function.


2.2 Post to Agent Square (Public Access and Configuration) (Backend Review required)

Publishers can publish bots to public pages within the platform (visible to all users within the platform) in the following two forms:
Public access: other users within the platform can use the bot published by the publisher, but it cannot be copied;
Public access and Configuration: it can be copied. Other users within the platform can rename publicly configured bots for their own use;



2.3 Agent Status
Add the status of agents to differentiate their published status. Published agents need to be published again after editing to be effective to the public.
Last updated