01
Singapore region scan map
The bot scans across Singapore by working through defined regions, instead of relying on one broad request and hoping for the best.
Case study
Accident alert Telegram bot for Singapore traffic monitoring.
A short case study for busy business owners who want the important parts quickly: what problem existed, what we built, what features mattered, and why a similar workflow could help their business.
Problem
The team needed accident alerts without babysitting a map all day.
Before
- Someone had to keep checking traffic data manually, which is not exactly the dream job anyone signed up for.
- Raw alert data could be noisy, duplicated or incomplete, so it needed filtering before it became useful.
- A single broad API request was not reliable enough for Singapore-wide monitoring.
- Repeated alerts could irritate the Telegram group and make people ignore the important updates.
- The workflow needed to keep running even when API calls or Telegram delivery were not perfect.
Solution
A custom PHP automation that turns traffic API data into Telegram alerts.
After
- The worker scans 10 overlapping Singapore regions every 60 seconds.
- It reads Waze-sourced accident alerts through the OpenWeb Ninja API and keeps only relevant items.
- It remembers incident IDs for seven days to reduce duplicate Telegram alerts.
- It sends clean Telegram notifications with useful location context and a Waze link.
- It includes retry and monitoring logic, because real systems cannot just panic and go home.
Feature slideshow
The features that made the system useful.
02
Live Telegram accident feed
Relevant accident alerts are pushed into Telegram in a format the team can read quickly, even during a busy workday.
03
Duplicate and retry control
The workflow checks incident IDs, skips repeated alerts, stores state and retries failed sends so the group does not get spammed.
04
One tap from Telegram to Waze
Each alert includes a direct Waze action, helping the team move from notification to map context without digging around.
05
Alerts via Telegram notifications
The final output is simple: timely Telegram notifications that reach the right people without another dashboard to babysit.
Tech stack
The practical technologies behind the monitoring and alert workflow.
PHP 8.1+
Runs the core monitoring worker, filtering rules, state handling and Telegram delivery without a heavy application framework.
cURL Multi
Requests all 10 Singapore regions concurrently, keeping each complete scan fast instead of waiting for sequential API calls.
OpenWeb Ninja Waze API
Provides the live Waze-sourced traffic alerts that the system checks, normalises and filters for Singapore accidents.
Telegram Bot API
Delivers readable group notifications with the road, incident details, reported time and a direct Open in Waze button.
JSON State + File Locks
Tracks incident IDs, delivery status and retries while preventing duplicate alerts and overlapping worker runs.
Linux + cPanel Cron
Starts the protected Singapore-wide scan every minute for practical 24/7 operation on the production server.
Testimonial proof
Show proof without making visitors read a novel.
Why hire us
Because the job is not just coding. It is understanding the messy workflow.
We map the workflow first
Before building, we clarify what should happen, who needs alerts, what can fail and what success looks like.
We build for real-world mess
APIs can fail, data can repeat, people can miss messages. The system should expect that instead of acting shocked.
We keep it maintainable
The solution stays understandable, documented and practical so future fixes do not become a treasure hunt.
We think in business outcomes
The goal is not “nice tech”. The goal is less manual checking, faster reaction and better operational control.
Could this fit your business?
WhatsApp us
If your team keeps checking, copying, chasing or reporting manually, we can probably automate part of it.
Send us your current workflow. We will help you figure out whether you need a simple bot, a dashboard, an internal system, a CRM workflow or a phased custom build.
Quick contact card
Anees Khan
Founder-led web, mobile app and custom management systems team. Send us your issue, current website, or idea and we will help identify the practical next step.
Pricing starting point
Start with a clear scope before you start spending heavily.
Small fixes, audits and consultation can start from a practical entry point. Full websites, apps and systems are quoted after scope, screens, roles and workflow are clear.
- Free initial audit or consultation for serious enquiries
- Different options for fix, improve, rebuild or new build
- Clear deliverables before development begins