Register provenance before opportunity status
Capture how the person arrived, the source reference, stated purpose, property context and any permission statement exactly as supplied.
Workflow blueprint
A real estate CRM should remember why a contact entered the pipeline
An educational lead-custody model for brokers and property teams, without lead scoring, listing feeds, message automation or referral-law conclusions.
Keep the supplied source, stated property interest, communication preference, assigned owner, follow-up decision, suppression event and closure reason visible as separate evidence.
TL;DR — Keep the supplied source, stated property interest, communication preference, assigned owner, follow-up decision, suppression event and closure reason visible as separate evidence.
Assign a relationship owner
Name who may review the enquiry, which team owns the next action and when an assignment changed without granting broader contact authority.
Record contact and suppression decisions
Preserve attempted channels, outcomes, expressed preferences, objections and suppression instructions with their dates and sources.
Close the thread without erasing history
Choose a human-supplied closure reason, retain unresolved questions and leave later reactivation dependent on fresh authority evidence.
Page-specific decision aid
A lead provenance and permission ledger separating source, contact preference, assignment, suppression and closure
The ledger follows an open-house enquiry with a supplied email preference, a reassignment from sales to lettings, an unanswered call, a later objection, a suppression instruction, a second property interest from a new source and a human decision about whether the old authority can be reused.
- ✓A lead source is not permission to contact.
- ✓Assignment does not expand communication authority.
- ✓Closure cannot silently remove a suppression record.
Scope first
What Codeblix would confirm before implementation
This page is an operational blueprint. The final workflow, screens, permissions and integrations depend on your current process and agreed implementation scope.
- ✓Lead source and communication permission remain different facts
- ✓Assignment changes preserve the former owner and reason
- ✓Suppression survives pipeline stage and property changes
- ✓Outreach scoring referral legality feeds and conversion proof excluded
Relevant Codeblix foundations
Review the existing product areas that support the proposed workflow.
Use the related planning tools
Run the operational calculation, save the result in the URL and share it with your team.
Map this workflow to your operation
Tell Codeblix how work moves today. We will confirm the practical scope before proposing an implementation.
Discuss your workflow