How to set up scheduled messages in Telegram step by step?

Why Scheduled Messages Matter in 2026

Telegram’s scheduled-message feature lets you queue any text, media, poll or paid-post up to 366 days ahead without keeping the device online. Unlike reminders, the message is sent by Telegram cloud servers, so it counts as a normal outgoing message for rate-limit, read-status and monetisation analytics. This article walks through the exact taps, the hidden performance knobs, and when not to rely on the queue.

Feature Boundary: What Can and Cannot Be Scheduled

As of Telegram 9.3.3 (Jan 2026) you can schedule:

• plain text, hyperlinks, spoiler tags
• single or grouped photos/videos up to 4 GB (8 GB beta)
• voice chats start link, live-stream URL, Quiz or regular poll
• paid-collection posts (the price is locked at schedule time)

You cannot schedule: voice/video messages, live video stickers, or messages inside an E2EE Secret Chat because those require per-device keys. Bot messages are also excluded; use /sendlater style third-party bots instead.

Performance & Cost Benchmark

Metric to watch: delivery drift—the delta between the chosen time and the actual server timestamp. On a 100 Mbit uplink and 30 ms RTT, 95 % of schedules land within ±1 s; on 2G the tail spreads to ±7 s. Cloud queue is free, but each delivered message still burns your account’s send quota (30 msg/min for groups <1 k members, 20 msg/min for channels >1 k). If you breach the cap, Telegram quietly holds the message until the next rolling minute, extending drift.

Measurement method

Enable Developer Settings (tap Settings → Advanced → hold App Version until “Debug” appears). Toggle Show Delivery Timestamp. After the message appears, long-press it → Copy Link; the msg_id= URL contains Unix epoch in milliseconds—compare with your original schedule.

Step-by-Step: Mobile (Android & iOS)

1. Open any cloud chat (private, group, channel).
2. Type or attach your content but do not press Send.
3. Long-press the blue airplane icon (Android) or tap once and choose Schedule Message (iOS).
4. In the date-picker wheel, scroll to the target day; tap Next.
5. Set exact hour-minute-timezone. Telegram uses the device TZ at schedule time; it does not auto-adjust for future DST.
6. Tap Send on <date>. A tiny clock badge appears next to the draft in the input field—this is your confirmation.

To edit before dispatch: tap the clock badge → Reschedule or Edit. After it leaves, edits are impossible.

Step-by-Step: Desktop (Windows / macOS / Linux)

1. Right-click the Send button (or press Ctrl+Shift+S).
2. A calendar sidebar slides in; pick date & time.
3. Click Schedule. The message moves to the Scheduled folder in the left panel.

You can bulk-select up to 100 messages inside the folder and drag them to a different time slot; useful for serial course drops.

Web Client Caveats

Telegram Web K and Web A support scheduling, but the queue is held in the browser’s IndexedDB until you stay online. If you close the tab before dispatch, the message is lost with no warning—mobile/desktop clients sync the queue server-side. For reliability, always finalise on a native app.

Scenario Mapping: When Scheduling Saves Money

Global product launch

A hardware startup with 120 k channel subscribers used to pay three moderators to stay up for 48 h to cover time-zones. By batch-scheduling 18 posts (teaser, spec sheet, purchase link) they cut labour cost USD 1 200 and still hit ±2 s accuracy across regions.

Education drip feed

An online teacher runs a 30-day Python boot-camp. She pre-records daily 5-minute videos (≤200 MB each), schedules them at 08:00 student local time, and locks each behind a cheap paid-collection (0.5 TON). Students feel “live” pacing while she’s on holiday.

Checklist: Best-Practice for High-Volume Schedules

• Keep individual chat load ≤ 20 msg per rolling minute.
• Pad 60 s between paid-collection posts; Apple IAP backend sometimes serialises large bundles.
• Export your queue before vacation: Settings → Data & Storage → Export → choose “Scheduled messages” → .JSON. If you lose the device, you can re-import via a small script using TDLib.
• For 10 k+ member groups, enable Slow Mode (Admin → Permissions → 30 s) to prevent your own schedule from drowning chat.
• Always spot-check DST: Telegram records the literal hour number you picked. A 9:00 schedule in London will fire at 9:00 after March shift, not 8:00 UTC.

Non-Applicable Checklist: When You Shouldn’t Schedule

• Emergency alerts—drift may be 7 s on poor networks.
• Secret Chats; no server queue by design.
• Messages that need mid-day price updates (crypto rates, airline tickets) because you cannot auto-edit.
• Live event commentary where audience interaction changes the next message; use real-time bot flow instead.

Working with Bots & Third-Party Tools

Bot API 7.6 has no native scheduleDate field. If you need conditional sends (e.g., weather-dependent), let your bot post privately to a “log” channel, then you manually forward-schedule. Never give bot admin write rights to main channel; a mis-timed loop can burn your 30 msg quota in seconds.

Troubleshooting Quick Map

Version Differences & Migration Notes

Telegram 9.2 allowed only 100 future messages per chat; 9.3 lifts the cap to 1 000. If you upgraded from 9.2 and see “Quota exceeded,” delete old schedules once—they are grandfathered but count against the new limit.

Verification & Observability

For compliance audits you may need to prove a message was pre-scheduled. Turn on Export with Metadata before any campaign; the resulting .JSON contains "scheduled_at":<unix_ts> and "sent_ts":<unix_ts>, forming an immutable delta record.

The 2026 Roadmap

