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
With the Flow Bot Builder, you have the option to view, add and edit the script of your bot. In this guide we will look at how can you
In order to view the script, you need to click on the desired node in the “Tree View” section and the associated script will be displayed in the “Script Designer” section on the right. The Script Designer will show the script of the selected node as well as the nodes above in that flow.
For example:
In the image below the last node is selected and the complete script of that flow is being displayed.
You can add either a bot state or a user state depending upon the node you choose. To do so, select a node and then in the “Script Designer” click on either “Bot Says” or “User Says” to add. This will then appear as a new node in the “Tree view” section.
NOTE:
While improving your script you may want to
1. Add more to the end of the flow.
OR
2. Add more in the middle of the flow.
Adding to the end of the flow:
Let's say you have a quick reply in the script like below
Now you want to add the bot responses to the button selection of the quick reply. You can select the user state node and then click on “Bot Says” to add the bot response.
The final result will be like
Similarly, you can click on the other user state and add a bot state to it and so on.
Adding in the middle of the flow:
Let's say you have a script like this one
clicking on “Watches” will send a quick reply asking for the brand but let's say you want to add one more quick reply asking for the gender before sending the quick reply for the brand.
To do so, you can simply:
to drag away: click on the node and drag your mouse. You will see various nodes highlighted using the dotted box.
These are the nodes to which you can drag and drop the selected node.
to add: simply follow the example on the top to add a quick reply for asking the gender.
to drag back: just select the node that you had moved and drag it back below the response of the gender quick reply
thus by using drag and drop feature, you can add to the middle of the flow.
You can also edit the script at any given point. In the “Script Designer” section hover or click on the down arrow button of the corresponding state. It will display options to
NOTE:
Sample of the edit screen for a quick reply
You can add variations to the intents from the users or to the responses from the bot which are of type text.
Adding variations to user intents
All the nodes that you have scripted as “User says” are treated as the user intents by the script and the NLP engine. There could be a case where you would like to add some variations to those intents. You can do so by adding them in the variation section
Thus the NLP engine will pick that state by comparing the main intent and the variations.
Adding variations to bot responses
You can randomise the responses sent by the bot to the user.
Just add the variations in the section and system will pick one of the provided responses
Using Flow Bot Builder to create an extensive conversational bot with multiple flows can quickly become complicated. Take a look at below tree structure of a bot with multiple flows
In the above image there multiple flows a user can go to and to manage all these in a single window becomes difficult. Hence we have introduced bot flows.
Few benefits of Bot flows:
How to create a flow:
You can create a new flow by expanding the Bot flows icon and clicking on the “Create a flow” button present on the menu items on the left-hand side of the screen.
Once you have entered a name for the flow you will be taken to edit the script of that flow. You can then add/edit/delete the content of the flow using the usual steps of the Flow Bot Builder.
Name of the flow should be alphanumeric and should not contain any space or special character.
Example:
I have a bot that has 6 different options(flows) for the user.
Now, I can go ahead and create 6 different flows for each of these options.
“main” is the default flow and is the starting point for the bot. Also, the flow that is being edited is shown as active using the green dot. Also, the bottom bar indicates which flow is in current view.
How to link a flow
Select the node in the tree view that should call a flow. Then click on the “Link” icon. You should see the option as “Call another flow”
Once you click on the “Call another flow” you will be presented with an option to select the flow that the bot should go to
after the selection, the tree view will be updated with a sign representing that the node is calling another flow.
How to test a flow
The web widget for testing will display a drop down to select the flow you want to test
and then you can click on the “GO” button.
You can even select to test the complete bot by selecting the first item on the list, which is your botname.
Create a new flow via Export
In case your bot flow becomes huge where the script and tree become unmanageable, you can break your existing flows into new flows, right from the script designer. When you click on this icon
you will be prompted to enter a flow name and decide if you wish to only create the flow or create and call the flow from that point.
When you create and call, the Call is made from the previous node so that the new flow starts with your selected node.
With export, a large flow can be broken into smaller flows, and this decision need not be taken up front, when designing the bot.
NOTE:
As stated earlier, please ensure that your flows have a Return state appropriately set at the end of the flow.
State-specific fallback message
There are instances when the generic fallback response doesn?t convey the error in user response. The bot needs to be specific about what user input it exactly needs. For e.g. if the bot is expecting a numeric 4 digit input and the user doesn?t provide exactly that, the generic sorry message doesn?t usually tell the user the specific error and what?s expected.
In order to make conversations even more natural and smooth, you can now add fallback messages that are relevant to that bot state so as to guide the user to reply with a more appropriate response, for that bot query.
When you click on this icon
Note: For states where this isn?t set, the generic fallback response will be triggered.
Shareable Bot flow links
Once you publish your bot to a Facebook messenger page, you will automatically get unique messenger links generated for each individual bot flow. When you click on the messenger links next to your flow names
you will see a popup which gives you a messenger link.
This link takes users directly to that specific bot flow. This is useful when you?ve created flows with a specific functionality or goal that can be shared via marketing campaigns to get users to interact with that specific flow / section of your bot. These flows could be specific to leads, specific promotions an updates, new functionality, etc.
NOTE:
Please ensure that each bot flow calls or returns to main or other flows in your bot so that the conversation flows smoothly and users don?t get lost.
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