Web push notifications

Web push notifications put the events that make you money — a new lead, a tour request, a visitor message — on your screen the moment they happen, even when the CRM tab is closed. They are the fastest layer of the BrokerFold CRM’s three-layer notification stack: push for immediacy, the in-app bell feed for the record, and email for everything you didn’t see live.

The events worth interrupting you for

Push is reserved for instant-class events, because a notification channel that cries wolf gets muted. A lead submitting on your site, a formal viewing request, a visitor sending a chat message about a property — these fire immediately to the seat that owns them. Digest-class information (your activity summary, pipeline movement) stays in the daily digest email where it belongs. The distinction is structural in the product: you never have to build a filtering scheme to keep push meaningful.

Notifications respect assignment. When lead routing hands a lead to a seat, that seat gets the push; a first-to-claim offer notifies the eligible racers; an unassigned visitor message falls back to the owner. Nobody gets spammed with the whole team’s traffic.

Setting it up on a live site

Enabling push is a one-time browser permission from the CRM — no app install, no phone-number pairing. Under the hood the platform uses the standard web push protocol with proper cryptographic server keys, and the plumbing is self-healing: dead subscriptions are cleaned up automatically, and a key rotation re-subscribes clients without you noticing. Per-seat notification preferences live in the CRM settings, so a team lead who wants push for leads but email-only for messages can have exactly that, per device, without touching anyone else’s setup.

What push protects in the CRM

Push exists because of one number: the collapse in contact rates as minutes pass after a lead submits — speed to lead is the whole argument. The CRM already answers instantly on your behalf with automated first-touch, but automation buys you time; it doesn’t replace the human call. Push is what gets the human moving.

Every pushed event is also written to the bell feed with its full context, and the underlying lead or message carries its complete CRM record — source, routing history, and the person’s site behaviour. You tap the notification, land on the person, and see what they were doing on your site before they raised their hand. The notification is the trigger; the CRM record is the ammunition.

Why built-in beats bolted-on

Teams assemble this from parts — a website vendor emailing leads to an inbox, a phone app watching that inbox, a group text for coverage. Every relay adds latency and a failure point, and none of the parts knows about assignment. Because BrokerFold’s push layer sits inside the same system that captures the lead, routes it, and stores the behaviour, there is nothing to wire, nothing to desync, and no lead that pings three phones while its owner sleeps through it. It ships on every plan, and it takes one browser prompt to turn on.