008REPLYRAILCRM messaging router
/
CORE STACKPython 3.12UvicornSQLiteTelegram Bot APIBitrix24 APIDocker ComposeNginx● LIVE
008 / REPLYRAIL / BITRIX24 ↔ TELEGRAM
R
ReplyRailCRM MESSAGING ROUTER

The client wrote.
The owner already knows.

Telegram becomes part of the CRM process, not a separate window.

Open product Architecture
hard routing text + media + files soft + critical SLA
REPLYRAIL / CONTROL
ONLINE
DIALOGS · TODAY
ACTIVE ROUTESOFT SLA
Telegram ReplyRail Anna Bitrix24
LAST CLIENT MESSAGECan you confirm the delivery date?
waiting 18 min
SLA TIMER18 min
soft threshold active
01 / PRODUCT

One route connects the client, bot, manager and full history.

The manager stays in Bitrix24. ReplyRail works as the integration layer: receives Telegram events, resolves the route and preserves conversation context.

Deterministic routing

A client is bound to a specific bot and responsible manager.

Unified history

Text, images, documents, voice and other files stay attached to the route.

SLA alerts

Soft threshold warns; critical threshold escalates an overdue response.

Self-hosted

Database and file storage run inside the customer infrastructure.

02 / SLA ENGINE

SLA becomes visible before the client is lost.

Each project can define soft and critical thresholds. The service measures the age of the last inbound message and surfaces overdue conversations in a dedicated control loop.

soft: 15 min critical: 60 min
Demo Retail → Alex@sales_demo_bot · last incoming message
ON TIME02 min
North Studio → Anna@support_demo_bot · last incoming message
SOFT SLA18 min
Vector Labs → Sergey@lead_demo_bot · last incoming message
CRITICAL01:24
03 / ARCHITECTURE

An integration layer between the channel and the CRM.

Public ingress receives Telegram events; the API resolves the route, persists state/files and synchronizes the conversation with Bitrix24.

Telegram Bot APImessages · media · files
Python / Uvicorn APIrouting · SLA · webhooks
SQLite + files volumeroutes · history · attachments
Bitrix24 APImanager · CRM context
Nginx reverse proxypublic HTTPS edge
Persistent volumesdb-data + files-data
/api/healthlive health endpoint
Protected API docsadmin/API contour separated from public landing
04 / ENGINEERING STACK

The routing, storage and delivery stack.

01Python 3.12

routing backend

02Uvicorn

ASGI runtime

03SQLite

dialog + route state

04Docker Compose

service deployment

05Nginx

reverse proxy

06Telegram Bot API

inbound/outbound messages

07Bitrix24 API

CRM delivery

08Persistent volumes

database + files

05 / SYSTEM PRINCIPLE

The manager does not need another system.

ReplyRail absorbs routing, history and SLA complexity while keeping Bitrix24 as the team’s primary workspace.

OPEN REPLYRAIL