UI/UX NGO Feedbacks: Enhance configurations and workflows

El issue no menciona archivos, pruebas ni puntos de entrada. Empieza por dividir los comentarios en cambios con alcance separado para la configuración, la recopilación, el editor de prompts y el flujo de trabajo de audio; después, identifica los puntos de entrada relevantes de la UI para un alcance acordado. Done debería definirse para cada alcance, ya que el issue combina actualmente cambios de UX, nuevas capacidades y compatibilidad con proveedores sin criterios de aceptación.

Summary

This issue tracks UI/UX feedback, workflow confusion, and feature improvement suggestions gathered from internal usage, NGO cohort discussions, and partner feedback sessions related to configurations, collections, evaluations, guardrails, and voice/audio workflows.

---

Configuration Creation Flow

• Improve UX for creating a new configuration from the Library page.
• Current flow involving:
  • loading an existing config
  • selecting + New Config from dropdown
    is non-intuitive and confusing.

Config ↔ Text Evaluation Navigation

• Improve navigation/UX between:
  • Configurations → Text Evaluations
  • Text Evaluations → Configurations
• Current screens expose too much information upfront, causing confusion:
  • Dataset / Create Dataset
  • Evaluations / Create Evaluation

---

Untitled Collection Placeholder

• Replace "Untitled Collection" with a better dummy/default naming mechanism.

Pending Collection Visibility

• While creating collections from existing documents:
  • show PENDING status immediately
  • prevent collection cards from disappearing until SUCCEEDED

Better Collection Creation Mechanics

• Improve UX for creating collections from documents.
• Current multiselect dropdown forces users to remember document names.
• Explore better interaction patterns:
  • drag-and-drop
  • searchable selection
  • document cards/list selection

---

Vector Store Visibility

• Move Vector Store ID/tool visibility to the primary view in Prompt Editor.
• Currently hidden behind the + Add Tool action, making discoverability poor.

---

Audio / Conversational AI UX & Features

Conversational Memory Layer

• Explore conversational memory layer for audio-heavy use cases.
• Need user-specific contextual memory persistence across multi-turn conversations.

Audio Cost Visibility

• Add predictable cost/token estimation for audio workflows.
• Current providers make token/credit usage difficult to estimate.

Multi-Provider Audio Evaluation Support

• Add support for multiple STT/TTS providers in evaluations UI:
  • Sarvam
  • ElevenLabs
  • Gemini
  • AI4Bharat
  • Bhashini

Better Provider-Specific Benchmarking

• Improve provider/model/language-specific benchmarking:
  • STT
  • TTS
  • Speech-to-Speech
  • RAG