Visitor accounts

Visitor accounts are the free consumer accounts people create on your BrokerFold site — the identity layer that unlocks favourites, saved searches, sold-price data and property chat for them, and turns anonymous traffic into named, consented, behaviour-rich CRM contacts for you. Portals built empires on this mechanic; here it runs on your domain, and the database it builds is yours.

What an account unlocks for the visitor

Registration is quick — and everything it gates is genuinely worth having. Favourites persist across devices and sessions. Searches can be saved with daily email alerts attached. The sold layer — closed prices, off-market history, sold-derived market stats — opens under the VOW gate, with the terms acceptance the boards require. Property chat becomes available on every listing. And an account hub ties it together: saved homes, saved searches, messages, profile.

Sign-in prompts appear in place, at the moment of intent — tapping a heart, saving a search, touching sold data — and complete the original action right after registration instead of dumping the visitor back at square one. Friction is spent exactly where the visitor is most motivated to pay it.

How accounts work under the hood

Each tenant’s visitors are their own population: accounts are namespaced per site, host-scoped, and never pooled across BrokerFold customers. Passwords for VOW access expire on the board’s schedule — 90 days under TRREB’s rules — with renewal a self-serve emailed-code flow that re-verifies the person without destroying their account, favourites or searches. Access to gated data is evaluated on every request and logged, which is the audit posture VOW agreements expect of a compliant operator.

What a registration feeds in the CRM

The moment someone registers, the platform provisions a CRM contact and links the visitor identity to it. Consent is recorded the way Canadian law actually works: the VOW terms click-wrap establishes implied consent from the inquiry relationship, while express marketing consent is captured only by its own separate checkbox — never bundled, because bundled consent is invalid. Registration can also enrol the person into your visitor-welcome nurture sequence, once you have reviewed and armed it.

From then on, the account is a signal pipe. Every listing view, favourite, saved search and sold-price session flows onto the contact’s timeline, and the behaviour profiler turns it into scores and “what matters” summaries. The full argument for registration as a lead engine — including where to set the gate — is on VOW registration lead capture.

The privacy stance is part of the pitch, and your site should say so: registrants’ details are never sold onward or pushed to third-party portals. A visitor deciding whether to hand you an email address can tell the difference between a site that monetizes them and one run by the agent they might actually hire — and the registration rate reflects it.

The asset this builds

A portal’s registered users are the portal’s asset. Your site’s registered visitors are yours: named people, on your domain, with documented consent, live intent data, and no competitor’s ads beside your listings. Every month the site runs, that asset compounds — and it transfers with you, because you own the platform relationship it lives in.