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
    • Persona
    • 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
  • No trigger
  • Keyword
  • NLP
  • Catch All
  • Close
  • Location
  • CoBrowsing

Was this helpful?

  1. Bot basics

Triggers

Each scenario has a trigger type associated, this lets the bot know how it should trigger the scenario. Below is the different types of triggers that exist in Ebbot explained.

No trigger

A scenario without a trigger can not be directly entered. It can only be entered through a button click from another scenario or a transition.

Keyword

A scenario with a keyword trigger can only be entered by a visitor entering the exact keyword. This type of trigger is useful if you would like to add a shortcut to the scenario.

NLP

A scenario with NLP trigger is the most common one. NLP stands for Natural Language Processing and its one of the magic parts behind conversational AI. With this trigger you supply the bot a bunch of phrases or words it should "understand" and respond to. You specify the phrases that the bot will use to interact with the user. This allows the bot to comprehend user queries and respond accordingly, creating a more natural and fluid conversation flow.

Catch All

A scenario with the CatchAll trigger will be triggered any time the bot does not comprehend the user input. If there are no available NLP scenarios that matches the user input, catchall will be triggered instead. If EbbotGPT is active on the bot, the catchall works as a fallback if the GPT response would fail. Usually, there is only one CatchAll scenario in the root of the scenario tree.

Close

This trigger needs to be used in scenarios that should end the conversation. A scenario with the Close trigger is created by default (End conversation) and usually that is the scenario that should be used for this purpose.

Location

This trigger is used specifically for Messenger integrations, it prompts the user on their device to allow them to share their location.

CoBrowsing

This trigger is used specifically for CoBrowsing scenarios, where the user should be prompted to share their screen with the agent.

PreviousEntitiesNextTraining center

Last updated 1 year ago

Was this helpful?