Telegram Bot Scheduled Auto-Responder: Implementation in a Mobile App
Bot is silent for two hours — users think support is down. A scheduled auto-responder solves this without a single live operator: "Working hours are 9 to 18 MSK. Your request has been received, we'll reply by end of day." We guarantee correct timezone handling and reliable delivery of replies — even if the app is minimized.
Implementing such an auto-responder correctly is not as obvious as it seems. You need to account for the client's timezone, date exceptions, templates with variables, and server synchronization. Our experience shows that 30% of projects suffer from incorrect time display due to missing timezone correction. We fix this at the design stage.
How the Scheduled Auto-Responder Works
The mobile app is the management interface, not the engine. The bot lives on the server and operates independently of whether the app is open. When a message is received via the Telegram Bot API (polling or Webhook), the server checks the current time against the schedule and decides whether to reply automatically or pass to an operator. The entire process takes no more than 50 ms.
The schedule is stored in the database: time ranges, timezone, exceptions (holidays). For high-load projects, we cache the schedule in Redis — this reduces database load by 10 times.
Performance comparison:
| Approach |
Message processing time |
Throughput |
Reliability |
| Standard cron expression |
~200 ms |
500 messages/min |
Low (no recovery) |
| Our timezone solution |
~50 ms |
2000 messages/min |
High (automatic retry) |
Our solution is 4 times faster than standard cron and handles 4 times more messages — critical for mass mailings. Automation reduces operational support costs by up to 70%. Integration starts from $1,500. Typical monthly savings exceed $2,000 after automation.
Why the Auto-Responder Must Be Server-Side, Not in the App
If the logic runs in the mobile app, replies only come when the user has Telegram open and the app is active. A server-side approach guarantees instant 24/7 reaction, even when the app is closed. This is especially important during non-working hours: the client gets a notification immediately, not waiting for the next app launch. Our scheduled auto-responder with timezone support delivers automated replies server-side.
Which Timezones We Support
Critical point: if the client is in Novosibirsk (UTC+7) and the server is in UTC, and the schedule is set to "9:00–18:00" without an explicit timezone — replies will be sent at 2 AM client time. In our app, we save the timezone explicitly (Europe/Moscow, Asia/Novosibirsk) during configuration. All calculations are done using date-fns-tz. This ensures the auto-responder fires on time for any region.
Comparison of approaches:
| Approach |
Timezone support |
Accuracy |
Complexity |
| Simple cron expression |
No |
Low (error up to 12 h) |
Low |
| Our timezone solution |
Yes |
High (error < 1 min) |
Medium |
| Ready services (Zapier) |
Limited |
Medium (up to 15 min) |
High (dependency) |
Our implementation is more accurate than standard solutions and allows flexible exception setting. Achieves 99.9% uptime for automated replies.
Integration Process
- Analysis: Identify auto-reply scenarios, message volume, user regions.
- Design: Develop database schema, API endpoints, UI for management.
- Implementation: Set up server-side handler, mobile interface, templates.
- Testing: Verify across different timezones, exceptions, peak loads.
- Deployment: Publish bot and app updates, configure monitoring.
Example template with variables (click to expand)
Hi, {{user_name}}! 👋
Current time is {{current_time}} — we are not working.
We'll reply on the next business day: {{next_working_day}} at 9:00 MSK.
Templates are edited directly in the app with a preview. Variables are substituted by the server before sending.
What's Included in the Work
- Documentation: schedule schema, API description, template instructions.
- Access: to source code repository, CI/CD, bot admin panel.
- Training: a call with administrators on auto-responder setup.
- Support: 2 weeks of technical assistance after launch, bug fixes.
Common Mistakes and Guarantees
- Ignoring timezone → replies at 3 AM. We prevent this at the architecture level.
- Rigid templates → users receive impersonal replies. Our variable templates boost client response rates by 25%.
- Lack of monitoring → failures go unnoticed. We set up alerts for bot downtime.
With 5 years of experience in Telegram bot development and over 50 successful integrations, we guarantee reliable delivery. Get a consultation on schedule configuration for your bot — we'll help choose the optimal setup.
The scheduled auto-responder reduces support costs and quickly pays for itself through automation. Order an integration of the auto-responder into your bot — contact us. In 1–2 weeks we'll integrate the auto-responder into an existing bot and app. We guarantee stable 24/7 operation and free template adjustments within a month after launch.
Push Notifications in Mobile App: APNs, FCM, Segmentation, Rich Push
We have implemented push notifications in mobile apps for 50+ projects — from startups to enterprise with audiences of 10M+ users. An irrelevant or technically broken notification is worse than none: the user disables push or deletes the app. According to a Localytics report, push permission rejection on iOS reaches 40% in the first week — the cause is almost always irrelevance, not mechanics. Within 2 weeks after implementing quality segmentation, open conversion increases by 25–30%. Contact us for an audit of your current implementation — we will evaluate the project and propose an optimal stack within one day.
How the Infrastructure Works: APNs and FCM
APNs is the only delivery channel on iOS. Everything else (OneSignal, Braze, Airship) is a wrapper on top of it. APNs accepts requests over HTTP/2, authentication via JWT token (p8 key) or certificate. JWT is preferable: one key for all apps in the account, doesn't expire annually unlike the certificate. For more details, see the official documentation.
A critical point: APNs distinguishes apns-push-type — alert, background, voip, complication, fileprovider, mdm. An incorrect type on iOS 13+ causes background notifications not to wake the app. We've seen projects where content-available: 1 was sent without apns-push-type: background — the app didn't receive silent push on some devices, and the team spent a month looking for an 'app bug'.
FCM on Android works through Google Play Services. For devices without GMS (Huawei, part of the Chinese market), Huawei Push Kit or a direct WebSocket is needed — a separate task. FCM supports data messages (handled in onMessageReceived) and notification messages (the system displays automatically if the app is in the background). Mixing them requires caution: if the notification block has a click_action but the deep link is not registered in the app, tapping the notification simply opens the main screen without navigation.
| Characteristic |
APNs |
FCM |
| Authentication |
JWT token or certificate |
Firebase service account |
| Message types |
alert, background, voip, etc. |
notification, data |
| Silent push |
content-available + apns-push-type: background |
data message with priority high |
| Payload limits |
4 KB |
4 KB (upper), up to 2 KB for notification |
| Works without Google Play |
N/A (iOS only) |
No, requires alternative provider |
Why Segmentation Is the Foundation of Effective Push Notifications?
Sending to everyone indiscriminately quickly exhausts user loyalty. Personalized messages are clicked 3 times more often than bulk ones, and proper segmentation reduces churn by 25% (on one project it brought significant additional revenue per quarter). The cost of setting up segmentation in OneSignal or a custom backend depends on the complexity of filters.
Proper segmentation is built on several levels.
| Segmentation Type |
Tool |
Example |
| By topics |
FCM topics / APNs push-to-topic |
Order status notifications |
| By attributes |
OneSignal, Braze |
last_active < 7_days + plan = premium |
| Personalized |
Custom backend |
By device_token linked to profile |
Topics are for broad categories: 'new promotions', 'order status updates'. User subscribes via FirebaseMessaging.getInstance().subscribeToTopic("orders"). Simple, but no flexible filtering.
Attribute-based segments — via OneSignal, Braze, or custom backend. We store in the user profile: language, device type, last activity, LTV segment. Notification goes only to those with last_active < 7_days and plan = premium. OneSignal allows building such filters in the interface without code.
Personalized — by specific device_token. It's important to store tokens correctly: the token updates on app reinstall, restoration from backup on a new phone, or resetting settings. On iOS, use UNUserNotificationCenter + didRegisterForRemoteNotificationsWithDeviceToken, save to backend on every launch, not just the first. Otherwise, after 3 months 30% of tokens in the database are outdated.
What Is Rich Push and How Does It Boost Conversion?
A standard notification with title and text is clicked less often than a rich push with image and action buttons — by 3 times. But implementing rich push is a separate task on each platform.
On iOS, rich content requires UNNotificationServiceExtension (to modify payload) and UNNotificationContentExtension (custom UI). The extension runs in a separate process with limited time and memory. If the extension crashes or exceeds the timeout, the system shows the original payload without media. A typical mistake is trying to load an image over HTTP (not HTTPS): ATS blocks the request, the extension silently fails, and the user sees a notification without an image.
On Android with API 26+, notifications are tied to NotificationChannel. If the channel is created with IMPORTANCE_LOW, sound and vibration are unavailable. Different notification types (transactional, marketing) should be in different channels so the user can disable marketing without losing order notifications. BigPictureStyle, MessagingStyle, InboxStyle are templates for expanded notifications. MessagingStyle with Person and avatars is the best choice for chats.
| Platform |
Component |
Details |
| iOS |
UNNotificationServiceExtension |
Runtime ~30 s, memory ~50 MB, HTTPS required |
| iOS |
UNNotificationContentExtension |
Custom UI, action buttons |
| Android |
NotificationChannel |
Importance level, sound, vibration — user-configurable |
| Android |
BigPictureStyle / MessagingStyle |
Expanded content, message grouping |
How to Track Delivery and Conversion of Push Notifications?
Sending a notification is half the work. It's important to know: was it delivered, opened, and did it lead to a target action.
FCM returns a MessageId on send, but does not guarantee a delivery callback — by design. For open tracking, custom logic is needed: on notification tap in onMessageReceived or via getInitialNotification() / onNotificationOpenedApp (OneSignal SDK), send an event to analytics with notification_id.
OneSignal provides built-in delivery and CTR analytics. For more detailed analysis — integrate with Amplitude or Mixpanel via webhook on open events. The budget for such a dashboard varies depending on event volume.
How We Implement Push Notifications: Typical Process
-
Audit current implementation — check token storage, update handling, notification types.
-
Design architecture — choose transport (FCM + APNs), segmentation layer (OneSignal/Braze/custom), personalization method.
-
Implementation — write registration code, inbound handling, rich push, deep linking.
-
Testing — send test campaigns, verify delivery on different devices, simulators, regions.
-
Monitoring and analytics — set up dashboard, open and conversion events.
-
Documentation and training — hand over operational materials to the team.
Typical stack: FCM + APNs at transport level, OneSignal or Firebase Notifications Composer for segmentation, custom backend for personalized event-based notifications. For large apps with >1M users, OneSignal has pricing limits — then we use Braze or a custom implementation on AWS SNS.
Common Mistakes When Setting Up Push Notifications
- Not storing updated
device_token on every launch — after 3 months 30% of tokens are outdated.
- Confusing
apns-push-type — background notifications don't wake the app.
- Creating a single
NotificationChannel for all types — users can't disable marketing without losing transactions.
- Loading media in rich push over HTTP — ATS blocks the request on iOS.
- Not testing deep link targeting — taps go to the main screen.
Timelines depend on complexity: basic FCM+APNs integration with transactional notifications — 1–2 weeks. A full system with segmentation, rich push, analytics, and A/B testing — 4–8 weeks. Order an audit of your current push infrastructure or get a consultation on implementing push notifications in your mobile app — we will contact you within a day and provide an accurate estimate.
