Different agencies.
The same lost enquiry.
Someone messages on WhatsApp. A coordinator replies, then a dozen newer threads push it down the list. Nobody decides to drop it — it just stops being visible. That failure is identical whether you place helpers or sell units.
What differs is how long quiet means dead.
This is the reason a single reminder setting does not work across agencies. Coreframes Lab measures time since the last message you sent, and each stage carries its own threshold, set per agency.
- property
- 24 hours — a buyer who goes quiet for a day is usually already viewing someone else’s listing.
- maid
- 24–48 hours — employers compare two or three agencies before committing, and the slow reply loses.
- confinement
- weeks — mothers book months ahead of a due date, so three quiet weeks can be a perfectly healthy thread.
Apply the property threshold to a confinement agency and you generate alarms all day until someone turns alerts off entirely. That is why the number belongs to you, not to us.
Pick the version written for your work.
The parts that do not change.
One inbox, sorted by neglect
Open threads ordered by how long since you last replied, oldest first. A lead nobody has ever answered sits above everything else, because it should.
Your own phone keeps working
Reply from WhatsApp on your handset and the thread updates here, marked as handled by a person. Nobody has to change how they already work.
Stages you name yourself
Nothing is hardcoded to one trade. You define the stages your work actually has, and the staleness threshold for each one.
PDPA handled at the data layer
Row-level isolation per agency, signed URLs on stored files, and an immutable log of every record viewed. Singapore-hosted.
Not sure which one fits?
Tell us how enquiries reach you today and we will say plainly whether this helps — including when it does not.
