UDOM REMINDER

The Problem

Announcements were sent manually, one by one, whenever fees, examinations or registration deadlines approached. Messages were forgotten, replies were hard to track, and there was no record of who had actually received what.

The Solution

A scheduling service where an administrator uploads or selects a contact list, writes a message with optional personal details, and sets a send window. The service handles delivery, retries and reporting automatically.

Challenges

Local SMS gateways deliver reports inconsistently, so the reconciliation logic had to be defensive and idempotent. Rate limits and network timeouts also meant sends had to be queued rather than fired in one burst.

Result

Reminders go out on time, every time, with a clear record of what was sent and whether it arrived.

Key Features

• 01

  Scheduled reminder campaigns

• 02

  Personalised message templates

• 03

  Delivery status and webhook tracking

• 04

  Automatic retry on failure

• 05

  Contact list management

• 06

  Campaign history and audit log

Development Process

1. 01Mapping the reminder schedule and message templates
2. 02Designing contact lists and campaign records
3. 03Building the scheduling and queue layer
4. 04Integrating the SMS gateway and delivery webhooks
5. 05Implementing retry and reporting
6. 06Testing, deployment and handover

Project Screenshots