cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Guides

Learn more about specific Flow features
Filter
Filter by Labels
Select any of the labels below to filter results.
Filters applied...
Sorted by:
Flow allows you to create multiple fallback scenarios for when the NLP engine fails to understand a message. The Unknown Trigger For creating fallback scenarios we provide a special trigger called   Unknown. Whenever the system receives a trigger it cannot match it will search for an Unknown trigger. Handing over to humans If you want to hand over a conversation to a human agent, you can do this by using the   takeover action   in   cloud code.     Auto Pause When a human agent sends a message using the Chat app the NLP engine is paused automatically. You can set the number of minutes before the bot is activated again using the project settings. The NLP engine also automatically pauses when there a messages being sent by moderators on Channels like Facebook Messenger. For example: when an employee uses the Facebook for business app to send replies. Example Scenarios Standalone AI Assistants Add a new flow Start with the trigger Unknown Add a Text reply with the message:   Sorry I don't know about that yet Customer service     Add a new flow Start with the trigger Unknown Add a Text reply with the message:   Thank you, one of our service operators will be here shortly Drag and drop an action with Takeover Drag and drop an action with Pause bot Customer service, double tap     Add a flow Start with the trigger Unknown Add a Text reply with the message:   Could you please rephrase the question Add another the Unknown trigger below the reply message Add a Text reply with the message:   Thank you, one of our service operators will be here shortly Drag and drop an action with Takeover Drag and drop an action with Pause bot Read more on Handover actions:  Chatbot Handoff How to nail the bot to human handoff How pausing and resuming works with Front How to implement Push Notification How to hand over to a human agent Send text versus trigger event Trigger the bot from within Front
View full article
by Khoros Staff Khoros Staff Jun 19, 2021
Labels (4)
0
83
With   data retention,   you can automatically remove conversation data that is resolved or inactive. Note: To enable this feature within your project settings you'll have to upgrade to an enterprise plan. Instead of adding a   resolve   action inside a flow, you can also resolve all conversations when they are no longer active, or remove data after the last time a resolved conversation was updated. The image below shows that inactive conversations will be resolved after 1 day. And after 1 day that they are resolved they will be permanently deleted.     You can do the same manually by clicking on the   Resolve   and   Run policy   buttons.   Resolve   will resolve all conversations that are not yet resolved and   Run policy   will remove all resolved conversations that confirm with the configured policy.   Event triggering You can also trigger an event after auto resolve or after agent’s resolve/archive. This is useful if you, for example, want to automatically send out a survey.    
View full article
by Khoros Staff Khoros Staff Jun 19, 2021
Labels (1)
  • Flow Integrations

