Farid Ismail
Lead analyst. Focuses on request timelines, zone density, and report structure for Pattern Reviews.
About
Operators first, charts second
Service Pulse Core grew from years of sitting with dispatch leads who already knew their Fridays felt wrong—and needed a calmer way to prove which hours and zones deserved attention.
Origin
We began in Ipoh, working alongside local on-demand service teams who ran bookings through a mix of apps, chat, and phone. The same questions kept appearing: which request windows were durable, which cancellations hid wait problems, and whether adding headcount would fix lag or simply raise cost. Service Pulse Core formalised that review work into clear engagements with written outcomes.
How we work with clients
We treat service request analytics as a reading of operational history, not a reason to rebuild your product. Clients share anonymised request timelines; we map peaks, lag, and handoff stalls; then we return recommendations ranked by effort and likely effect. When records are incomplete, we say so instead of inventing certainty.
People
Mei Ling Ong
Operations reviewer. Challenges roster recommendations against real shift constraints in Malaysian cities.
Values we hold to
- Specificity over slogans — findings name hours, zones, and stages.
- Honesty about gaps — missing status times shrink what we claim.
- Respect for operators — recommendations must be schedulable by people who already run the floor.