Public beta leaks (via TON Society AMA, Jan 14) hint at conditional triggers in 9.5: schedule if URL returns HTTP 200, or if TON payment arrives. Until then, master the manual queue and you’ll already outperform 90 % of channels on timeliness and labour cost.

Scheduled messages in Telegram are free, precise to the second under good networks, and integrate with monetisation. Use them when the content is final, the timing is known, and the chat is cloud-based. Otherwise, stick to real-time or bot flows.

Case Study ① – Indie Game Studio (3 k channel)

Goal: Build hype for mobile roguelike launch across US, EU, SEA without night shifts.
Setup: Pre-rendered 14 trailers (≤90 MB) and 28 GIF teasers; scheduled one post every 8 h for 2 weeks, locked last 3 trailers behind 1 TON paid-collection.
Result: 42 % CTR on purchase link, zero overtime pay, median drift 0.8 s.
Revisit: Studio initially forgot DST; two posts fired 1 h late in São Paulo. Re-imported corrected JSON and ran 30 s apology poll—audience engagement spiked 18 %.

Case Study ② – Regional News Desk (450 k group)

Goal: Deliver morning digest at 06:00 sharp for 12 cities while editors sleep.
Setup: RSS-to-Telegram bridge writes drafts into private channel; night editor bulk-schedules 12 localised editions at 05:55 device time, enables Slow Mode 30 s, tags each with city-emoji.
Result: 98 % on-time delivery, unsubscribe rate down 7 % quarter-over-quarter.
Revisit: During a cellular outage drift hit +14 s. Desk now keeps a 4G failover tablet logged in; if “Scheduled” badge stays >30 s past due, editor on-call receives Pushover ping.

Runbook: Monitoring & Rollback

1. Alert signals

• “Recent Actions” shows >30 outbound in one minute
• Drift >10 s for three consecutive schedules
• Paid-collection stuck “Waiting for confirmation” >15 min

Any one trigger warrants inspection.

2. Locate fast

1. Open Scheduled folder, sort by ascending time.
2. Long-press first overdue item → Copy Link → paste in browser; note msg_id.
3. Settings → Advanced → Recent Actions → filter by your UID, check for red “Rate limit” tag.

3. Rollback / mitigation

• Quota hit: wait 60 s, tap Send Now on each held message, or bulk-delete if content now stale.
• TON gas low: open @wallet → pending tx → increase gas → rebroadcast.
• Device clock off: enable “network time,” reschedule affected messages.

4. Practice drill (quarterly)

1. Create private test channel.
2. Schedule 35 messages inside 90 s window.
3. Force quota breach; measure recovery time.
4. Document actual drift vs. theoretical.

FAQ

Q: Can I schedule a message to myself?
A: Yes, open “Saved Messages” and follow the same long-press gesture. Delivery still passes through cloud queue.

Q: Does editing a scheduled message reset its time?
A: No; the timestamp remains unless you explicitly choose Reschedule.

Q: What happens if the channel is deleted before dispatch?
A: Telegram purges all pending schedules instantly; no bounce notification is sent.

Q: Can two admins schedule conflicting paid-collection posts?
A: Yes; the second post will queue normally, but double-charge risk is low because price is locked at schedule time.

Q: Is there an API for scheduling?
A: Not in Bot API 7.6; TDLib supports messages.sendScheduledMessage for user accounts only.

Q: Why does my web client lose schedules on refresh?
A: IndexedDB is cleared when the last tab closes; native apps persist the queue server-side.

Q: Can I back-date?
A: No; the picker blocks any past time.

Q: Do reactions count toward quota?
A: No; only outgoing messages burn send quota.

Q: Will schedules survive an account transfer?
A: Yes; they are bound to the user ID, not the device.

Q: Can viewers see that a message was scheduled?
A: No metadata is exposed unless you export chat history with developer flags.

Terminology in This Guide

• Delivery drift: delta between chosen time and server timestamp (first used in Performance section).
• Cloud queue: server-side hold for future messages (introduced in first paragraph).
• Send quota: rolling per-minute outbound cap (30/20 msg) (Performance section).
• Paid-collection: premium post locked behind TON payment (Feature Boundary).
• Slow Mode: admin setting that restricts member frequency (Best-Practice checklist).
• IndexedDB: browser-side storage for Web K/A (Web Client Caveats).
• Recent Actions: admin log visible in group/channel (Troubleshooting table).
• TON gas: transaction fee on TON blockchain (FAQ).
• TDLib: open-source library for building Telegram clients (Working with Bots).
• DST: daylight-saving time (Best-Practice checklist).
• User ID (UID): immutable account identifier (FAQ).
• msg_id: unique message identifier in URL (Measurement method).
• Debug menu: hidden developer options (Measurement method).
• Export with Metadata: option to include timestamps in JSON (Verification section).
• Conditional triggers: speculative future feature (2026 Roadmap).
• Recovery time: duration to restore normal delivery after quota breach (Runbook).

Risk & Boundary Summary

Confirmed limits: 1 000 future messages per chat, 366 days max horizon, no Secret Chat support, web client queue deleted on tab close.
Side effects: breached quota silently delays all pending, drift spikes on 2G, DST not auto-corrected.
When to avoid: emergency alerts, price-sensitive promos, interactive live commentary.
Alternatives: real-time bot flows, external cron calling TDLib, IFTTT webhook to private channel followed by manual forward-schedule.

Looking Ahead

Until conditional triggers arrive, the manual queue remains the most reliable, zero-cost path to perfect timing. Treat it as production infrastructure: version-control your JSON exports, rehearse quota failures, and keep one eye on the clock—literally.