0
123
The Payload list/button support for WhatsApp enhances the user experience for the end-users.  It helps to create preset options for the users who are seeking instant consultation over WhatsApp. The users can choose from the available options, this eases the process by reducing the typing effort for the end-users. This also curates the inputs that are sometimes not recognized by the bot.  Implementing the Payload support for WhatsApp also helps to retain and retrieve the customer resolution histories, if required. To implement payload list/ button support for WhatsApp, ensure that you have integrated WhatsApp.  Create Payload List Support for WhatsApp In a Flow, create a Trigger Event . In the Replies section, drag List and create List Items for the list. Update the following for List Items: Note:    You can add multiple lists and list items. To avoid errors, ensure that the text length in the field is in-inline with WhatsApp/ Facebook restrictions . You can see the error messages in the Notification section.  List Fields  Description Header Type   Select a reply format (text, image, video, or document).  This is set to None, by default.  Header Value Enter a List name that broadly defines the list. Note: You should select a header type in order to enter a value. Body Enter additional information about the list or customer concerns that must be addressed. Section Title Enter section name that broadly defines the list options. List Item Title Enter option names for the customers.  List Item Description Enter additional information to describe the option.  List Item Type Select the list type:  Send Text Value- To send a text reply.  Trigger Event- To trigger another event. Value or Event Depending on your selection in the above field: Enter the text reply for Send Text Value. Select an event for Trigger Event.  Note: The event needs to be created first.  PARAMS (Optional) Enter the Label and Value.  This information is archived in the database with the label and value for future retrieval. The default use case is using param in bot conditions. Button Text Enter final call to action for the customers, once the customer chooses from the list options. Footer (Optional) Enter additional information or announcements, if any.    Create Payload Button Support for WhatsApp In a Flow, create a Trigger Event . For the Replies section, add Buttons . Update the following for Button options: Note:    You can add multiple lists and list items. To avoid any errors, ensure that the text length in the field is in-inline with the WhatsApp/ Facebook restrictions. You can see the error messages in the Notification section.  List Fields  Description Header Type (Optional) Select a reply format (text, image, video, or document).  This is set to None, by default.   Header Value Enter a Button name that broadly defines the list. Note: You should select a header type in order to enter a value. Body Enter additional information about the list or customer concerns that must be addressed. Button Title Enter option name for the customers.  Button Type Select the button type:  Send Text Value- To send a text reply.  Trigger Event- To trigger another event.  Button Value Depending on your selection in the above field: Enter the text reply for Send Text Value. Select an event for Trigger Event.  Note: The event needs to be created first PARAMS  Enter the Label and Value.  This information is archived in the database with the label and value for future retrieval.  Footer Enter additional information or announcements, if any.   Separate list section items/ button options should have different Text Values or Trigger Events in order to provide distinct resolutions for the options selected by the end-users. 
View full article
by Khoros Staff Khoros Staff Nov 19, 2021
Labels (3)
0
235
This article explains definitions for all the Flow metrics captured in Flow Analytics. Flow Metrics  Flow analytics captures events that take place during user interaction with a chatbot. With each reported event, you can find an agent_id and thread_id . The agent_id relates to the Flow project and the thread_id relates to the interaction with a customer. When considering the Flow event metrics like interaction, handover or resolve, you might see small variants in the reported numbers; this is expected when you compare a metric for a specific period. Sometimes a user interaction can span a longer period than you are currently looking at, ensure that you are considering the correct timeframe.  Flow Analytics Dimensions Analytic events are separated into two dimensions: Thread and Brain events.  Thread events The following events are tagged with the thread events dimension when there is an interaction: Event Definition MESSAGE_IN Flow receives a message Note: This can be either from a customer, a moderator, or an agent (use the originator_role to distinguish). MESSAGE_OUT A reply is sent back by the automation LANGUAGE A language is detected (present in the language field) COUNTRY A country is detected (present in the language field) EVENT_OPENING An opening event is triggered (only supported by certain channels) EVENT_BROADCAST A broadcast is triggered PROJECT A new Flow project has been created ORGANISATION A new Flow organisation is created INTERACTION_NEW When a new interaction is created INTERACTION_UPDATED An existing interaction is updated RESOLVED_BY_BOT An interaction is resolved by the automation RESOLVED_BY_AGENT An interaction has been resolved by an agent TAKEOVER A takeover/handover is applied to an existing interaction TAG_ADD A tag is applied to a user TAG_REMOVE A tag is removed from a user USER_NEW A new user is registered Specific for voice: Event Definition VOICE_CALL_DISCONNECT A call is disconnected VOICE_CALL_HANDOVER A handover is applied for a call VOICE_CALL_CONFERENCE_END A call ends VOICE_CALL_AGENT_JOIN An agent joins a call VOICE_CALL_HOLD_ON A call is put on hold  VOICE_CALL_HOLD_OFF A call is put back from hold VOICE_CALL_AGENT_MUTE_ON An agent puts the call on mute VOICE_CALL_AGENT_MUTE_OFF An agent puts the call off mute Fields Field Description __time Date in a UTC format agent_id Flow project ID channel_id Connected channel or source ID channel_name Type of channel country Two-letter identifier of the region For example: us event_name Type of event  For example: MESSAGE_IN, TAKEOVER, USER_NEW, TAG_ADD language Two-letter language code  For example: en originator_role The originator’s role for the event For example: SYSTEM, EXTERNAL, MODERATOR, etc. tag_name Name of the tag that is applied tag_value Value of the tag that is applied thread_id Conversational thread between the bot and the customer resolution Reason of resolution attachment_event_name Event name that is triggered timestamp UNIX timestamp event_value Related Payload  campaign_id Broadcasted campaign care_conversation_id Care Conversation ID interaction_id Unique id for every interaction Brain events The following events are with the brain events dimension when there is an interaction: Event Definition FLOW_TRIGGERED A specific flow is triggered UNKNOWN_TRIGGERED An unknown message is received SENTIMENT AI estimated sentiment Note: You can find the Sentiment value in the Sentiment field. TAG_CREATED Old form of tags for thread params.  Note: You can find usage of it inside of text replies in the Advanced section in the right sidebar. Fields Field Description __time Date in a UTC format agent_id Flow project ID brain_name AI model flowai for single language model or flowaiv2 for multilingual model channel_id Connected channel or source ID channel_name Type of channel event_name Name of the event that is triggered flow_id Flow ID that is triggered  Note: This can change between versions flow_immutable_id Unique Flow ID that is triggered flow_name Name of the Flow that is triggered intent_id Intent ID that is matched  Note: This can change between versions intent_immutable_id Unique intent ID that is matched intent_label Name of the intent that is matched language Two-letter language code query The text utterance step_id Unique step ID that is matched step_name Name of the step that is matched step_type Type of the step that is matched  For example EVENT, INTENT, ANYTHING, NOTHING, etc.  thread_id Conversational thread between the bot and the customer accuracy AI confidence matched with an intent threshold Confidence threshold used for matching the intent timestamp UNIX timestamp
View full article
by Khoros Staff Khoros Staff Aug 29, 2022
Labels (6)
0
61