Dialog Actions
To speak is to act
Conversational interactions of the virtual agent, especially when running a business process can be broken down into discrete dialog actions. For example, prompt for an input, what to expect during a turn of a conversation etc.
Please find the dialog actions that Dhee supports using which you can define the dialog transitions as described in further automation chapters.
CALL_API
To make a call to a backend REST API
GET
To expect a slot value while displaying the prompt
EXPECT (Silent GET)
To expect a slot value without prompt
SPEAK
To display a message on the chatbot
SPEAK_N_EXIT
To display a message and exiting an intent
SPEAK_4_EACH
To speak multiple messages with the messages comma separated
SET
To equate or initialise a value to a slot
DO
To call upon another intent
TAKE_PAYMENT
To take the payments from end users
COMMAND
To perform a specific command, for example, COMMAND END_CONVERSATION to end the conversation
COMMAND_N_TEXT
To perform both command and text together
ESCALATE
To escalate the conversation to supervisors
WAIT
To add a waiting period in the chatbot
To perform emailer action
SAVE_2_SHEET
Save to spreadsheets action
SAVE_2_THIS_SHEET
Save to spreadsheets action from multiple intents
STORE_FEEDBACK
To store the user feedback
Find below the syntax for some the functions
SAVE_2_SHEET
SAVE_2_SHEET {slot 1} {slot 2} .. {slot K} The above command is to be called once per run of a top level intent. The location to find these spreadsheets is - Reports & Invoice/ Live Statistics/Output Spreadsheets
SAVE_2_THIS_SHEET
SAVE_2_THIS_SHEET {sheet name} {slot 1} {slot 2} .. {slot K} The advantage of this command over the existing intent specific sheets is that you can write to the same sheet from multiple intents (by using the same arbitrarily set name for the sheet from those intents' DSMs)
TAKE_PAYMENT
TAKE_PAYMENT ${amount slot} INTO {payment status slot} amount slot will be holding the value of amount to be asked from user, and can be replaced with any slot name which you use for the purpose.
Similarly, payment status slot will hold Boolean result of the transaction (true or false). Can be replaced with any slot name which you use for the purpose.
COMMAND
For signalling javascript events to parent pages use DSM Transition function - COMMAND EVENT (any event code you want to pass, without these brackets)
For closing widget and ending conversation - COMMAND END_CONVERSATION
COMMAND_N_TEXT
COMMAND_N_TEXT <COMMAND> <MLT> The advantage of this command over the COMMAND is that we can now send command and text together. For example, COMMAND_N_TEXT RingAlarm TimeForMeetingMLT
EMAIL emailId1|emailId2|emailIdN subjectMltName contentMltName subjectMltName should contain the subject of the email and contentMltName should contain the contents of the email
ESCALATE
To escalate the conversation for every supervisor - ESCALATE
To escalate to a specific domain (domain-wise escalation) - ESCALATE domainName
Last updated