Difference between revisions of "Wisevoice Builder"

Revision as of 17:53, 22 January 2020

The Wisevoice Builder provides access to development of virtual conversational agents.

A project defines an individual virtual agent. The project configurations consists of two main areas:

There are 3 types of integrations:

Communication channels, such as SIP Callcenter, Web Chat, Facebook, SMS, Telegram and API that can be consumed by custom clients
External services integrations, such as UiPath and API
Customer service integrations such as Zendesk or Salesforce

There are two ways of defining a dialog:

The Q&A module offers a simple way of defining question and answer pairs. The content defined as Q&A is accessible to the chat user at any point in the conversation regardless of the context. (coming soon)
Conversation Flows are visual maps of dialog trees used to define more complex scenarios. A project can contain multiple conversation flows that are triggered in different situations.

@@ Line 17: / Line 17: @@
 There are two ways of defining a dialog:
 *'''The Q&A module''' offers a simple way of defining question and answer pairs. The content defined as Q&A is accessible to the chat user at any point in the conversation regardless of the context. ''(coming soon)''
 *'''Conversation Flows''' are visual maps of dialog trees used to define more complex scenarios. A project can contain multiple conversation flows that are triggered in different situations.
-For example a medical clinic might have the content of it's project structured the following way:
-*A Q&A collection that contains answers to general questions like the location of the clinic and working hours.
-*One conversation flow for creating new appointments
-*A second conversation flow for canceling appointments
-*A third conversation flow for routing between the first two. This flow is triggered by inbound calls from patients, asks for the call reason and triggers either the new appointment or the cancelation flow
-*A forth conversation flow for confirming appointments. This flow is triggered by API calls from the clinic's business logic server and generates outbound calls to the patients asking for confirmation.