LogoLogo
  • Introduction to the Ebbot Platform
  • Ebbot Platform
  • Bot basics
    • Scenarios
    • Entities
    • Triggers
    • Training center
  • Scenarios
    • Cards and syntax
      • File Input
      • Text card
      • Input
      • Buttons
      • Image
      • File
      • Carousel
      • Location
      • List
      • Contact Agent
      • Rating request
      • Custom component
      • CoBrowsing
    • Transition
    • Card properties
  • AI Insights
    • Setup and Configuration
    • Using the Insights Dashboard
  • EbbotGPT
    • Knowledge
      • Data source transformer
      • Source types
        • File
        • Website scrape
        • Docx file
        • TOPdesk API
        • Sitevision API
        • SharePoint API
          • Create app with Sites.FullControl.All permission in Azure
          • Ebbot SharePoint Postman Guide
        • Confluence API
    • Configurations
    • GPT Evaluation
    • Embedder models
    • EGPT models
  • Custom vocabulary
  • Tutorials
    • Create your first scenario
      • Select a trigger
      • Add bot responses
  • Data Object
  • Release notes
  • For developers
    • Ebbot SDK
    • Safe Exchange API / Vault
    • Subdomain manager
  • EbbotGPT API
  • Chatbot & Live chat
    • Install chat widget
    • Chats API
    • Chat widget API
    • Datasource API
    • Sales tracking for live chat
    • Webhook
      • Incoming webhooks
      • Outgoing webhooks
    • SMS API
      • Authentication
      • Send SMS
      • Errors
      • Encoding
    • Python components
    • Intent detection (NLP)
  • Product guides
    • Product data feeds
    • Install guide
    • Product guide events
      • Product guide user events
      • Received events
      • Send events
    • API & webhooks
    • GA4 integration
    • Klaviyo integration
  • Messenger marketing
    • Install popup
    • API & webhooks
  • For chat agents
    • Ebbot Chat
      • Settings modal
      • Queue
      • Topbar Stats
      • Menu
        • Power-Ups!
        • Quick Replies
  • INTEGRATIONS
    • Ebbot Live Chat in Zendesk
      • Setup guide
    • Active Directory - SAML
    • Configure SAML in Azure
Powered by GitBook
On this page
  • Add a text response
  • Save and test
  • Train the bot
  • Get to know the user

Was this helpful?

  1. Tutorials
  2. Create your first scenario

Add bot responses

PreviousSelect a triggerNextData Object

Last updated 1 year ago

Was this helpful?

Now, we will add the bot's responses. First, click "add bot responses" in the top of the right panel.

In this example we will use two of the most common card types: Text and Input String.

Add a text response

Click the "Text" bot reaction in the left panel to add it to the scenario, then provide some text that the bot should send.

Save and test

Scenarios that are published will be active when talking to the bot, the bot will not play unpublished scenarios. Make sure that the "Published" toggle is on, and hit "Save scenario".

Train the bot

When NLP scenarios are added or updated in Ebbot, the bot needs to be trained. When saving your new scenario, it will change color along with the "Train Bot" button in the bot builder. Press "Train Bot" to run the training, this activates your new scenario and makes it react to the phrases you previously added. Training may take up to 3 minutes.

Training is needed when:

  • A new NLP type scenario is created

  • The list of NLP phrases is edited in a scenario

When the training is completed you will get a success notification in the app. As soon as it is done, you should be able to trigger your new scenario.

By clicking on the message bubble in the upper right corner you are always able to start talking with the bot and to test your flow.

Get to know the user

Now we should let the bot ask a question back to the user about their favorite color.

Bot responses are sent to the user in the order they are placed in the scenario, so we will add the question after the first text about the bot's favorite color.

Head back to the scenario and drag the "input string" card from the left and place it under the first text card. This time we will use the input string. This allow us to ask a question and then store the answer in a variable. The output variable name can be named anything but in this case we'll name it color.

Once a variable has been defined you can always reach it at any time during the conversation. To do so we can for example add another text card under the input string, repeating what the user just told us:

The result is that we now have the users favorite color stored in the data object and can use it throughout the conversation. In this case we use it immediately in the following bot reaction when given to us: