# Chatbot

GLIK defines **app types** as structured execution models that determine how workflows are built, how state is handled, and which system features are available. Each app type reflects an intentional tradeoff between control, complexity, and capability.

<details>

<summary>Summary</summary>

The Chatbot app type offers the most efficient way to deploy focused, stateless logic within GLIK Cloud. It is ideal for front-line automations, high-traffic Q\&A, and internal enterprise knowledge access.

It should be selected when the business need favors:

* Simplicity
* Predictability
* Speed
* Stateless interaction

For regulated processes, memory retention, or multi-step reasoning — escalate to a stateful app type.

</details>

GLIK Cloud currently supports four core app types:

* **Chatbot** (stateless Q\&A logic)
* **Agent** (stateful memory-driven logic)
* **Advanced Chat** (threaded conversational logic)
* **Workflow** (graph-based, condition-driven orchestration)

Understanding app types is essential to selecting the right execution mode for your enterprise use case.

***

### Chatbot App Type

<figure><img src="/files/nYKP1zHcTshljz7zngiL" alt=""><figcaption><p>Provides a streamlined interface for creating stateless LLM-based chatbots with simple configuration, ideal for Q&#x26;A, internal support, and lightweight enterprise automation.</p></figcaption></figure>

The **Chatbot** app type provides a stateless, single-turn execution model. It is optimized for lightweight prompt-response use cases such as FAQ bots, static data lookups, or simple internal triage systems.

Chatbot apps:

* Accept user input
* Run a single structured response generation via LLM or tool logic
* Return a response without storing memory across sessions

It is the **lowest-complexity** app type in GLIK, designed for rapid deployment and minimal state management.

***

### When to Use a Chatbot&#x20;

| Scenario                        | Use Chatbot?      | Recommended Alternative        |
| ------------------------------- | ----------------- | ------------------------------ |
| Static FAQs                     | ✅ Yes             | —                              |
| Single-step form assistant      | ✅ Yes             | —                              |
| Expense escalation or approvals | ❌ No              | Agent or Workflow              |
| Document summarization          | ✅ Yes (stateless) | Agent if multiple turns needed |
| Memory-aware triage bot         | ❌ No              | Advanced Chat or Agent         |
| Regulated or auditable process  | ❌ No              | Workflow                       |

### Enterprise Strategic Value

While simple, the Chatbot app type delivers real business value in enterprise environments:

<table data-view="cards"><thead><tr><th>Value Area</th><th>Benefit Summary</th></tr></thead><tbody><tr><td><strong>Cost Efficiency</strong></td><td>- Minimal model usage per request - No need for memory or session tracking</td></tr><tr><td><strong>Speed to Deployment</strong></td><td>- Build and publish chatbots in minutes via GLIK Studio - No orchestration or branching logic</td></tr><tr><td><strong>Security &#x26; Control</strong></td><td>- Statelessness lowers risk of memory leakage - Simple validation is easier to audit and log</td></tr><tr><td><strong>Business Use Cases</strong></td><td>- Internal tools (policy lookup, HR, IT) - Customer-facing Q&#x26;A (pricing, docs, support) - Embedded chat in SaaS apps</td></tr></tbody></table>

### Developer Considerations

Enterprise developers using the Chatbot app type should be aware of its **limitations and boundary conditions**:

#### ✅ What Works Well:

* Prompt + single output logic
* Frontline decision routing
* Integration with static data tools or API responses

#### ❗ Key Limitations:

* No persistent state or scoped memory
* Cannot use fallback blocks or conditional routing
* No branching logic

Developers should **avoid overloading Chatbots** with multi-step reasoning or dynamic memory use cases — escalate to Agent or Workflow when complexity rises.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.glik.ai/app-types/chatbot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.