Everything has been deliberately platform-free until this point. If you jumped here first, go back: a list without a committed owner and measurable number is how brokerages end up with three half-built campaigns feeling like nothing works.
The design test
If you can't describe the agent's action in one sentence, you haven't finished designing it yet.
Run every idea through these seven tests
These come from builds that worked and builds that didn't. Check each one before anybody starts configuring.
Build sequence — agent follow-up with existing contacts
Worked example: a brokerage curated a monthly newsletter that agents weren't sending. Rather than coaching harder on sending, they removed the agent from the send path entirely.
- Agree the one agent action — before anything is builtIn the worked example: "add this tag to any contact who should get the newsletter." That's it. Not "curate your list and send monthly."
- Deploy a tag campaign to pre-populate the tag in every agent's accountDo not ask agents to create the tag. Pre-populating guarantees it exists everywhere, spelled identically, before a single agent is coached. This is the step that makes the rest reliable.
- Build the campaign to personalize itselfDynamic content: the sending agent's own listings and recent solds, plus brokerage-selected featured listings and region-specific articles. Personalization is automatic, never agent labor.
- Coach exactly one behaviorSame words, every time, from every leader. Add the tag. Nothing else in the message.
- Verify tag propagation before the first sendConfirm the tag landed and is being applied. A silent under-delivery looks like campaign failure when it's actually a data problem.
- Deploy on behalf of all agentsDefault-on. The brokerage sends; agents receive credit and replies.
- Give agents the preview and the scheduleEvery agent should be able to see what went out under their name and when.
What actually changes
Agent effort drops to one action. Admin effort drops because there's no reconciling of a dozen tag variants. Brand reach scales to the whole roster instead of the handful of agents who were self-sending. The reclaimed admin time goes back into better content — which is the part that compounds.
Prerequisites — confirm before build
| Prerequisite | Who confirms |
|---|
| Agent roster in RISE is current — no departed agents, no missing new hires | Brokerage |
| Agents have contacts in RISE to tag (if the database is empty, this is a different project) | Brokerage |
| Listing and sold data is flowing correctly for dynamic content | Both |
| Sending domain authentication is in place | Both |
| Content owner named and calendar agreed for the first three issues | Brokerage |
Build sequence — new lead to appointment
In-flight example — results not yet confirmed. A brokerage with steady lead flow and under 1% conversion to appointment. They had tried high-frequency email, buyer-specific content, and seller-specific content over 1–3 years. The approach below replaces more emails that make assumptions with fewer emails that ask questions.
Why the previous attempts didn't work
Every approach they tried assumed they already knew who the lead was. Sending buyer content to someone who turns out to be an investor doesn't fail loudly — it just quietly doesn't convert. Three years of tuning content couldn't fix a problem that was really about missing information.
- Separate new subscribers from the existing programNew leads enter a short discovery sequence, not the general content stream. Resist the instinct to add this on top of what's already sending.
- Email 1 — introduce the brokerage, open a real reply channelThe brokerage's value proposition, plus an "ask me anything" CTA. Build the button as a mailto to the sending agent's own address. This matters: the goal is a live conversation with a person, not a click on a tracked link.
- Email 2 — the RISE client survey, two days laterUncovers whether the contact is a buyer, seller, or investor, and what they actually need. This is the engine of the sequence — everything else exists to get this answered.
- Email 3 — short callback, two weeks laterReturns to the ask-me-anything invitation and thanks them for the chance to connect when the timing is right. Brief and low-pressure. It closes the loop without adding volume.
- Make sure agents see what comes backSurvey responses and replies have to land somewhere the assigned agent will actually look. A discovery sequence that nobody reads the output of is just more email.
- Coach the one agent actionWhen a survey comes back, follow up on what it revealed. That's it. The agent isn't writing sequences or deciding cadence — they're responding to a lead who just told them what they want.
How you'll know it's working — and when
This sequence is a few weeks old at its first brokerage, so treat the early signals as encouraging rather than proven. Don't promise the lagging number on the strength of the leading one.
| When | What to look at |
|---|
Day 30
Leading | Survey completion rate. Replies to the ask-me-anything CTA. Open and click rates against the old high-frequency program. |
Day 60
Behavioral | Are agents acting on what the surveys reveal? A survey nobody follows up on is engagement without consequence. |
Day 90
Lagging — the real test | Conversion to listing appointment or showing, against the starting baseline. This is the number the brokerage came to you with, and it's the only one that settles the question. |
Where this could still fail
Better lead intelligence only converts if agents use it. If engagement climbs and conversion doesn't, the bottleneck has moved downstream to follow-up behavior — which is a real and useful finding, not a failed build. Plan to look for that rather than be surprised by it.
Prerequisites — confirm before build
| Prerequisite | Who confirms |
|---|
| New leads are flowing into RISE and assigned to the right agent | Both |
| Each agent's sending email address is correct — the mailto CTA depends on it | Brokerage |
| The brokerage value proposition is written and agreed before build | Brokerage |
| RISE client survey configured, and agents know where responses appear | MoxiWorks |
| Decision made on what happens to the existing high-frequency sends | Brokerage |
| Agents briefed that replies are coming directly to their inbox | Brokerage |
Build sequence — brokerage-to-agent communication
Partially proven — engagement measured, retention impact not yet confirmed. A brokerage struggling with both recruiting and retention. Digging into what that actually meant surfaced two separate problems, and one of them had to be fixed first.
What the diagnosis actually found
Recruiting: the messaging was vague and read as marketing copy. Agents weren't attracted to it because it wasn't concrete or authentic.
Retention: agents felt lost, forgotten, or like they were missing things.
These look like one problem and they aren't. You can't write an authentic recruiting story about a culture that isn't working yet — so recruiting content strategy was deliberately deferred, and retention was fixed first to generate something real to recruit with.
Facilitator note
When a brokerage names recruiting as the goal, ask what a new agent would find if they joined tomorrow. If the answer is uncomfortable, retention comes first — not as a consolation prize, but because it produces the story recruiting needs.
- Separate the recruiting problem from the retention problemName both, then explicitly park one. Deferring is a decision, not a failure — write down when you'll come back to it.
- Build a new-agent email series — monthly, first 12 monthsThe most important things a new agent needs to know, paced out across their first year instead of dumped in week one. Solves "I feel lost" by making orientation continuous.
- Build a weekly all-agent newsletter with a hard limit of three itemsThree most important or relevant pieces of information in the body. Nothing else. This constraint is the whole intervention — it is not a starting point to negotiate up from.
- Summarize in the email, detail on the intranetThe body carries the headline; the link carries the depth. Agents get the signal in ten seconds and choose what to go deeper on.
- Verify the new-agent trigger fires on start dateA drip that starts late or never is worse than no drip — it confirms the new agent's suspicion that they've been forgotten.
- Name the content owner and hold the three-item limitSomeone has to say no every week. Without a named editor, the newsletter grows back to the thing nobody read.
What actually changed
Measured: open rates on these emails are roughly double any other company communication.
Anecdotal: higher attendance at classes and office meetings, and more organic questions and collaboration happening in offices.
Not yet demonstrated: the retention number itself. Engagement and attendance are credible leading indicators, but if retention is the commitment in Part 2, the 90-day check has to be retention — not open rates.
Where this could still fail
The three-item limit erodes. Every department has something important, the newsletter drifts to seven items, open rates fall back to where they started, and it looks like the tactic stopped working when what actually happened is the discipline stopped.
Prerequisites — confirm before build
| Prerequisite | Who confirms |
|---|
| Agent roster current, with accurate start dates for the new-agent series | Brokerage |
| Intranet exists, is current, and agents can actually get into it | Brokerage |
| Twelve months of new-agent content outlined before the first send | Brokerage |
| A named weekly editor with authority to cut items | Brokerage |
| Baseline open rate on existing company communication, captured before launch | MoxiWorks |
| Current retention rate recorded, so the 90-day comparison is possible | Brokerage |
Build sequence — agent activation in RISE
This is the hardest mechanism but a critical framework to be successful. It's also the one everything else depends on.
Why this isn't optional
A brokerage can do everything right — send on behalf of agents, fill the pipeline, build the campaigns — and the agent still has to close the deal. Every other track on this page assumes agents have done the basics. If they haven't, nothing upstream reaches anyone.
The three essential actions
An agent has to do these three things to benefit from anything the brokerage builds. They're in order — each one makes the next worth doing.
| # | Action | Why it gates everything else |
|---|
| 1 | Add contacts | An empty database can't receive a campaign, a newsletter, or a nurture sequence. This is the floor. |
| 2 | Tag contacts | Contacts the system can't segment all get the same thing. Tagging is what makes brokerage-level automation land correctly. |
| 3 | Understand their market | The first two are data entry. This one is a habit — and it's what turns a contact list into a conversation the agent can actually have. |
Start at three, not one
The order above is how the actions build on each other — but it isn't the order to coach them in. Actions 1 and 2 are chores with a delayed payoff. Action 3 works immediately, because the market snapshot falls back to the agent's profile zip when their contacts aren't populated.
That makes it the on-ramp. An agent who checks their market every morning has a reason to add contacts: contacts carry Insights zips, and those zips make the snapshot reflect the market they actually work rather than the one their profile says they work. The chore becomes an upgrade to something they already use.
Check this before choosing another track
If your agents haven't done actions 1 and 2, a follow-up or nurture build will underdeliver and it will look like the campaign failed. Confirm the floor exists before building on it — or make activation the 90-day commitment and come back to the rest.
- Measure where the floor actually isPercentage of agents with contacts in RISE. Percentage with any tags applied. Distribution, not average — an average hides the fact that ten agents are doing all of it.
- Pick one action, not threeCoaching three behaviors at once gets you none. Start at action 1 if the database is empty; start at action 2 if contacts exist but nothing is segmented.
- Pre-build whatever the action depends onIf the action is tagging, ship the tag to every agent's account first — never ask agents to create it. Same principle that made the newsletter build reliable.
- Give the action an immediate, visible payoffAdding contacts is a chore unless something happens because of it. Tie the action to something the agent sees working within days, not quarters.
- Put the market snapshot in front of agents firstRISE AI's "Today in your Market" gives an agent month-over-month and year-over-year price and volume data. It reads the Insights zip/postal codes on their contacts — and falls back to the zip in their profile when contacts aren't populated yet. That fallback is the point: it works on day one, before an agent has added anything.
- Report progress back by office, not brokerage-wideManagers act on their own numbers. A single company-wide percentage gives nobody a reason to do anything.
What we've seen so far
Individual agents taking small actions in RISE have started to build momentum. It is too early to tell whether that translates into production for the agent or the brokerage. Treat this as a hypothesis you're testing with a specific brokerage, not a pattern with results behind it.
Where this could still fail
Activation gets measured as logins because logins are easy to count. Logins aren't one of the three actions. If the 90-day number is login rate, this track will report success while the database stays empty.
Prerequisites — confirm before build
| Prerequisite | Who confirms |
|---|
| Baseline captured: % of agents with contacts, % with tags applied | MoxiWorks |
| One action chosen — not a bundle | Brokerage |
| Office managers briefed and bought in — this only moves through them | Brokerage |
| Anything the action depends on is pre-built, not agent-created | Brokerage |
| Agreed that login rate is not the success metric | Both |
30 / 60 / 90
Three dates, three checks. Put them in the calendar before you leave the room.
