Gallabox Bot FAQs
Unlock the secrets of Bot Management with our extensive FAQs. Master the art of creating, deploying, and optimizing chatbots with ease.
Last updated
Unlock the secrets of Bot Management with our extensive FAQs. Master the art of creating, deploying, and optimizing chatbots with ease.
Last updated
Our comprehensive FAQs cover all aspects of Bot Management to help you create, deploy, and optimize your chatbots with ease.
It is the time your bot will wait for a response before closing the conversation with a user. You can set timeout message and actions when the session is dropped without user's input.
It should only be inputted in minutes.
"Action on Invalid Response" phrase refers to action taken when a bot-flow encounters an invalid or unexpected response from a user. Let's define each of the options:
Drop from the bot:
If there's an error, the Bot session timeout action will happen and the message for Session timeout will be shared with the user.
Skip the Question:
Your customer will move forward with the BotFlow without answering a particular question.
Proceed to Fallback:
Fallback refers to an alternative or backup plan. If an invalid response is encountered, the question will be skipped and will move to the next card connected to the fallback connector🔶.
Yes, any number of flows with the correct intent/ payload can be created within a Bot.
Within a chatbot, intent refers to the keyword the customer texts you with when initiating a conversation. Without an intent, the chatbot cannot function. If you'd like your chatbot to start for any and every word use " * " as the intent.
Payload is the unique ID given to each intent/option button created for the Bot flow. Button payloads are used in scenarios when the option keyword may be repetitive or similar in nature. Types of Payload in Gallabox:
Intent Payload to link bot flows.
Button Payload to link cards within a flow.
You can make a broadcast specific bot but you can't deploy two bots together.
Yes, you can duplicate a flow and customize the pre-filled cards to create a new flow. This action promotes a faster method of creating a bot with the same conversational flow.
Ask Question Cards wait for some seconds for user response but Send Message Cards don't wait for user's response.
Ask Question Cards can be further linked to multiple cards depending on the options whereas the Send Message Cards can be further linked to one card.
A circular Bot can be created by ending your bot flow with a 'Send Message' card having button option. The payload of the required button should be the intent of your next flow.
Whenever you click on a Bot, look in the link updated in the browser. Refer the picture below, the part highlighted is the Bot id.
For example - you are seeing https://app.gallabox.com/bots/654454fe71a2a9198a678ed7/flows this in your browser when you clicked on a Bot. Then 654454fe71a2a9198a678ed7 will be the Bot id for the Bot you clicked. Every Bot has a unique Bot id.
Yes, you can customize the Validation error message according to your brand voice.
Yes, you can store user replies in variables for every Ask Card. Gallabox Variables are of two types:
Pre-existing data variables - these variables are available for the bot to use through customer contact information or field collection metrics. Eg: {{contact.name}}
Acquired data variables - these variables can be a response generated by the customer within the bot flow. Please note that these variables can only be used while collecting customer data in a conversational bot flow. Eg: {{response.email}}
Yes, to add an emoji is your card click on the emoji or press ⊞ Win + ' . ' .
Yes, you can integrate your bot flow with your CRM using the 'Connectors' Nodes. At present, we have Zoho, Leadsquared, Sangam, HubSpot connectors. You can also use API Call Connector to Integrate any third - party CRM.
Yes, you can send media files. Media files can be of audio, video or image. You can choose between audio, video, image, or document media file.
To link two cards click on the right-hand Rhombus button of card A and drag your cursor to card B.
Yes, if you are sending a Template Message with Quick Reply Buttons to your users.
Gallabox offers a helpful feature called "Nudge" to prevent users from dropping off the bot. If a user doesn't respond, enabling the nudge feature proactively engages the customer before they're disconnected from the bot.
To remove a current default bot, you can either make another bot as default or you can assign all the incoming messages to your Team.
To assign all the incoming messages to your Team or one person from your Team, go to Assignments.
Session logs are comparable to a diary for your bot, helping you understand user behavior and engagement. By analyzing session logs, you can pinpoint where users might be dropping off in the bot flow and assess the number of users who successfully complete interactions.
