Please make sure you sign up with the same account with which you would like to create and maintain the app from. Transferring apps/wallet balance from one account to another in future would not be possible
By logging in, you are agreeing to the Terms of Service and the Privacy Policy.
Want to outsource bot development? We have partners to get it done. Click here to get in touch
Using the Flow Bot Builder you can add small talk module and also tweak few configurations for the bot like the fallback message or NLP threshold etc. Let's look at these in this guide.
Use this section to configure your Bot responses based on certain user messages, that can be mentioned at anytime during the conversation. An example of this is small talk phrases like Hi, hello, good morning, etc. In addition, there could be specific user statements like “how do I pay” or “start over” for which, your bot can redirect users to specific flows.
For text inputs & responses, add user variations to allow for more varied user input match and random bot responses to keep the conversation fresh & avoiding the bot to repeat itself to often.
To add a user message, you need to click on the Manage conversations icon from the menu on the left.
You will get this screen to add the user messages and Bot responses, which can be a bot message or calling a flow
You can add the expected user query(user intent) on the left and the bot response to that query on right. You can also add variations to the user query or the bot response by clicking “Add variations”.
NOTE:
1. Adding variations to the user query means that the bot should consider them all as the same query from the user and send the appropriate bot response back.
2. Adding variations to the bot responses means that the bot can send any one of those responses randomly to the user.
You can also add more keywords or smalltalk phrases by clicking on the “+ Add More” button. Once you have added your required list of words and phrases, click on “Done” to save.
When you add smalltalk to your bot via the Manage conversations section, Gupshup's NLP is called every time to match the intents from the user. This might cause your bot to break in cases where you are expecting an open-ended response from the user.
For example:
In a specific flow of your bot, you want users to enter their email address. Now an email address is different for different users. With Smalltalk added to the bot Gupshup's NLP will be called and since the email address will not match the example entered by you in the bot script, your bot will send out the default failure message.
There is a way to stop this from happening. You can turn off the Smalltalk for that specific flow, so that the NLP engine is not called and bot accepts any input from the user.
Rule for Turning off Smalltalk
How to turn Smalltalk off
Select the bot state before the user state from the tree view for which smalltalk has to be turned off. Then in the script designer hover or click on the down arrow button. You should see options as displayed in the screenshot below
click on the chat like option beside the edit button and you are done. This is the icon from when smalltalk is OFF for that state
To access the Settings, click on this icon from the menu on the left.
Threshold:
As the Flow Bot Builder is powered by Gupshup's NLP framework, this threshold is a way to configure the acceptable maxintent score for the user intents(user says).
The default value is set to 0.2 but you can change this to any value between 0-1 as per your need.
Fallback response
When your bot doesn't understand the user message, it can either respond with a text message or redirect user to a specific flow. A good fallback response guides the user to rephrase their query or gives them a message with buttons to move forward in the conversation.
Re-state query
Typically, in most conversations, when a person replies with an incorrect or inappropriate response, we tend to restate our query, to ensure they get it the second time round. Today, when a bot doesn?t understand the user intent, it throws the Fallback response and waits for the user?s message. This can be confusing to the user at times, especially with voice bots.
To address this conversational dilemma, you can always have the Bot restate its message in case of an incorrect user response. When this option is enabled, the bot will always repeat the query / message to the user after responding with the Fallback response.
Google Analytics
You can enable Google's analytics by toggling the on/off switch and adding the Tracking ID of the Google analytics.
Debugger
By default, the “Logs” tab on the dashboard for your bot with Flow Bot Builder will not generate any logs. You can turn on the logs for debugging by toggling the on/off switch.
Peristence Menu
This feature is primarily built for Facebook messenger and Gupshup?s web widget. Users can configure a persistence menu with buttons that link back to a specific flow (postback), open a web URL or create a sub-menu. The persistence menu, along with sub-menu?s can be maximum of 3 (level 1) X 5 (level 2) X 5 (level 3) buttons.
Once you?ve configured your Persistence menu, use the ?Get Configuration? button to copy the JSON code snippet. When publishing your bot to Facebook messenger and web widget, paste it in the configuration
This will only be a one time activity, as once your bot is published to these channels, to make any further updates, you will just need to deploy your changes from Flow bot builder and the latest persistence menu changes will reflect live on these channels.
This website uses the following types of cookies: strictly necessary, functional and performance cookies. To know more information regarding how these cookies may impact your experience, please click on Settings.
These cookies are necessary for the website to function and cannot be switched off in our systems. They are set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Name | Provider | Purpose | Expiry | Type |
---|---|---|---|---|
CookieConsent | CookieBot | Stores the user's cookie consent state for the current domain | 1 year | HTTP |
smacon | www.gupshup.io | Authenticating user to access our website | Session | HTTP |
rc::c rc::b |
This cookie is used to distinguish between humans and bots. | Session | HTTP | |
JSESSIONID | www.gupshup.io | Preserves users states across page requests. | Session | HTTP |
gipuserid | www.gupshup.io | Collect & store User ID for easy accessibility | 5 years | HTTP |
__stripe_mid | www.gupshup.io | Stripe is used to make credit card payments in our application. Stripe uses this cookie to remember who you are and process payments without storing any credit card information on our servers. Know more | 1 year | First party |
__stripe_sid | www.gupshup.io | Stripe is used to make credit card payments in our application. Stripe uses this cookie to remember who you are and process payments without storing any credit card information on our servers. Know more | 30 minutes | First party |
These cookies enable the website to provide enhanced functionality and personalisation such as the website content being provided in the preferred language for your location. They may be set by us or by third party providers whose services we have added to our pages.
Name | Provider | Purpose | Expiry | Type |
---|---|---|---|---|
gs_lang_pref | www.gupshup.io | Remember the user's selected language version of a website. This allows the website to show content most relevant to that language. | Session | HTTP |
These cookies allow us to measure visits, traffic sources and engagement so we can improve the performance of our site. They help us learn which pages are the most and least popular and see how visitors move around the site. All information these cookies collect is aggregated and therefore anonymous.
Name | Provider | Purpose | Expiry | Type |
---|---|---|---|---|
_ga | www.gupshup.io | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. Know more | 2 years | HTTP |
_ga_# | www.gupshup.io | Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit. Know more | 2 years | HTTP |
_gat | www.gupshup.io | Used by Google Analytics to throttle request rate. Know more | 1 day | HTTP |
_gid | www.gupshup.io | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | 1 day | HTTP |
__utmz | www.gupshup.io | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. Know more | 6 months | HTTP |
__utma | www.gupshup.io | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. Know more | 2 years | HTTP |
initialTrafficSource | www.gupshup.io | Used by Google Tag Manager to track the initial traffic source of the visitor. | 2 years | HTTP |
We may use cookies, web beacons, tracking pixels, and other tracking technologies when you visit our website gupshup.io including any other media form, media channel, mobile website, or mobile application related or connected thereto (collectively, the “Site”) to help customize the Site and improve your experience.
We reserve the right to make changes to this Cookie Policy at any time and for any reason. We will alert you about any changes by updating the “Last Updated” date of this Cookie Policy. Any changes or modifications will be effective immediately upon posting the updated Cookie Policy on the Site, and you waive the right to receive specific notice of each such change or modification.
You are encouraged to periodically review this Cookie Policy to stay informed of updates. You will be deemed to have been made aware of, will be subject to, and will be deemed to have accepted the changes in any revised Cookie Policy by your continued use of the Site after the date such revised Cookie Policy is posted.
Cookie Policy (“Policy”) provides detailed information about cookies and JavaScript libraries, how we use them, and how you can manage them when you visit Gupshup website (“website”).
Cookies make it easy and efficient for you to navigate and interact with the Gupshup website. Cookies are small text files that we place on your device (e.g. computer or smartphone) when you visit our website. We will always ask your consent to set cookies e.g., to remember your preferences that are more relevant to you.
Cookies which are necessary for the website to function cannot be switched off.
You can at any time change or withdraw your consent from the Cookie Declaration on our website. (see "Cookie Consent" below in footer).
Learn more about who we are, how you can contact us and how we process personal data in our Privacy Statement.
Your consent applies to the www.gupshup.io domain only.
Cookies are used to make the user's web experience faster, convenient and personalised. For example you can select a language to view a website the first time you visit it. When you visit the website again it will save your preference.
Session cookies: these cookies remain in your browser during your browser session only, i.e. until you leave the website.
Persistent cookies:these cookies remain in your browser for a set period of time after the browser session expires (unless you delete them in advance).
First-party cookies:these cookies are created by us, that is the domain you are visiting (i.e. the website displayed in the URL window).
Third-party cookies:these cookies are created by domains other than the one you are visiting at the time.
When you first visit our website you will see our Cookie Declaration where you can see all the cookies. You can change or withdraw your consent at any time (see "Cookie Consent" below in footer).
If you have any questions regarding this Policy, you may reach our Data Protection Officer at dpo@gupshup.io
Added below language support for WhatsApp,
Bot developers for Line: With the release of Line Messaging API, all BOT API Trial Accounts are scheduled to be deleted. Please republish your bot according to new Line implementation, mentioned under Publish tab in My Bots section.
New tool for non-developers- Our Flow Bot Builder helps users create their bot messaging flow with a graphical editor.
API.ai tool is now available for developing your NLP/AI bot.
Gupshup Enterprise APIs (SMS,Voice and Email) are now available directly in the APIs section.
New channels added for publishing bots- Smooch.io and your website as a web widget.
Now you can access our services including the bot builder tool using your Facebook login credentials.
Now you can delete the dummy bots created for testing from the My Bots Dashboard.
You can now access Bot specific data from your Dashboard itself.
Introducing a hassle free bot development experience for users to instantly create bots using our pre-defined restaurant templates. Check out our blog to know more.
We are removing few redundant parameters, that were being sent when a callback happens to your bot (i.e. inbound message comes to your bot).
Following is the list of parameters.
However, we will continue to send following parameters. If you are using any of the deprecated parameters, we request you to use these alternatives.
You are requested to make a note of this and do the necessary changes immediately to your bot code to keep it working. Should you need any help, please feel free to send an email to devsupport@gupshup.io