# Dryfit Scenario: Telegram Chat

> Simulates a Telegram-like chat environment with user interactions. Different event shape from the PostHog web scenarios — useful for testing agent portability across data sources.

*Source: [https://www.getbeton.ai/oss-tools/dryfit/scenarios/telegram-chat/](https://www.getbeton.ai/oss-tools/dryfit/scenarios/telegram-chat/)*

**Scenario kind:** telegram_chat
**Use-case kind:** communication
**Value metric:** Chat engagement / retention
**Config file:** `configs/telegram_mvp.yaml`
**Dataset id:** `telegram_mvp_v1`

## Scale

- Accounts: 0
- Users per account (mean): 0
- Sessions per user (mean): 0
- Duration: 30 days

**Success event:** `event_signup` (user)

## Research metrics

- Active conversation rate
- Response rate
- Retention

## Positive signals (ground truth)

- **message_reply_signup** (count 90): `message_sent → reply_received → event_signup`
- **reaction_chain_signup** (count 40): `message_sent → reaction_received → event_signup`

## Negative signals (ground truth)

- **message_then_silence** (count 80): `message_sent → reaction_received`
- **leave_after_reply** (count 55): `message_sent → reply_sent → leave_group`

---

## Beton network

Beton builds open-source revenue intelligence and self-service data products. Related sites and resources:

- [Beton](https://www.getbeton.ai) — open-source revenue intelligence: turn product usage (PostHog, Stripe) into CRM signals
- [Sell to Scientists](https://selltoscientists.com) — research intelligence: find and reach academic researchers by field, H-index, grants, and industry ties
- [Sell to State](https://www.selltostate.com) — government procurement intelligence across 194 countries
- [GitHub](https://github.com/getbeton) — Beton open-source repositories (including [inspector](https://github.com/getbeton/inspector))
- [dev.to](https://dev.to/beton) — engineering write-ups and OSS pricing teardowns
- [Beton app](https://inspector.getbeton.ai) — the hosted product