Challenge
The school ran requests, approvals, and parent communication through chats and tables. A typical request sat for a week. Client sites launched one-off, without a shared ops loop.
Education / B2C · 2025
SEHRIYO — Telegram ops platform & school sites
SEHRIYO · education B2C
What’s included
We built a Telegram platform for staff and clients, wired Airtable + Make around 10 internal processes, and coordinated four client websites with the same integration playbook.
Outcome
Live platform for ~1,300 staff and clients. 10 processes automated. Approval cycle cut from 7 days to 2. Four client sites launched with integrations.
Challenge
Keep a school network running in messengers people already use — without losing status, owner, and deadline.
Review
- Mapped request types: who starts, who approves, who executes
- Timed where work died in chats and spreadsheets
- Scoped four client sites and a reusable integration pattern
Plan
- Telegram as the daily ops surface — no extra login for staff
- Automate the slowest internal loops first (approvals, routing)
- Reuse one website + CRM playbook across launches
- Human review only where a real decision is required
Ease of use
- Short Telegram flows instead of long web forms
- Visible status for every request — not “check the chat”
- Separate paths for staff vs clients, same source of truth
Look & feel
- Calm education brand on the public site
- Admin/bot screens designed around tasks, not decoration
Build
- Telegram bots/scenarios and role access
- Airtable as operational source of truth
- Make automations for routing, reminders, and handoff
- Four client websites + forms/CRM wiring
Technologies
- Telegram
- Airtable
- Make
- Web