MeetCal: Why I Built Calendly Inside Telegram
The stream that leaves its bed loses its force.
scheduling in 2024:
Telegram message: "can we chat?"
│
▼
"here's my calendly" ──→ [link]
│
▼
[new tab opens] ← the channel is broken here
│
▼
[browser calendly]
│
▼
[picks time]
│
▼
[confirmation email]
│
▼
back to Telegram
Five steps to leave the conversation and return to it. Each step is a chance to lose the person. Each step is friction.
Friction compounds.
The question was simple:
Why does scheduling require leaving the place where the conversation already lives?
The meeting was decided in Telegram. The scheduling happened elsewhere. This is backwards.
scheduling inside Telegram:
"can we chat?"
│
▼
[mini app opens in chat]
│
▼
[picks time — same screen]
│
▼
both parties confirmed
│
▼
still in Telegram
The stream stayed in its bed. The force remained.
The simplest products are the ones where you ask:
Why does this require leaving the place we already are?
If the answer is “no reason” — build the bridge.
One hundred and fifty million scheduling events happen every month. Many of them are arranged in Telegram first. None of them needed to leave.
They just didn’t have a reason to stay.
— Ilao Dzindin