Add a Button
A button is, most often, a URL that is included beneath the response body. It can also provide another response instead of a link. When the button is a URL, the button text is underlined. Button formatting is the same for all channels.
In most cases, buttons are used to link URLs so that the end user does not have to view the extended text of a URL.
Step 1: Locate the response you wish to update, and select “Edit” in the top right corner.
Step 2: Locate the “Buttons” area within the response window and select “Add Button…”.
Step 3: Add a button label. This will be visible to your end user. We recommend using a call to action as often as possible.
Step 4: Select what type of button you’d like to add. Most often, you’ll likely be selecting “URL”. Click here to see the list of definitions below.
Step 5: Enter the URL into the final container. Note: The URL must begin with https:// or http://.
Step 6: To add another button, jump back to Step 2 and follow the same steps.
A button can also be linked to provide an existing response within the dashboard. These are managed like quick replies.
Step 1: Locate the response you wish to update, and select “Edit” in the top right corner.
Step 2: Locate the “Buttons” area within the response window and select “Add Button…”.
Step 3: Add a button label. This will be visible to your end user. We recommend using a call to action as often as possible.
Step 4: Select what type of button you’d like to add. To link a button to another response, you’ll want to select “Response Name”.
Step 5: Select the response name of the response copy that you’d like to populate when the button is selected. Note: Each response is assigned a unique response name. This can be found within the “Response Name” column of the dashboard. The button label should always relate to the subject of the response you’re linking.
Step 6: To add another button, jump back to Step 2 and follow the same steps.
- URLs: The button label should be a call to action.
- Examples: Purchase Tickets, Learn More, Contact Us
- Responses: The button label should always be related to the subject of the response you are linking to.
- Example: “View the Schedule” should provide a schedule response
- Buttons should be used as supporting information. The user should be able to receive major details or information from the response copy.
- The URL must begin with https:// or http://.
- The Web/App Channels can support a maximum of 7 buttons.
- We typically recommend starting with no more than 2.
- The Facebook Channel can support a maximum of 3 buttons.
- Response Name: This should be used when you’d like the user to receive copy from another response within the dashboard.
- Input Text: Used very sparingly. Used for a press of a button resulting with an input sent through NLP.
- URL (Default): This should be used for all URL additions.
- URL (Same Tab): Likely unused. Only to be applied when overriding default settings and having the link open in the same window.
- URL (New Tab): Likely unused. Only to be applied when overriding default settings and having the link open in a new window.
- URL (iFrame): This should be used when you’d like to iFrame a website within the AI, to prevent the user from leaving the chat. It is important to test this feature, as not all websites format correctly.
Last modified 7mo ago