Product
What the platform holds, stage by stage
The AI tools are one layer. This page covers the record-keeping underneath them: where a lead lives, how a claim works, and what happens to a commission after a deal closes.
Beneath the AI tools the platform is a system of record for a team: a shared lead pool with a claim and return workflow, a deal pipeline with transaction milestones, commission tracking tied to signed referral agreements, open house sign-in with consent capture, direct mail with broker identification, and a notification layer with per-category preferences.
Key takeaways
- Leads live in a team-scoped pool with an explicit claim and return workflow rather than being assigned by hand.
- Commission payments join against a signed referral agreement, so money is always traceable to an executed document.
- Open house sign-in captures consent and stores a snapshot of the exact wording shown at the time.
- Notification categories are separately controllable for in-app and email, and a few operationally critical types always send.
Leads move through a pool, not an inbox
Contributed leads land in a team-scoped pool that agents browse with filters for type, price and recency. Claiming is an explicit action with a record attached rather than an informal agreement, and a claimed lead can be returned to the pool.
Priority scoring orders the queue. It is a ranking aid over observed signals, not a prediction of who will transact, and the pool remains browsable independently of it so a low-scored lead is never hidden.
Capture accepts messy input. A pasted SMS or a screenshot of an enquiry is parsed into structured fields that pre-fill the contribution form for review, which keeps a misparsed phone number a correction rather than a bad record.
Deals carry stages and dated milestones
A claimed lead becomes a deal with pipeline stages and transaction milestones that carry real due dates. Deadline checks run on a schedule and raise notifications to the agent and, where relevant, the team leader.
The scheduler is written to survive a restart without shouting. A watermark records when each job last ran so the first tick after a deploy does not replay a backlog, and notifications carry a deduplication key so a retry cannot email someone the same reminder twice.
| Stage | What the platform holds | What it produces |
|---|---|---|
| Capture | Parsed lead fields, source, property details | A pool record for the team |
| Claim | Claim event and the referral agreement it satisfies | An executed agreement and a PDF for both parties |
| Work | Pipeline stage, milestones, follow-up tasks | Deadline reminders and follow-up nudges |
| Close | Deal outcome and commission records | Commission payments joined to the agreement |
| After | Audit history, notifications, reporting | A trail of who did what, and when |
Commissions attach to a signed document
A commission payment joins against a referral agreement rather than floating free against a deal. That constraint is what makes the money traceable: every recorded payment points at a document two parties signed, with a fee basis stated on it.
It also drives the editing rules. A fee can be amended while nothing has been paid, and the amendment voids both signatures until both parties re-sign. Once a payment exists the fee is locked, because the basis for money that has already moved is not something software should let anyone revise quietly.
Open houses, direct mail and the paperwork around them
Open house sign-in requires consent and stores a snapshot of the exact consent wording that was displayed, rather than a boolean pointing at whatever the current text happens to say. If the wording changes later, the record of what a visitor actually agreed to does not change with it.
Direct mail postcards inject broker identification into the template signoff from the stored broker profile, which is what New Jersey advertising rules require of a licensee. Keeping it in the profile rather than in each template means it is correct on every piece or wrong on none.
Administrative actions are audited, including impersonation. When a staff member acts on behalf of a user, the audit record carries both the real actor and the account acted upon, so support activity is never indistinguishable from the user own actions.
Notifications people can actually live with
Notifications reach an agent in the app, live over an open session, and by email, with categories controlled separately for each channel. New leads, deadlines, deals, commissions, open house signups and follow-ups are all independently switchable.
A small set always sends by email regardless of preference, and they are the ones where silence would be worse than noise: a closed deal, a claimed or returned lead, a role change, a failed login, a system error.
A per-role daily digest and a weekly team recap sit on top, each with its own preference so turning off one does not silently turn off the other.
Common questions
Can a claimed lead go back to the pool?
Yes. Returning a lead is a first-class action with its own record and notification, rather than something handled by asking an administrator to edit a row.
What stops two agents claiming the same lead?
Claiming is a single explicit transition on the record, so the second attempt finds the lead already claimed. The pool view reflects claim state rather than relying on agents to coordinate.
Is the consent text stored with each open house sign-in?
Yes, as a snapshot taken at the moment of signing. A later change to the wording does not rewrite what an earlier visitor agreed to, which is the point of snapshotting it.
Does the platform supervise agents or hold a licence?
No. RealEst Technologies LLC is a software company. Supervision, licensure and broker of record duties remain with the brokerage; the platform records the work rather than taking responsibility for it.