Zia is equipped with default in-built abilities that allow it to perform actions based on user’s instructions. But that’s not all; with the help of Zia’s Developer Console you can define unique set of actions depending on your requirements.
Actions can be defined as single ability or tasks that Zia performs when you give an instruction during a conversation.
For example, you ask Zia to get the details of the deals closing this month by stage or add a note to a record. Tasks like these are called as actions. Based on the intention of the action, an action can be classified in to three different types.
Defining an action in Zia involves configuring Sample sentences, Parameters and Functions for any particular action.
Parameters
Parameters or Params are data that are required to fulfill or execute an action. For example, typical params for an action like create an event in CRM would be title, start time, end time and so on.
If we compare execution of action with filling a form, then the fields in the form are considered as the params for the action. Params that are statically pre configured while defining an action are "Static params" while that are included in the runtime are call "Dynamic params".
Sample sentences
Sample sentences are the example invocations that end users may say to invoke a particular action in their natural language. For example, typical sample sentences for an action that creates an event in CRM would be the following.
When conversing, people speak out data as part of invoking instructions and hence sample sentences can also be considered as params. For example, the following can be sample sentences that include params like event title, start time and from time.
Hence, the data model for Zia’s intelligence is formed by the combination of sample sentences and params.
Functions
Functions are the custom hooks written by developers that are executed by Zia during execution of any action. All the functions must be written in Deluge <<