Approach: Improve Bot Discoverability with Search and Team Scoping

Vincent Jay

— 1 min read

What:

  • Add a persistent search input at the top of the bot directory.
  • Search should match:
      • Bot name
      • Short description
      • Tags / keywords
      • Owner or team (optional enhancement)

2. Role-Based Bot Filtering 

What:

  • Automatically filter bots based on the user’s authenticated role, team, or department.
  • Example:
      • Engineering users → DevOps, CI/CD, debugging bots
      • Support users → Customer insights, ticket analysis bots
      • Product users → Analytics, roadmap, insights bots

Why:

      • Eliminates irrelevant bots by default
      • Reduces cognitive load and decision fatigue
      • Reinforces “this tool is for me” feeling

3. Category-Based Bot Filtering

What:

Group bots into clear, functional categories based on their primary use case, allowing users to browse and filter bots by domain (similar to GPT Assistant categories like Marketing, DevOps, Research, etc.).

Example:

      • Engineering / DevOps → CI/CD helpers, infrastructure monitoring, debugging bots
      • Marketing → Content generation, campaign analysis, SEO bots
      • Research → Data analysis, summarization, insight-generation bots
      • Support → Ticket analysis, customer insights, response drafting bots
      • Product → Analytics, roadmap insights, user feedback bots

Why:

      • Improves discoverability when users don’t know the bot name
      • Encourages exploration of available tools by domain
      • Creates a familiar and intuitive mental model
      • Scales cleanly as the number of bots increases

4. Default Views: Favorites & Recently Used 

What:

  • Provide quick-access sections for bots the user interacts with most, surfaced automatically above the main list.

Example:

      • Favorites → Bots explicitly pinned by the user
      • Recently Used → Last 5–10 bots accessed

Why:

      • Reduces repeated searching for commonly used bots
      • Optimizes for daily workflows, not just discovery
      • Creates a personalized experience with minimal effort

Read more

How do you setup identity or age verification so that only certain locations need to get verified?

Answer: Use Location-Based Identity Verification. This is enabled via the locationRestrictions.requiresVerification attribute in your application configuration to define which countries and regions require verification. Summary Token of Trust now supports location-based verification requirements through the locationRestrictions configuration. This feature allows you to specify which geographic locations (countries and regions)

By darrin