Everybody your brokerage knows, whether they came through the website, the assistant, a spreadsheet or an agent typing them in. Each is matched to one record, carries what they agreed to and when, and can be tagged, segmented and messaged from the same place. Consent is not a checkbox on the contact; it is a ledger you can show.
Contacts
Everybody your brokerage knows. 1,842 contacts · 12 tags · 4 custom fields.
Five ways into the list, one matching rule. A person who enquired in March and signed the open-house sheet in July is one contact with two sources, not two contacts with half a history each.
A listing inquiry, a showing request, a pre-construction request, a compare enquiry or a question to an agent. The contact is created with the source and the property attached.
Source · inquiryA marketing form arrives with its purpose, such as newsletter. The assistant's short form arrives as an enquiry on the property that was being discussed.
Source · formA spreadsheet matched column by column, or a contact an agent types in. Both land in the same list and can be tagged, segmented and messaged like the rest.
Source · import, manualContacts is the brokerage's CRM: name, email, phone, address, notes, an owner, and the history of how each person arrived. Tags, segments, campaigns and flows all read from it, so a list is built once and used everywhere.
Every grant and every withdrawal is an event in an append-only ledger: channel, purpose, the exact wording shown, when it happened, and hashed evidence of the request. What a contact is allowed today is resolved from that ledger at the moment of sending, never from a cached flag that could drift.
Choose a CSV, match each column to the field it belongs to, and read the preview before it runs: how many rows are new, how many will update an existing contact, and how many cannot be read. The file is checked in your browser first, so a bad export is rejected before it is uploaded, and checked again on the server with the same rules.
A tag is the simplest way to record what a contact is; a custom field records a fact about them a flow can write and read. Segments select on both, campaigns aim at the segments, and a flow can add a tag or save a value as it runs.
Everyone at this brokerage can apply these. Only an admin can rename or delete them.
Shared across the whole brokerage. A flow's Save Value step writes to one of these.
Contacts, owners, notes and the enquiry history come with Growth. Tags, custom fields, CSV import with attested consent, the consent ledger and the segments that read them are part of Marketing Studio, which the Automated AI Lead Engine add-on switches on.
Added to Growth or Dominance AI. Switched on or off at any time, billed pro rata alongside your plan.
Growth includes the CRM itself: contacts, owners, notes, enquiries and the customer accounts that feed them.
One matching rule everywhere: email first, then the phone number in international form, always within your brokerage. An import checks each row against your existing contacts and updates a match instead of creating a copy; duplicates inside the file itself are counted once.
Only if consent is recorded for it. The import asks when, where and how the people agreed, plus your confirmation. With all four, marketing and reply consent is written for every imported contact; with fewer, they are imported without consent and no campaign will reach them until it is recorded.
Channel and purpose, whether it was granted or withdrawn, the time, the version of the wording that was shown, the source it came from, and hashed evidence of the request. It is append-only; a contact being deleted does not erase what they told you.
A STOP withdraws both texting purposes at once and outranks any earlier grant. An email unsubscribe is mirrored into the same ledger. From that moment the person is excluded from every campaign; nobody has to remove them by hand.
Yes. Every import is listed under Recent imports with a Reverse action. Reversing removes what that batch created, including the consent events it wrote, and leaves contacts it merely updated in place.
The brokerage, or the agent it is assigned to. Agents see their own; admins see everyone. When an enquiry matches an existing contact, the lead attaches to it without changing its owner, tags or marketing state.
Has or lacks a tag, has an email, has a phone, came from a source, came from a particular import, and consent for the channel you intend to use. Rules are combined with AND; for OR, make two segments.
Growth brings the CRM; the Lead Engine adds tags, imports with attested consent and the ledger that makes a campaign lawful. Start with the list you already have.