Concourse & Jira DC Portal

Description:

As we transition from "Ask Concourse" as a simple chatbot rooted in knowledge base retrieval to a robust, extensible agent framework, it is essential to revisit and update the terminology and naming conventions for our features and agents. The current nomenclature does not fully capture the expanded capabilities and modular design of the new agent-based architecture.

This initiative proposes a comprehensive review and rebranding of the agent names and the overall feature terminology to ensure clarity, scalability, and alignment with our product vision. The goal is to ensure each agent's name clearly communicates its core function and value to users, while also supporting future extensibility as new agent types are introduced.

Key agent roles under review:

• Q&A Agent: Handles natural language question answering and acts as the evolution of original the Ask Concourse. This agent will be responsible for providing accurate, context-aware responses to user queries.

• Asset Agent: Focuses on advanced search and personalized recommendations, powered by the introduction of a Knowledge Graph. This agent will help users discover relevant content, documents, and knowledge assets efficiently.

• Action Agent: Manages direct actions such as user administration, task automation, and system changes, demonstrating the MCP protocol pattern for secure, auditable agent-initiated changes.

• Data Agent: Specializes in reporting, analytics, and predictive insights, enabling users to surface trends and metrics seamlessly.

Objectives:

• Evaluate and update all agent names to better reflect their scope and future direction.

• Align terminology across the platform to ensure a consistent and intuitive user experience.

• Communicate the shift from a monolithic chatbot to a modular, agent-driven architecture.

• Support marketing, documentation, and onboarding materials with clear, differentiated agent descriptions.

Key People:

• Product Manager: Arman Dhar

• Copy: Amanda

• UX Team: Art Sanchez, Augustina Figuerido

• Technical Architect: Minal Dharod

Next Steps:

• Audit existing agent names and associated documentation.

• Propose new names/descriptions and collect feedback from stakeholders.

• Update all references to agent names across product UI, help content, and training resources.

• Plan for future extensibility as additional agent types are envisioned.