Skip to content

BRD-003 Chatbot Website Control

BRD – MachineAvatars Chatbot Website Control (Search & Navigation)

Product: MachineAvatars
Feature: Chatbot-Driven Website Search & Page Navigation

1. Background & Problem Statement

  • Users often struggle to find the right content through traditional menus or search bars.
  • The MachineAvatars chatbot can act as a single interaction layer to guide users directly to relevant information.
  • Enabling the chatbot to control search and navigation improves discovery and task completion.

2. Objective

Allow the MachineAvatars chatbot to perform website search actions and navigate users to relevant pages based on user intent.

3. Scope

In-Scope

  • Trigger website search using chatbot commands where a search feature exists.
  • Navigate users to relevant internal pages via chatbot actions.
  • Actions are limited to predefined, allowed website routes.

Out-of-Scope

  • External website navigation.
  • Creating or modifying website content.
  • Deep form submissions or transactional actions.

4. User Personas

  • End User: Uses natural language to find information or pages.
  • Admin: Configures searchable sources and allowed navigation routes.

5. High-Level User Flow

  1. User asks the chatbot to find something or go to a specific page.
  2. Chatbot determines whether search or direct navigation is required.
  3. If search is needed, chatbot triggers the website’s search functionality.
  4. If navigation is needed, chatbot redirects the user to the relevant page.
  5. User lands on the expected page or search results.

6. Functional Requirements

  • FR-1: Chatbot shall detect user intent for search vs navigation.
  • FR-2: Chatbot shall trigger the website’s native search functionality when available.
  • FR-3: Chatbot shall redirect users to relevant internal pages based on intent.
  • FR-4: Navigation actions shall only target pre-approved internal URLs.
  • FR-5: Chatbot shall provide a confirmation or explanation before navigation, where applicable.

7. Constraints & Non-Functional Requirements

  • Navigation actions must be fast and not disrupt the chatbot session.
  • Search and navigation must respect existing website permissions and access rules.
  • Chatbot must not navigate users to incorrect or unrelated pages.

8. Acceptance Criteria

  • Given a user query requesting information, when a search is applicable, then the chatbot triggers the website search.
  • Given a user request to go to a page, when the page exists, then the chatbot navigates the user to that page.
  • Given a request outside allowed routes, when detected, then the chatbot declines and explains the limitation.
  • Given a navigation action, when executed, then the chatbot session remains active.