LGU Notify — Constituent Notification Service

One notification rail for the whole LGU: permit status updates, RPT deadline reminders, disaster alerts, and payout schedules over SMS, email, and Viber — with templates, delivery receipts, and cost controls, modeled on the notifications-as-a-service pattern the UK government proved. Every department sends through one accountable channel instead of five personal phones.

Typically bought by: Municipal Administrator, Public Information Officer, department heads, MDRRMO

Standard features — always included

• ✓Central template library with placeholders, approval workflow, and bilingual (Taglish) variants
• ✓Multi-channel sending: SMS, email, and Viber with per-message channel fallback
• ✓Department sending accounts with quotas and cost accountability
• ✓Contact list management synced from LGU systems with opt-out handling
• ✓Bulk CSV sends for one-off campaigns
• ✓API for our LGU products to trigger transactional notifications (permit ready, payment received)
• ✓Delivery receipts and failure retry with per-message status
• ✓Priority lane for emergency/disaster alerts that preempts queued traffic
• ✓Send analytics: volumes, delivery rates, cost per department
• ✓Provider-agnostic SMS gateway support (Semaphore, M360, or the LGU's contracted aggregator)
• ✓GovLink-native: every connected LGU system sends through this rail automatically once the LGU joins

Popular custom additions

Quoted per feature in the configurator — typically ₱3,000–₱18,000 each.

• +Scheduled recurring campaigns (RPT quarters, renewal seasons, garbage schedules)
• +Two-way keyword replies routed to the right department
• +Voice-blast channel for announcements to non-readers
• +Barangay sub-accounts so barangays send under the same governed rail

Tech stack

Frontend

Next.js (React)

Backend

Next.js API / Node.js

Database

PostgreSQL

Integrations

SMS gateway (provider-agnostic), Email service, Viber business messaging (optional), REST API for LGU systems