Your neighbours can help. They just don't know when.
Knock is your building's private app: a spot coming free, a sofa to give away, a notice from the committee. Each one reaches only the neighbour who needs it.
A spot is free tonight
Water off Thursday
Your building already has everything it needs.
It just never reaches anyone in time.
A spot is free tonight
Dozens of spots sit empty for hours. Nobody knows which, or when.
Water off Thursday
The notice got written. It is message 340 in the group, in one language, and it cannot be pinned.
Three-seat sofa, free
It went to a group half the building has muted. It ends up downstairs by the bins.
Plumber · Moti
Six neighbours know he is good. That knowledge lives in six separate heads.
It isn't that the building is short of anything. It's that nobody knows in time.
Why the group stopped working
1,000
notifications from one request, in a group of 1,000 residents. So people mute the group, which is the right response to that much noise. And now the request reaches nobody.
12
of them reach someone who could actually help.
Unmuted, the group is unusable. Muted, it is useless.
See what's actually free, and ask without spamming anyone.
A request reaches only the neighbours whose spot is free right now, not the whole building.
Nobody has to answer. Not answering is completely silent: no score, no record, and nobody is told.
Owners take their spot back whenever they need it, instantly and at no cost.
One ordinary Tuesday on the committee.
Without Knock
- A DM, about the water.
- The same question, in the second group.
- A phone call.
- “Nobody told us.”
- A call, at home, in the evening.
Seventeen messages, three groups, two calls, one argument.
With Knock
One post. Ninety seconds.
The work didn’t move to someone else. It stopped being work.
Quiet on purpose.
Only genuinely urgent things interrupt anyone. Everything else waits quietly behind an unread badge.
Never suppressed
A recall on a parking spot. It gets through even with the whole parking module muted.
Urgent
The poster marks it urgent, and it pushes immediately.
Standard
Waits behind an unread badge. No push, no sound.
Ambient
Batched into at most one digest a day. The first thing dropped when things need to quiet down.
Building-wide pushes: at most two a week, by default.
Mute any module on its own. Muting the notice board can never mute a parking recall.
An app that publishes its own notification budget is making a promise a spammy app never would.
And when neighbours reach each other directly, you stop being the switchboard.
None of these roles goes away. They just stop being the route everything in the building travels through.
The committee
You stop being the building's inbox.
A notice is posted once, and stays somewhere you can search.
No comments and no reactions underneath it. Nobody argues there at midnight.
A request for a spot gets settled between neighbours, without routing through you.
Everything that happens is logged, so a dispute arrives with a record rather than two versions.
Residents
You only see what actually rings for you.
One screen, where anything with a deadline comes before everything without one.
The building's service providers: who the plumber is, and their number.
Give something away without posting into a group half the building muted.
Spot owners
You share when it suits you, and always get it back.
Listing an empty spot takes under ten seconds, for a window you choose.
“Ask me when it suits you”: reachable without being listed anywhere.
Take it back whenever you need it. Instantly, at no cost of any kind.
The management company
Fewer calls into the office, and a written record when you need one.
A publishing role for staff, with no access to the resident roster and no admin powers.
Every post is attributed by role (committee, management, reception), with a name underneath.
A monthly summary you can put in front of the committee.
The front desk
Residents tell the desk what to expect, and the desk tells residents what is waiting for them.
A note to the desk: visitors tonight, a viewing at 17:00, or a standing instruction.
A parcel, laundry or a key waiting at the desk, and the apartment is told.
No chat with the desk. Each note has one short line, and that is the whole conversation.
The module is off by default, and the building decides whether to turn it on.
The committee doesn't get more information about residents. It just stops carrying all of them in its head.
Everything in the building, in one place.
The committee chooses what is switched on, and any module can be turned off on its own.
- Announcements & events
- Parking
- House rules
- Service people
- Give away & sell
- Neighbour help
- Anyone have…?
- Issues
- Front desk
- Residents
- Budget
- Surveys
Your building is a closed room.
One door in: a building code, from a neighbour. No directory of buildings, and no search.
Your number is never shown to neighbours. It is revealed only when a transaction connects two people, and it expires on its own.
No location. No contact upload. No phone-number search.
The committee cannot see who read a post. On purpose.
The app refuses to publish “who lives where” next to “whose spot is free tonight”. Together, those two facts are a list of empty apartments.
We set it up. You post the first notice.
The committee's first action is writing an announcement, not administering a system.
We create the building and load the roster.
We verify spot labels against the actual signage.
Two admins trained, front desk briefed.
We recruit the first households, so it isn't empty.
A launch kit for the lobby and the group.
We're choosing our first buildings.
Knock is new, and we'd rather set up three buildings properly than thirty badly. So we run each pilot ourselves, end to end. The committee can turn it off at any time and take their data with them, and the WhatsApp group stays exactly as it is.
Book a 20-minute call20 minutes, your building's situation, no deck.