"I'm running a '24/7 reply' chatroom, what do I do at night?"
A trap new operators fall into. The 24/7 promise looks commercially appealing but extracts costs from the operator, members, and Telegram itself. This post draws four boundary areas from operators' actual night policies + extended operation of chatroom data.
Hourly distribution, two policies side by side
The chart below simulates hourly auto-reply volume for two policies in the same room. Red bars = "24/7 promise" (members expect constant cover). Blue bars = "active-hours" policy. Hover any bar for the exact value.
Bottom line, don't promise 24/7
The most common advice for new chatroom operators: don't promise 24/7 replies. Instead:
- "Operator active hours: weekdays 9 AM ~ 10 PM"
- "Night / weekend replies: next business day"
- "Emergency: [separate channel]"
Fast replies (5~30 min) inside the stated window beat 24/7 with a 4-hour gap at night. Members are more satisfied with the former.
Area 1, operator sleep
Even with automation, a 1~6 AM reply pattern invades human sleep:
- Auto-reply firing 5 messages at 3 AM → operator who didn't mute notifications wakes up
- Review modes need operator decisions even at night
- A detection event at night demands immediate response
Boundary: even with automation, cut night-time automation (typically 10 PM ~ 7 AM) frequency by 90%+. Mute chatroom notifications at night.
Area 2, member expectations
A 24/7 promise inflates member expectations:
- "I asked at 2 AM and got no answer in 5 minutes" → complaint
- One night-reply event → all members expect the pattern
- The moment you stop, trust fractures
Boundary: state in chatroom intro / pinned message:
"Operator active hours: weekdays 9 AM ~ 10 PM. Night / weekend replies the next business day. Almost no auto-replies at night."
Expectation management beats trying to reply every time.
Area 3, bot-detection risk
Night-time replies are the strongest bot signal:
- Human operators almost never reply at 3 AM
- Equal volume at 3 AM and 3 PM = obvious bot
- Night-time tone identical to daytime (zero typos, zero emotion) = 100% bot
Boundary: night-time (1~6 AM) auto-reply frequency ≤ 5% + intentional latency + tone shift (tired vibe). Combine Replyer's [active hours] + [no-reply probability] + persona latency. Handling in responding when AI replies get spotted.
Area 4, Telegram suspension risk
Night-time patterns send direct signals to Telegram's automation detection:
- MTProto rate limits don't care about time of day, but internal detection (estimated) does analyze temporal patterns
- Night-time accumulation → report risk + Telegram automated review possible
- Suspension case analysis correlates with heavy night-time replies
Boundary: one of the seven safety lines in account ban prevention.
Operator active / rest grid (day × hour heatmap)
Below is a day-of-week × hour grid showing when an operator actually keeps auto-reply on. Dark cells = active, light cells = night-time at 5% frequency, near-black cells = fully off. You can recreate this with cfg.active_hours + per-persona active-hour mapping.
Four practical boundaries
Boundary 1, active hours
Run auto-reply only during the operator's natural active window:
- Weekdays 9 AM ~ 10 PM / weekends 11 AM ~ 9 PM (example)
- Outside active hours: auto-reply off, or 5% frequency
- Replyer's [Settings → active hours] or per-persona active hours
Boundary 2, frequency reduction
Rather than full off, 5% frequency reads more natural:
- Even human operators occasionally reply during a sleepless night (natural pattern)
- 5% = 1~2 replies per hour at night (vs 30 during the day)
- Set no-reply probability to 95%
Boundary 3, night-time tone shift
When night replies do fire, shift the persona tone slightly:
- Shorter replies (≤ 1 sentence)
- Tired phrasing ("I'll reply in detail tomorrow")
- Minimal emotion (intentional, reads natural)
Boundary 4, pre-disclosure
State the active hours in the chatroom intro:
- "Active weekdays 9 AM ~ 10 PM, almost no auto-replies at night"
- Members lower their night-time expectation
- Pre-empts detection events / complaints
When 24/7 actually makes sense
Edge cases that justify true 24/7 automation:
- Global chatroom members spread across timezones → night replies hit other people's daytime
- Business / consulting chatroom emergency replies have direct business value → operator rotates 1~2 weeks of night duty per quarter
- Multi-operator chatroom 2~operators rotate shifts to cover 24/7
Other regular chatrooms shouldn't promise 24/7.
Frequently asked questions
Q. I already promised 24/7. How do I change it?
Gradual:
- Chatroom notice introducing active hours (e.g. "Operator night rest, night-reply policy update")
- Cut night auto-reply frequency 30% → 10% → 5% over 2~4 weeks
- Collect member feedback, then settle
Most members accept reasonable changes. Strong objection ≤ 5% is normal.
Q. Does 5% night frequency hurt member satisfaction?
Almost no. Pre-disclosure + stated active hours + a natural tone when night replies do fire = trust intact. Across 12 chatrooms, those with explicit night policies scored noticeably higher member satisfaction than the 24/7-promise rooms.
Q. How do I protect my day job / family / sleep?
Night policy + chatroom notifications off (night) + webhook alerts for major events. Quarterly 1~2 week vacations also help. Time-protection flow in remote operator automation and burnout recovery guide.
Q. Does a business chatroom (customer service) need night-time replies?
No. Business chatrooms also state active hours + separate emergency channel (phone / email). "Auto-reply only at night for the chatroom, urgent matters via email" is standard. Promising 24/7 human reply accelerates operator burnout.
Q. How is "night" defined for a global chatroom?
By operator local time. Operator's 10 PM ~ 7 AM KST off → other-timezone members see no replies in that window. Global 24/7 operation needs multi-operator (per-timezone shifts) to be sustainable. Single operator + global 24/7 → fast burnout.
Q. Does fully turning off night auto-reply reduce bot suspicion more?
Yes. But total silence may break chatroom promises, so 5% frequency (1~2/hr) is the compromise. Full off also fine, just disclose in the chatroom intro.
Q. Difference between [active hours] and [no-reply probability]?
- [Active hours]: outside the window, auto-reply fully off
- [No-reply probability]: within active hours, skip a percentage of messages
Use both. Night off + a sliver of night active (e.g. 11 PM ~ midnight) with 95% no-reply probability = occasional natural night reply.
Next steps
To start auto-replies in your chatroom, download Replyer for your OS and follow the usage manual for the step-by-step guide.