Nurture plans

BF

The BrokerFold Team — Product + Engineering

Last reviewed

Planning a follow-up sequence with notes beside the laptop

Nurture plans are the BrokerFold CRM’s follow-up autopilot: triggered sequences of waits and actions that keep you present through the long middle of a lead’s journey — built so that nothing sends without your review, nothing sends illegally, and nothing robotic lands while a real conversation is underway. Automation here has manners, and the manners are enforced by the engine.

Anatomy of a plan

A plan is a trigger plus ordered steps. Triggers enrol automatically: a new lead arriving through routing, a visitor registering on your site. Steps alternate waits — days or hours — with actions: send an email, create a task, update status, add a tag, notify an agent, or stop the plan. Frequency guards decide whether a person can ride a plan once ever, once per window, or per instance; one live journey exists per plan per contact, so re-enrolment can never double-email anyone.

The platform seeds a library to adapt rather than a blank page — including a visitor-welcome sequence spanning an immediate greeting through day-seven follow-up. Every seeded plan lands as a draft.

The review-first gate

Nothing in your account sends until you have looked at it and made a decision. The nurture surface in the dashboard presents each plan for review — one tap on, one tap off, with step editing and a live preview — and nags gently until you have decided. This is the opposite of the industry pattern where switching platforms silently enrols your database into someone’s default drip. Your name goes on every send; the product makes sure your eyes went there first.

The engine’s non-negotiables

Three rules live in the engine, not in recipes, so no plan can break them. Consent: every email passes the CASL gate — suppression checked first and permanent, consent basis and expiry evaluated per send, unknown consent never mailed. Every message carries your identification, mailing address, and a working unsubscribe; an incomplete footer pauses the enrolment rather than sending anyway. The full posture is documented on the CASL-compliant CRM page. Politeness: at most one nurture send per lead per day, with a rolling combined ceiling — enforced over a true 24-hour window. The human pause: a real two-way conversation suspends the journey, because a scheduled “checking in!” an hour after you booked the showing is how automation embarrasses agents.

What plans feed in the CRM

Every automated touch writes to the person’s timeline, badged with the plan that produced it — attribution is law, so the machine’s work is never mistaken for yours. Engagement flows back: opens, clicks and replies stamp the ledger, replies pause the journey and surface the lead for a human, and plan enrolments are visible on the person record with their paused-or-active state. The result reads less like a campaign report and more like a relationship history where some entries happen to be automated.

Where email drip campaigns is the category, nurture plans is BrokerFold’s implementation of it — the version built for a country with consent law and a profession where tone is the product. Included in the CRM on every plan; the only setup is the review you would have wanted to do anyway.

Frequently asked questions

Will anything send before I've approved it?

No. Library plans arrive as drafts, and the review surface asks for an explicit decision — on or off — before any enrolment sends. A nurture system that emails your leads copy you have never read is a liability, so the gate is structural.

Can a plan do more than send emails?

Yes. Steps can create a task for you, update the lead's status, add a tag, notify an agent, or stop the plan — waits in between. A good plan mixes machine touches with prompts for human ones, because automation's job is to cue the call, not replace it.

Keep reading

Fold your stack into one.

14 days free. No credit card. Your data stays yours.