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
  • Welcome scenario
  • Catchall scenario

Was this helpful?

Scenarios

PreviousTraining centerNextCards and syntax

Last updated 1 year ago

Was this helpful?

The scenario is where the magic happens since a bot is built entirely on scenarios. Each chatbot is made up of "scenarios". You build a chatbot by combining different scenarios which in turn allows Ebbot to understand and have a human dialogue with the user. When a user says something, Ebbot matches the user expression to the best scenario in your bot and return the proper reply/action

Welcome scenario

All bots have one welcome scenario which is the first message that gets triggered when a conversation has been started. It's marked with a red color in our studio and you modify it as you like.

It's a good idea to add a bunch of relevant buttons that could act as a conversation starter and let the user know what kind of knowledge the bot is trained with.

Catchall scenario

A catchall scenario is a scenario that it's trigger if the bot couldn't match the phrase against another trained scenario. You should always consider to have human handover in the catchall scenario so that the user can have an answer on their questions and have good experience. If it's outside office hours you should have a flow that creates a ticket or send an email to you so that you don't loose anything.

The catchall scenario is marked with a blue color in the studio.