Optimizing Engagement Timing for Higher Click-Through Rates

The Challenge

A multi-channel fintech platform was executing batch campaign runs based on its database servers' default UTC schedule. This caused significant notification timing issues: users based in India frequently received promotional push notifications, SMS, and WhatsApp alerts at late-night hours (e.g. 11:30 PM or 2:00 AM IST). This midnight spam drove a sharp increase in app uninstalls and spam reports. Additionally, the platform was flagged for violating the **Telecom Regulatory Authority of India (TRAI) guidelines**, which restrict Unsolicited Commercial Communications (UCC) during quiet hours. Under TRAI regulations, sending promotional messages between 9 PM and 9 AM is illegal and subject to network penalties.

What We Did

We built a geolocated, timezone-aware scheduling middleware that restructured the notification pipeline:

1. TRAI Quiet Hour Enforcement: Hard-coded a block on all promotional API endpoints. Any marketing message queued between 9 PM and 9 AM IST was automatically held in a Redis buffer and delayed until the next morning at 9:30 AM.
2. Timezone Normalization: Captured each user's timezone preference during signup based on client IP geolocations. All batch runs were executed in regional waves, ensuring a user in Mumbai received an alert at the exact same relative time as a user in Singapore.
3. Individual Engagement Routing: Analyzed the historical hourly login data of each user. If a user consistently checked their portfolio during their evening commute (7:00 PM to 8:30 PM), the system prioritised sending their non-urgent summaries during that specific window.

Key Insights

Our timing optimization experiments yielded three insights:

• Night messaging is lethal: A single promotional notification sent after 10 PM IST resulted in a 4x higher uninstall rate than the same message sent during the day. Users view late-night notifications as invasive.
• Align with market hours: For financial products, price-sensitive updates performed best when sent during active market hours (9:15 AM to 3:30 PM IST). Educational or portfolio performance reviews performed best on Saturday mornings.
• Establish a multi-channel fallback: Instead of sending a push alert, WhatsApp, and SMS simultaneously, we staggered delivery. The system sent a push notification first. If it remained unopened after 2 hours, it sent a WhatsApp alert. Transactional SMS was reserved only as a secure confirmation step.

The Results

After enforcing timezone-aware scheduling for 30 days: - Blended click-through rates (CTR) across push notifications rose by **24%**. - Spam complaints and DND registration violations fell to **zero**, avoiding potential TRAI fines. - Overall weekly app uninstalls dropped by **18%**. - Open rates on WhatsApp campaigns rose from 45% to **68%** due to better daytime delivery.

How to Implement This

To implement timezone-aware timing optimization:

• Store user locations: Log the user's localized timezone offset (e.g. `GMT+5:30` for India) in their profile record during onboarding.
• Write quiet hour validation logic: Build a middleware filter that checks the target user's local time before executing any messaging webhook:

      if (localTime.hour >= 21 || localTime.hour < 9) {
        delayNotification(notification, nextMorning9AM);
      }
      

• Verify DND status: For Indian SMS and voice routing, integrate with telecommunication gateways that cross-reference the national Do Not Disturb (DND) registry automatically.
• Test batch execution time: Never run cron jobs on raw server time without normalizing targets first.

Why This Works

This approach works because it respects the user's personal boundary. By aligning your messaging schedule with local regulatory norms and individual usage habits, you minimize cognitive disruption. Your notifications transition from being perceived as intrusive ads to timely, high-value personal updates.