Enquiries, viewings and follow-ups stay visible.
For property agents and brokersThe unanswered-message problem
Nothing slips through.
Know which authorised conversations still need a reply, where they arrived, and how long they have waited.
For people whose reputation depends on replies.
Every platform is shown at its verified access level.
Who it helps first
Relationship-heavy work comes first.
SM Crawler is for an owner or small trusted operation that needs to see and act on authorised conversations personally.
Separate proper requests from ordinary updates while keeping each source and its access boundary clear.
See the conversation, priority, reply state and elapsed time together in one customer-controlled local system.
Every platform is shown at its verified access level.
Your platforms · stated honestly
One list. Each route carries its state.
Only connected and proven routes appear in the working product. A view-only item opens the official destination and never shows a Reply action it cannot perform.
Established authorised or owner-local routes preserve the context available to them.
READ + REPLY WHERE CONFIGUREDProfessional and Page routes use only the permissions granted to the connected account.
AUTHORISED ACCOUNT ROUTESOfficial-account, bot or authorised-account capability varies by platform and account.
WHEN ACCESS IS ACTIVERestricted routes stay pale and open the official destination unless exact access is approved.
VIEW-ONLY UNLESS APPROVEDCredentials alone do not make a connection live. Dedicated access evidence comes first.
ACCESS PROOF FIRSTThey are shown only after a lawful route and its actual behaviour have been verified.
NOT YET / VERIFY FIRSTKnow what is still waiting.
Other people’s requests can take control of your agenda. SM Crawler puts you back in command of your own.
One clear view, with the host boundary stated.
- SM Crawler runs from the owner's computer.
- Keep that computer on whenever SM Crawler or paired-device access is needed.
- The current system does not claim an independent always-on private-cloud crawler.
- It tracks reply state instead of treating arrival alone as proof that work is handled.
The system in plain English
See the answer, then open the detail.
Who still needs an answer?
Waiting work keeps its source, elapsed time and conversation context.
What can this route do?
Reply, view-only, approval and not-yet states stay visible beside the named route.
Where does the data remain?
Inside the customer's local installation, subject to the stated operating-system and encryption boundaries.
Security and data protection
The current boundary is explicit
Messages, contacts and history stay inside the customer's local SM Crawler installation. They do not enter a central SM Crawler customer-content database.
Personal passwords remain private
The operator does not ask for or know the personal password used to sign in to a platform. Revocable tokens or app-specific credentials may be stored in the customer's controlled installation where a connection requires them.
Private sign-in is protected
SM Crawler account passwords use salted scrypt hashes. Sessions use verified protections, repeated guesses are throttled and cross-site writes are rejected.
The current boundary is explicit
Local message, token and history files use restricted operating-system permissions but are not yet encrypted at rest. No end-to-end or independent-certification claim is made.
Local-host boundary: remote and paired-device access depends on the owner's computer remaining on. The independent customer-owned always-on crawler is future work, not a current offer.
Open the full trial
Add three conversations you want to answer.
They stay only in this tab and reset when you reload. The trial figures are examples, never presented as live account data.
Property enquiry · waiting 2 daysBooking question · waiting 5 hoursDocument follow-up · waiting 38 minutes
Language path:EnglishItalianSpanishFrenchSimplified ChineseJapanesePortuguese PTPortuguese BRArabic RTL