31 lines
846 B
Markdown
31 lines
846 B
Markdown
# Track 15 - Telegram Chat
|
|
|
|
Status: `implemented`
|
|
|
|
## Scope
|
|
|
|
- real Telegram Bot API webhook
|
|
- one persistent thread per `chat_id`
|
|
- 2-way text chat
|
|
- separate `Telegram` page in `/operator`
|
|
|
|
## What changed
|
|
|
|
- `telegram-adapter-service` now owns Telegram threads and thread messages
|
|
- new thread/message routes exist under `/integrations/telegram/threads/*`
|
|
- inbound messages reuse the same thread and linked interaction
|
|
- a closed Telegram interaction is reactivated on new inbound activity
|
|
- operator replies go through Telegram `sendMessage`
|
|
|
|
## Out of scope
|
|
|
|
- Telegram voice/video calls
|
|
- media/file workflow
|
|
- admin UI for bot setup
|
|
|
|
## Acceptance focus
|
|
|
|
- first inbound message creates thread + interaction
|
|
- repeated inbound on the same `chat_id` reuses the same thread
|
|
- operator can claim and reply from the dedicated `Telegram` page
|