> For the complete documentation index, see [llms.txt](https://docs.crxtoken.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crxtoken.xyz/page-4.system-architecture/4.5-application-layer-web-and-bot-interfaces.md).

# 4.5 Application Layer: Web and Bot Interfaces

The application layer is intentionally thin with respect to business logic; it focuses on presentation, interaction, and context. The web dashboard organizes information into views that answer specific questions: “Where do I stand today?”, “How has my situation changed?”, and “What are the key risks or opportunities right now?”. Visualizations are chosen not to impress but to clarify, with a preference for simple, interpretable charts and narrative summaries.

The Telegram bot provides a complementary experience. Rather than attempting to replicate the entire dashboard inside a chat window, it focuses on a small number of high-impact interactions: on-demand summaries, weekly or monthly digests, and push-style alerts when important thresholds are crossed. This design acknowledges that many users will interact with their credit information in short bursts, at moments of context—during commutes, at checkout, or when making a financial decision—and that a conversational surface is often the fastest way to deliver value.

Both interfaces respect user-configured preferences regarding notification frequency, depth of detail, and tone. They interact with the same backend services and rely on the same analytics results. As a result, a user who reads a weekly digest in the bot and then opens the dashboard will see a coherent, consistent story rather than two disconnected interpretations of their data.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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.crxtoken.xyz/page-4.system-architecture/4.5-application-layer-web-and-bot-interfaces.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.