| Use Case | Best Product | Key Capability |
|---|---|---|
| Chat assistant with memory | Agent Studio | Cognis memory, multi-turn sessions |
| Document Q&A | Agent Studio | Classic KB, RAG, citation output |
| Database query via natural language | Agent Studio | Semantic Model, Text-to-SQL |
| Complex relationship queries | Agent Studio | Knowledge Graph (Neo4j) |
| Multi-step business workflow | Agent Studio | SuperFlow or Manager Agent |
| Voice bot / phone agent | Agent Studio | Voice Agents (Realtime/Pipeline) |
| Full-stack AI app from a prompt | Architect | Text-to-App, agent orchestration |
| Programmatic agent creation | ADK | Python/TypeScript SDK, full control |
| Add AI to an existing product | API | REST endpoints, any language or stack |
Chat agents
Conversational agents answer questions, handle requests, and maintain context across a conversation. What’s required: a role, a goal, and instructions; a supported LLM (GPT-4o, Claude, Gemini, and others). Optionally, enable Cognis for cross-session memory so the agent remembers past conversations with the same user. Example prompt: RoleKnowledge search and document Q&A
Knowledge agents answer questions grounded in your organization’s documents, PDFs, URLs, or databases. What’s required: a Classic Knowledge Base with uploaded documents, RAG retrieval enabled on the agent, and optionally citation output mode. Supported sources: PDF, DOCX, TXT, CSV, websites (live crawl or snapshot), SharePoint, S3, Google Drive, Notion, Confluence. Use a Knowledge Graph instead when your data has complex relationships (org charts, product dependencies, compliance rules) where entity connections matter as much as the text. Use a Semantic Model instead when your data lives in a relational database and users need to query it in plain English.Database query (Text-to-SQL)
The Semantic Model translates natural-language questions into SQL queries against your structured data. What’s required: a Semantic Model connected to a database (PostgreSQL, MySQL, BigQuery, Snowflake, and others), plus a schema definition covering tables, columns, and business glossary. By default, the Semantic Model generatesSELECT queries only (read-only). Write access is configurable for internal tooling.
Multi-step workflows
Workflows automate sequences of actions: fetch, analyze, decide, act. Lyzr provides two orchestration modes: Manager Agent is dynamic. The manager agent reads the task and routes it to sub-agents based on context. Use Manager Agent for conversational, branching logic where the execution path varies by input. SuperFlow is deterministic. You define a directed acyclic graph (DAG) of nodes (LLM calls, HTTP requests, code, conditionals, human approvals) and the workflow runs exactly the steps you defined. Use SuperFlow when execution order must be guaranteed, when you need exactly-once side effects, or when the workflow touches financial or compliance-sensitive systems.Voice agents
Voice agents handle phone calls, voice assistants, and real-time speech interfaces. Two engine modes:- Realtime: sub-500ms latency, streaming ASR + TTS + LLM. Best for live phone calls.
- Pipeline: standard latency, higher accuracy. Best for asynchronous voice UX.