Comparación de páginas

...

• Name: Specify a name for the bot.

• Description: Add a description, indicating the purpose/purpose of the bot.

• Bot Template (only available for CHAT-type bots): Select one of the available bot templates to start building your bot, or select Empty Bot if you want to create your bot from scratch. The available templates contain examples of different types of nodes and allow you to have conversations with customers for three specific use cases:

  • Appointment Scheduling: generates a conversation for scheduling an appointment for a specific service. It contains a node that queries available appointment schedules through a web service and displays them to the customer for selection.

  • Prospect Capture: Generates a conversation for capturing prospects for your company. Captures and stores different prospect data (name, type of document, email, etc.).

  • Satisfaction Survey: Generates a conversation to conduct a customer satisfaction survey. It asks the customer to rate the service received (on a scale of 1 to 5) and collects comments.

• Use an existing bot as a template (only available for CHAT-type bots): Activate this option if you want to use a bot previously created on the platform as a template for your new bot. Upon doing so, a selector with available bots will be displayed. Choose the bot you want to use, and its published version will be duplicated and automatically loaded as a template for the new bot.

...

3. The panel on the right side of the screen allows you to add new nodes and edit the configuration of existing nodes. By clicking the Edit button of a specific node, its configuration will be displayed in this panel, allowing you to make necessary modifications. Additionally, clicking the "Conversation Preview" button(only available for CHAT-type bots)will open a window in this panel where you can send a message. The bot will initiate the conversation flow, allowing you to validate its correct functioning.

...

• Keep in mind what is going to be the message or type of message triggering the conversation. The first bot node must be able to recognize this message and act on it.

• Except for the first (has only child nodes) and last node of the flow (has only parent node), all nodes have a parent node or node that links to the entry point, and one or more child nodes that link to the node's exit point.

• Logic is important when constructing a bot conversation flow, so the order and sequence of nodes will influence the flow and effectiveness of the conversation.

• In case of leaving "orphaned" or unconnected nodes, they will be listening to the customer's messages constantly, regardless of the rest of the flow.

Node Configuration (CHAT)

• Name: It is the name of the node.

• Description: Is the description and/or purpose of the node within the flow.

• Intent: It is the specific intention of the end customer when entering the node. It is recommended that the intentions of each of the nodes are unique and different, since this value will be used to obtain statistics and analyze the bot's conversations.

• Pattern: This is the pattern or regular rule that must match the incoming messages sent by your customer for the bot to execute the node's logic. This pattern can be an exact text string (for example, if the given pattern is "Hello", the node logic will execute when the customer types "Hello", or a regular expression that encompasses several options. More information about regular expressions and patterns here: https://developer.mozilla.org/es/docs/Web/JavaScript/Guide/Regular_Expressions

• Node Type: This is the type of node and must be selected according to the purpose of the node (giving a message to the customer, asking the customer for information, querying an external web service, etc.). The available node types are (find the detailed description of each node type below):

  • Ask

  • Say

  • Capture: By selecting this field node type, the following additional fields will be displayed in the form:

    • Expected: Type here a regular expression to validate the response sent by the customer.

  • List: By selecting this node type of field, the following additional fields will be displayed in the form:

    • List: Specify here the list of values to be shown to the customer for selection. In case the tickets come from a previous node of Web Service type, use the nomenclature {{webhook.response}}.

  • Fallback: When selecting this node type of field, the following additional fields will be displayed in the form:

    • Bot: Select here the bot to which the conversation will be moved in case of exceeding the maximum attempts.

    • Bot Node: Select here the bot node to which the conversation will be moved in case the maximum attempts are exceeded.

    • Maximum Attempts: Specify here the maximum number of attempts that the customer will have to retry the previous step to this node.

  • Scheduled Node: When selecting this node type of field, the following additional fields will be displayed in the form:

    • Start Date: Specifies here the start date of the period/range during which this node will be applied.

    • End Date: Specify here the end date of the period/range during which this node will be applied.

  • Validator: When selecting this field node type, the following additional fields will be displayed in the form:

    • Condition Type: Specifies here whether the validation rules will be applied with the conditional and (or - all of the rules comply) or with the conditional or (or - some of the rules comply).

    • Validation Rules: Add one or more validation rules, specifying a variable, an operator, and a value.

  • Web Service: When selecting this field node type, the following additional fields will be displayed in the form:

    • Request Type: Select one of the available HTTP request types (GET, HEAD, POST, PUT, DELETE, CONNECT, OPTONS, TRACE, PATCH).

    • URL/Endpoint/IP: Specify here the URL/endpoint/IP address to access the webservice. For example, https://mywebservice.mybusiness.com/getCustomerInfo/4224563

    • Headers: Specify here the headers that should be added to the HTTP request to consume the web service. For example, { "Authorization": "AccessKey GoCsdWE5rR2x7oXTQ4cPn4fTb5R"}.

    • Body: Specify here the body of the HTTP request. Generally, this body should have a JSON structure. For example, {"first name": "Jane", "last name": "Doe}.

    • Timeout: Specify here the maximum time Sagicc will have to wait when consuming the web service. If this time is exceeded, the request will be considered failed.

  • Dialog Flow

  • Go to

    • Bot: Select here the bot to which the conversation will be moved.

    • Bot Node: Select here the bot node to which the conversation will be moved.

• Use template: Activate this option if the message you want to send in the node corresponds to a previously created template in Sagicc. By activating it, you will be able to select the desired template.

• Message: This is the message that will be sent to the customer in this conversation node. It can be a customized message with variables, emojis 😀😎😋, links (), specific formatting (hello, hello, hello), and can include variables associated with the case, customer, and other entities in Sagicc. Use the Variables option to copy variables and include them in the message."

• Action: corresponds to an action that will be executed in Sagicc when the conversation between the bot and the customer passes through this node. The available actions are:

  • Transfer to agent: Transfers the conversation with the customer to a human agent of the campaign, modifying the user assigned to the ticket generated for the conversation.

  • Transfer to a campaign: Transfers the conversation with the customer to a different campaign.

  • End conversation: Marks as closed the ticket generated for the conversation with the customer.

  • Release conversation: Removes the user assigned to the ticket generated for the conversation (Sagicc System) and leaves the ticket free so that any human agent can take it and continue the conversation with the customer.

• Enabled: Specifies whether the node is enabled or disabled in the flow.

Node Types (CHAT)

Node Configuration (VOICE)

• Name: This is the name of the node.

• Description: This is the description and/or purpose of the node within the flow.

• Node Type: This is the type of node and should be selected according to its purpose (play an audio, capture customer information, etc.). The available node types are (find detailed descriptions of each node type below):

  • Read: When selecting this node type, the following additional fields will appear in the form:

    • Variable Name: This is the name of the variable through which the bot's response in this node will be identified. It can be accessed from other nodes.

    • Audio to Play: Attach the audio file to be played to the customer here. It must be in one of the following formats: wav, mp3, ogg.

    • Maximum Digits: Enter the maximum number of digits expected to be dialed by the customer.

    • Minimum Digits: Enter the minimum number of digits expected to be dialed by the customer.

    • Number of Attempts: Specify the number of failed attempts the bot will accept before moving to the fallback node. A failed attempt is one where the user dials more or fewer digits than allowed.

    • Audio to Play on Failed Attempt: Attach the audio file to be played to the customer after a failed attempt.

    • Fallback: Select the node to which the conversation will be redirected once the failed attempts are exhausted.

  • Playback: When selecting this node type, the following additional fields will appear in the form:

    • Audio to Play: Attach the audio file to be played to the customer here. It must be in one of the following formats: wav, mp3, ogg.

    • Number of Attempts: Specify the number of failed attempts to play the audio.

    • Fallback: Select the node to which the conversation will be redirected once the failed attempts are exhausted.

  • Go To: When selecting this node type, the following additional fields will appear in the form:

    • Action: Choose the action to be executed in this node. It can be "Transfer to a Campaign" or "Go to a Bot."

    • Campaign: If selecting "Transfer to a Campaign" in the previous field, choose the corresponding campaign here.

    • Bot: If choosing "Go to a Bot" in the previous field, select the corresponding bot here.

    • Bot Node: Select a specific node of the bot to which you want to redirect the conversation.

  • Menu: When selecting this node type, the following additional fields will appear in the form:

    • Variable Name: This is the name of the variable through which the bot's response in this node will be identified. It can be accessed from other nodes.

    • Audio to Play: Attach the audio file to be played to the customer here. It must be in one of the following formats: wav, mp3, ogg.

    • Number of Attempts: Specify the number of failed attempts the bot will accept before moving to the fallback node. A failed attempt is one where the user dials more or fewer digits than allowed.

    • Audio to Play on Failed Attempt: Attach the audio file to be played to the customer after a failed attempt.

    • Fallback: Select the node to which the conversation will be redirected once the failed attempts are exhausted.

Node Types (VOICE)

Save and Publish the Bot

...